2018-11-08 22:43:55 +01:00
|
|
|
|
{% extends "zerver/portico.html" %}
|
2019-10-23 07:46:34 +02:00
|
|
|
|
{% set entrypoint = "landing-page" %}
|
2018-11-08 22:43:55 +01:00
|
|
|
|
|
|
|
|
|
{% block title %}
|
|
|
|
|
<title>Zulip jobs</title>
|
|
|
|
|
{% endblock %}
|
|
|
|
|
|
|
|
|
|
{% block customhead %}
|
2021-04-21 00:46:14 +02:00
|
|
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
|
2018-11-08 22:43:55 +01:00
|
|
|
|
{% endblock %}
|
|
|
|
|
|
|
|
|
|
{% block portico_content %}
|
|
|
|
|
|
|
|
|
|
{% include 'zerver/landing_nav.html' %}
|
|
|
|
|
|
|
|
|
|
<div class="portico-landing jobs why-page no-slide">
|
|
|
|
|
<div class="hero bg-pycon drone">
|
|
|
|
|
<div class="bg-dimmer"></div>
|
|
|
|
|
<div class="content">
|
|
|
|
|
<h1 class="center">Work with us</h1>
|
|
|
|
|
<p>We're 100% open source, and we're hiring.</p>
|
|
|
|
|
</div>
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
<div class="open-positions-top">
|
|
|
|
|
<div class="main">
|
2019-07-22 19:22:56 +02:00
|
|
|
|
<div class="padded-content markdown">
|
2018-11-08 22:43:55 +01:00
|
|
|
|
<h1>Open positions</h1>
|
2021-12-01 20:54:37 +01:00
|
|
|
|
<p>
|
|
|
|
|
All openings are remote, or partially in-person in our San Francisco, CA office.
|
|
|
|
|
</p>
|
2022-02-03 02:56:29 +01:00
|
|
|
|
<ul>
|
2022-02-03 02:56:52 +01:00
|
|
|
|
<li><a href="#infra">Senior Infrastructure Engineer</a></li>
|
2022-02-03 02:56:29 +01:00
|
|
|
|
<li><a href="#mobile">Senior Mobile Engineer</a></li>
|
|
|
|
|
<li><a href="#fullstack">Senior Full Stack Engineer</a></li>
|
|
|
|
|
<li><a href="#marketing">Marketing/Growth Lead</a></li>
|
|
|
|
|
<li><a href="#writer">Technical Writer (part-time)</a></li>
|
|
|
|
|
</ul>
|
2018-11-08 22:43:55 +01:00
|
|
|
|
</div>
|
|
|
|
|
</div>
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
<div class="how-we-work">
|
|
|
|
|
<div class="main">
|
2019-07-22 19:22:56 +02:00
|
|
|
|
<div class="padded-content markdown">
|
2021-12-01 20:54:37 +01:00
|
|
|
|
<h1 id="how-we-work">
|
|
|
|
|
How we work
|
|
|
|
|
</h1>
|
2018-11-08 22:43:55 +01:00
|
|
|
|
<p>
|
2021-12-02 00:51:16 +01:00
|
|
|
|
<strong>Open source.</strong> The Zulip software is 100% free and
|
2018-11-08 22:43:55 +01:00
|
|
|
|
open source. We're <a href="/team/">an open-source project</a> first,
|
|
|
|
|
and we’re building a sustainable business as a means to support the
|
|
|
|
|
project's growth and long-term future. We provide the same open-source
|
|
|
|
|
code to our largest customers as to anyone with <code>git clone</code>.
|
|
|
|
|
We get paid by enterprises for support, and by smaller companies using
|
|
|
|
|
our rapidly-growing hosted service.
|
|
|
|
|
</p>
|
|
|
|
|
<p>
|
|
|
|
|
<strong>Open project.</strong> The Zulip project is one where people
|
|
|
|
|
really do show up through the Internet and start making real changes.
|
|
|
|
|
That doesn’t happen by accident; it takes work and thoughtfulness. Most
|
|
|
|
|
of us work remotely, and we discuss our code and our plans in public, in
|
|
|
|
|
writing, primarily asynchronously, using Zulip and GitHub.
|
|
|
|
|
</p>
|
|
|
|
|
<p>
|
|
|
|
|
<strong>Inclusive community.</strong> The Zulip community is made up of a
|
|
|
|
|
mixture of volunteers and professionals from all walks of life. Diversity is
|
|
|
|
|
one of our strengths, and we strive to be a community that welcomes and
|
|
|
|
|
supports people of all backgrounds and identities from anywhere in the world.
|
|
|
|
|
</p>
|
2021-11-16 07:30:09 +01:00
|
|
|
|
<p>
|
|
|
|
|
<strong>Globally distributed.</strong> Our company is
|
|
|
|
|
headquartered in San Francisco, CA, but like our community,
|
|
|
|
|
we work from around the world. Our roles
|
|
|
|
|
are open to all applicants without regard for location.
|
|
|
|
|
</p>
|
2018-11-08 22:43:55 +01:00
|
|
|
|
<p>
|
2021-12-02 00:51:16 +01:00
|
|
|
|
<strong>Maintainable software.</strong> Great
|
2018-11-08 22:43:55 +01:00
|
|
|
|
software over time depends on a team’s shared
|
|
|
|
|
understanding of a system and how to change it, as
|
|
|
|
|
much as on the code itself. Beyond writing our
|
|
|
|
|
code so it works today, we put equal effort into
|
|
|
|
|
writing code, tests, comments, commit history,
|
|
|
|
|
and <a href="https://zulip.readthedocs.io/en/latest/">documentation</a>
|
|
|
|
|
clearly, to share with each other and future
|
|
|
|
|
contributors our understanding of how and why it
|
|
|
|
|
works, so we can build on it tomorrow.
|
|
|
|
|
</p>
|
|
|
|
|
</div>
|
|
|
|
|
</div>
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
<div class="what-were-building">
|
|
|
|
|
<div class="main">
|
2019-07-22 19:22:56 +02:00
|
|
|
|
<div class="padded-content markdown">
|
2021-12-01 20:54:37 +01:00
|
|
|
|
<h1 id="what-were-building">
|
|
|
|
|
What we're building
|
|
|
|
|
</h1>
|
2018-11-08 22:43:55 +01:00
|
|
|
|
<p>
|
|
|
|
|
People working together need to communicate with their teammates, and they
|
|
|
|
|
also need to tune out the conversation to get work done. Teams tired of
|
|
|
|
|
wasting time in meetings move discussion to email; tired of waiting all
|
|
|
|
|
day for email replies, move to a team chat like Slack or IRC; and then
|
|
|
|
|
team chat becomes an always-on meeting, leaving people constantly
|
|
|
|
|
distracted, missing out on important conversations, or both.
|
|
|
|
|
</p>
|
|
|
|
|
<p>
|
|
|
|
|
Zulip is reinventing chat so teams can accomplish more together. We've
|
|
|
|
|
created a place where a conversation can shift seamlessly from the
|
|
|
|
|
immediacy of chat to the reply-whenever efficiency of email, and back;
|
|
|
|
|
where you can participate in the conversations that matter to you and
|
|
|
|
|
efficiently tune out the rest, no matter whether you're there in real
|
|
|
|
|
time, coming online after a morning hard at work, or returning from a
|
|
|
|
|
vacation away from it.
|
|
|
|
|
</p>
|
|
|
|
|
</div>
|
|
|
|
|
</div>
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
<div class="open-positions">
|
|
|
|
|
<div class="main">
|
2019-07-22 19:22:56 +02:00
|
|
|
|
<div class="padded-content markdown">
|
2018-11-08 22:43:55 +01:00
|
|
|
|
<h1>Open positions</h1>
|
|
|
|
|
|
2022-02-03 02:56:52 +01:00
|
|
|
|
<h2 id="infra">
|
|
|
|
|
Senior Infrastructure Engineer
|
|
|
|
|
</h2>
|
|
|
|
|
<p>
|
|
|
|
|
We’re looking for an engineer to join our small
|
|
|
|
|
core team and help define the future of team
|
|
|
|
|
chat.
|
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
<p>
|
|
|
|
|
This job is remote, or partially in-person in our
|
|
|
|
|
San Francisco, CA office.
|
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
<h3>We'd especially like to get to know you if:</h3>
|
|
|
|
|
<ul>
|
|
|
|
|
<li>
|
|
|
|
|
<strong>You love giving a code review, and love receiving one.</strong>
|
|
|
|
|
We’re an open-source project welcoming contributions from people with
|
|
|
|
|
a wide range of experience.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
<strong>You communicate with clarity and precision.</strong>
|
|
|
|
|
You’ll be doing this a lot in code, comments, code reviews, and chat
|
|
|
|
|
conversations. We care about this almost as much as your technical
|
|
|
|
|
skills.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
<strong>You can empathize with the many different types of users</strong>
|
|
|
|
|
who rely on Zulip, and see the product from their perspective — and do
|
|
|
|
|
the same thing for the project's contributors.
|
|
|
|
|
</li>
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
<h3>You will:</h3>
|
|
|
|
|
<ul>
|
|
|
|
|
<li>
|
|
|
|
|
Design, circulate proposals for, and build new
|
|
|
|
|
features and subsystems.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
Collaborate with other experts on our
|
|
|
|
|
infrastructure team to deploy and maintain the
|
|
|
|
|
servers that power Zulip Cloud.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
Design and implement improvements to our
|
|
|
|
|
tooling for installing, upgrading, and
|
|
|
|
|
maintaining a self-hosted Zulip server, both
|
|
|
|
|
for our traditional installer and Docker
|
|
|
|
|
image.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
Diagnose and fix bugs small and large and
|
|
|
|
|
across several layers of our stack, including
|
|
|
|
|
spelunking in third-party dependencies to find
|
|
|
|
|
the best possible solution. You will
|
|
|
|
|
prioritize fixing problems upstream when
|
|
|
|
|
possible, contributing to the open source
|
|
|
|
|
ecosystem.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
Bring a mindset of security awareness and
|
|
|
|
|
custodianship for customer data — identifying,
|
|
|
|
|
mitigating, and publishing security
|
|
|
|
|
vulnerabilities in Zulip and its dependencies.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
Share your expertise (both newly-acquired and
|
|
|
|
|
longstanding) with the rest of the team,
|
|
|
|
|
through short- and long-form written
|
|
|
|
|
communication.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
Write primarily Python, as well as some Puppet and shell.
|
|
|
|
|
</li>
|
|
|
|
|
</ul>
|
|
|
|
|
<h3>Extra credit for any of the following:</h3>
|
|
|
|
|
<ul>
|
|
|
|
|
<li>
|
|
|
|
|
You have 5+ years of software engineering
|
|
|
|
|
experience in a variety of settings: backend
|
|
|
|
|
services, or build systems, or desktop GUI
|
|
|
|
|
software — you name it.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
You have experience deploying, analyzing, and
|
|
|
|
|
diagnosing complicated and high-availability
|
|
|
|
|
systems with live traffic.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
You have experience designing systems for other
|
|
|
|
|
people to build different pieces of, coaching
|
|
|
|
|
people in writing high-quality code, or other
|
|
|
|
|
aspects of technical leadership.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
You have spent time maintaining and debugging
|
|
|
|
|
long-running, highly scalable server systems.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
You have experience doing large codebase
|
|
|
|
|
migrations in web apps in a way that minimizes
|
|
|
|
|
regressions.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
You have contributed to open-source projects;
|
|
|
|
|
better yet, maintained a project and helped many
|
|
|
|
|
people contribute to it.
|
|
|
|
|
</li>
|
|
|
|
|
</ul>
|
|
|
|
|
<p>
|
|
|
|
|
Email us
|
|
|
|
|
at <a href="mailto:jobs@zulip.com">jobs@zulip.com</a>
|
|
|
|
|
with your resume and portfolio to apply, or learn more about
|
|
|
|
|
<a href="/jobs/#how-we-work">how we work</a>.
|
|
|
|
|
</p>
|
|
|
|
|
<br />
|
|
|
|
|
<hr />
|
|
|
|
|
|
2018-11-08 22:43:55 +01:00
|
|
|
|
<h2 id="mobile">Senior Mobile Engineer</h2>
|
|
|
|
|
<p>
|
|
|
|
|
Our mobile app is a critical part of the Zulip experience. We’re looking
|
|
|
|
|
for an engineer to join our small, growing, core team and help define the
|
|
|
|
|
future of team chat on mobile.
|
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
<h3>We'd especially like to get to know you if:</h3>
|
|
|
|
|
<ul>
|
|
|
|
|
<li>
|
|
|
|
|
<strong>You love giving a code review, and love receiving one.</strong>
|
|
|
|
|
We’re an open-source project welcoming contributions from people with
|
|
|
|
|
a wide range of experience.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
<strong>You communicate with clarity and precision.</strong>
|
|
|
|
|
You’ll be doing this a lot in code, comments, code reviews, and chat
|
|
|
|
|
conversations. We care about this almost as much as your technical
|
|
|
|
|
skills.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
<strong>You can empathize with the many different types of users</strong>
|
|
|
|
|
who rely on Zulip, and see the product from their perspective — and do
|
|
|
|
|
the same thing for the project's contributors.
|
|
|
|
|
</li>
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
<h3>You will:</h3>
|
|
|
|
|
<ul>
|
|
|
|
|
<li>
|
|
|
|
|
Design new features and subsystems, write design proposals for
|
|
|
|
|
discussion, and build them.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
Diagnose and fix bugs small and large and across several layers of our
|
|
|
|
|
stack, and resolve questions about the frameworks and libraries we
|
|
|
|
|
rely on by diving into their source when the documentation doesn't
|
|
|
|
|
suffice.
|
|
|
|
|
</li>
|
|
|
|
|
<li>Share your expertise (both newly-acquired and longstanding) with the
|
2021-11-20 13:25:41 +01:00
|
|
|
|
rest of the team, through short- and long-form written communication.
|
|
|
|
|
</li>
|
2018-11-08 22:43:55 +01:00
|
|
|
|
<li>Write primarily JavaScript using React Native, with some Java, Swift,
|
2021-11-20 13:25:41 +01:00
|
|
|
|
and backend Python, and learn whichever of those are new to you.
|
|
|
|
|
</li>
|
2018-11-08 22:43:55 +01:00
|
|
|
|
<li>Work from our office in San Francisco, or from anywhere in the United
|
2021-11-20 13:25:41 +01:00
|
|
|
|
States.
|
|
|
|
|
</li>
|
2018-11-08 22:43:55 +01:00
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
<h3>Extra credit for any of the following:</h3>
|
|
|
|
|
<ul>
|
|
|
|
|
<li>You have 5+ years of software engineering experience in a variety of
|
|
|
|
|
settings: backend services, or build systems, or desktop GUI software —
|
|
|
|
|
you name it.
|
|
|
|
|
</li>
|
|
|
|
|
<li>You have experience designing systems for other people to build
|
|
|
|
|
different pieces of, coaching people in writing high-quality code, or
|
|
|
|
|
other aspects of technical leadership.
|
|
|
|
|
</li>
|
|
|
|
|
<li>You have spent time maintaining and debugging long-running systems.</li>
|
|
|
|
|
<li>You have the UI design skills to spot where a UI can be improved;
|
|
|
|
|
better yet, to design a better one.
|
|
|
|
|
</li>
|
|
|
|
|
<li>You have experience with iOS or Android development.</li>
|
|
|
|
|
<li>You have experience with React.</li>
|
|
|
|
|
<li>You have contributed to open-source projects; better yet, maintained a
|
|
|
|
|
project and helped many people contribute to it.
|
|
|
|
|
</li>
|
|
|
|
|
</ul>
|
2021-05-13 01:35:48 +02:00
|
|
|
|
<p>
|
2021-12-02 03:36:57 +01:00
|
|
|
|
Email us at <a href="mailto:jobs@zulip.com">jobs@zulip.com</a> with your
|
2021-12-01 20:54:37 +01:00
|
|
|
|
resume to apply, or learn more about
|
|
|
|
|
<a href="/jobs/#how-we-work">how we work</a>.
|
2021-05-13 01:35:48 +02:00
|
|
|
|
</p>
|
2018-11-08 22:43:55 +01:00
|
|
|
|
|
2021-04-21 00:46:14 +02:00
|
|
|
|
<br />
|
|
|
|
|
<hr />
|
2018-11-08 22:43:55 +01:00
|
|
|
|
|
|
|
|
|
<h2 id="fullstack">Senior Full Stack Engineer</h2>
|
|
|
|
|
<p>
|
|
|
|
|
We’re looking for an engineer to join our small
|
|
|
|
|
core team and help define the future of team chat.
|
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
<h3>We'd especially like to get to know you if:</h3>
|
|
|
|
|
<ul>
|
|
|
|
|
<li>
|
|
|
|
|
<strong>You love giving a code review, and love receiving one.</strong>
|
|
|
|
|
We’re an open-source project welcoming contributions from people with
|
|
|
|
|
a wide range of experience.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
<strong>You communicate with clarity and precision.</strong>
|
|
|
|
|
You’ll be doing this a lot in code, comments, code reviews, and chat
|
|
|
|
|
conversations. We care about this almost as much as your technical
|
|
|
|
|
skills.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
<strong>You can empathize with the many different types of users</strong>
|
|
|
|
|
who rely on Zulip, and see the product from their perspective — and do
|
|
|
|
|
the same thing for the project's contributors.
|
|
|
|
|
</li>
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
<h3>You will:</h3>
|
|
|
|
|
<ul>
|
|
|
|
|
<li>Design new features and subsystems, write design proposals for
|
|
|
|
|
discussion, and build them.
|
|
|
|
|
</li>
|
|
|
|
|
<li>Diagnose and fix bugs small and large and across several layers of our
|
|
|
|
|
stack, including spelunking in third-party dependencies to find the
|
|
|
|
|
best possible solution.
|
|
|
|
|
</li>
|
|
|
|
|
<li>Share your expertise (both newly-acquired and longstanding) with the
|
|
|
|
|
rest of the team, through short- and long-form written communication.
|
|
|
|
|
</li>
|
|
|
|
|
<li>Write primarily Python, JavaScript, HTML, and CSS.</li>
|
|
|
|
|
<li>Work from our office in San Francisco, or from anywhere in the world.</li>
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
<h3>Extra credit for any of the following:</h3>
|
|
|
|
|
<ul>
|
|
|
|
|
<li>You have 5+ years of software engineering experience in a variety of
|
|
|
|
|
settings: backend services, or build systems, or desktop GUI software
|
|
|
|
|
— you name it.
|
|
|
|
|
</li>
|
|
|
|
|
<li>You have experience designing systems for other people to build
|
|
|
|
|
different pieces of, coaching people in writing high-quality code, or
|
|
|
|
|
other aspects of technical leadership.
|
|
|
|
|
</li>
|
|
|
|
|
<li>You have spent time maintaining and debugging long-running, highly
|
|
|
|
|
scalable server systems.
|
|
|
|
|
</li>
|
|
|
|
|
<li>You have the UI design skills to spot where a UI can be improved;
|
|
|
|
|
better yet, to design a better one.
|
|
|
|
|
</li>
|
2021-05-14 00:16:30 +02:00
|
|
|
|
<li>You have experience doing large codebase migrations in web apps in a way
|
2018-11-08 22:43:55 +01:00
|
|
|
|
that minimizes regressions.
|
|
|
|
|
</li>
|
|
|
|
|
<li>You have contributed to open-source projects; better yet, maintained a
|
|
|
|
|
project and helped many people contribute to it.
|
|
|
|
|
</li>
|
|
|
|
|
</ul>
|
2021-05-13 01:35:48 +02:00
|
|
|
|
<p>
|
2021-12-02 03:36:57 +01:00
|
|
|
|
Email us at <a href="mailto:jobs@zulip.com">jobs@zulip.com</a> with your
|
2021-12-01 20:54:37 +01:00
|
|
|
|
resume to apply, or learn more about
|
|
|
|
|
<a href="/jobs/#how-we-work">how we work</a>.
|
2021-05-13 01:35:48 +02:00
|
|
|
|
</p>
|
|
|
|
|
<br />
|
|
|
|
|
<hr />
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<h2 id="marketing">Marketing/Growth Lead (full-time or part-time)</h2>
|
|
|
|
|
<p>
|
|
|
|
|
We’re looking for an experienced leader
|
|
|
|
|
to accelerate the growth of our business.
|
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
<h3>We'd especially like to get to know you if:</h3>
|
|
|
|
|
<ul>
|
|
|
|
|
<li>You have prior experience in a marketing or
|
|
|
|
|
growth leadership role at a B2B startup. You
|
|
|
|
|
know what questions to ask, and will figure
|
|
|
|
|
out how to experiment and innovate to take our
|
|
|
|
|
business to the next level.
|
|
|
|
|
</li>
|
|
|
|
|
<li>You are not afraid to get your hands dirty. If something needs to happen,
|
|
|
|
|
you will get it done.
|
|
|
|
|
</li>
|
|
|
|
|
<li>You are an excellent writer and storyteller.
|
|
|
|
|
</li>
|
|
|
|
|
<li>You communicate with clarity and precision,
|
|
|
|
|
and are comfortable in a distributed work
|
|
|
|
|
environment.
|
|
|
|
|
</li>
|
|
|
|
|
</ul>
|
|
|
|
|
<h3>You will:</h3>
|
|
|
|
|
<ul>
|
|
|
|
|
<li>Work closely with our leadership team to
|
|
|
|
|
develop growth and marketing strategy, and
|
|
|
|
|
align it with our product roadmap.
|
|
|
|
|
</li>
|
|
|
|
|
<li>Drive the execution of key growth and marketing initiatives.
|
|
|
|
|
</li>
|
|
|
|
|
<li>Create high-quality materials for our website,
|
|
|
|
|
blog, PR and advertising campaigns.
|
|
|
|
|
</li>
|
|
|
|
|
</ul>
|
|
|
|
|
<p>
|
2021-12-01 20:54:37 +01:00
|
|
|
|
Email us at <a href="mailto:jobs@zulip.com">jobs@zulip.com</a> with your resume to apply, or learn more about
|
|
|
|
|
<a href="/jobs/#how-we-work">how we work</a>.
|
2021-05-13 01:35:48 +02:00
|
|
|
|
</p>
|
|
|
|
|
<br />
|
|
|
|
|
<hr />
|
|
|
|
|
|
|
|
|
|
<h2 id="writer">Technical Writer (part-time)</h2>
|
|
|
|
|
<p>
|
|
|
|
|
Excellent documentation is a major priority for
|
|
|
|
|
our project, and we are looking for an experienced
|
|
|
|
|
technical writer to organize, extend and improve
|
|
|
|
|
our <a href="https://zulip.com/help/">user</a>
|
|
|
|
|
and <a href="https://zulip.readthedocs.io/en/latest/">developer</a>
|
|
|
|
|
docs.
|
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
<h3>We'd especially like to get to know you if:</h3>
|
|
|
|
|
<ul>
|
|
|
|
|
<li>You have empathy for users of our product, and
|
|
|
|
|
are able to predict and address their questions
|
|
|
|
|
and points of confusion.
|
|
|
|
|
</li>
|
|
|
|
|
<li>You have excellent attention to
|
|
|
|
|
detail. Instructions you write are clear,
|
|
|
|
|
well-tested, and in accordance with
|
2022-01-26 04:00:44 +01:00
|
|
|
|
our <a href="https://zulip.readthedocs.io/en/latest/documentation/helpcenter.html#writing-documentation">style
|
2021-05-13 01:35:48 +02:00
|
|
|
|
guidelines</a>; there are no typos or broken
|
|
|
|
|
links.
|
|
|
|
|
</li>
|
|
|
|
|
<li>You are comfortable with using Git to preview
|
|
|
|
|
new product features and contribute documentation
|
|
|
|
|
updates, or are happy to learn.
|
|
|
|
|
</li>
|
|
|
|
|
<li>You communicate with clarity and precision,
|
|
|
|
|
and are comfortable in a distributed work
|
|
|
|
|
environment.
|
|
|
|
|
</li>
|
|
|
|
|
</ul>
|
|
|
|
|
<h3>You will:</h3>
|
|
|
|
|
<ul>
|
|
|
|
|
<li>
|
|
|
|
|
Work closely with engineers to create polished
|
|
|
|
|
documentation for new product features and
|
|
|
|
|
feature updates.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
Create user docs for our mobile app.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
Extend
|
2022-01-26 04:00:44 +01:00
|
|
|
|
our <a href="https://zulip.readthedocs.io/en/latest/documentation/helpcenter.html#writing-documentation">style
|
2021-05-13 01:35:48 +02:00
|
|
|
|
guide</a> to help developers document the
|
|
|
|
|
features they build effectively.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
Think carefully about how to keep our
|
|
|
|
|
documentation clear and organized, and
|
|
|
|
|
restructure it as needed.
|
|
|
|
|
</li>
|
|
|
|
|
</ul>
|
|
|
|
|
<p>
|
2021-12-02 03:36:57 +01:00
|
|
|
|
Email us at <a href="mailto:jobs@zulip.com">jobs@zulip.com</a> with your
|
2021-12-01 20:54:37 +01:00
|
|
|
|
resume to apply, or learn more about
|
|
|
|
|
<a href="/jobs/#how-we-work">how we work</a>.
|
2021-05-13 01:35:48 +02:00
|
|
|
|
</p>
|
2021-04-21 00:46:14 +02:00
|
|
|
|
<br />
|
|
|
|
|
<hr />
|
2019-05-23 21:08:52 +02:00
|
|
|
|
|
|
|
|
|
<h2>How to apply for a job</h2>
|
|
|
|
|
<p>
|
2020-06-09 00:58:42 +02:00
|
|
|
|
You can email us at <a href="mailto:jobs@zulip.com">jobs@zulip.com</a> with your resume.
|
2019-05-23 21:08:52 +02:00
|
|
|
|
</p>
|
2018-11-08 22:43:55 +01:00
|
|
|
|
</div>
|
|
|
|
|
</div>
|
|
|
|
|
</div>
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
{% endblock %}
|