Some checks failed
Code scanning / CodeQL (push) Failing after 15s
Zulip production suite / Ubuntu 22.04 production build (push) Failing after 26s
Zulip production suite / Debian 12 production install with custom db name and user (push) Has been skipped
Zulip production suite / Ubuntu 22.04 production install and PostgreSQL upgrade with pgroonga (push) Has been skipped
Zulip production suite / Ubuntu 24.04 production install (push) Has been skipped
Zulip production suite / Ubuntu 26.04 production install (push) Has been skipped
Zulip production suite / Debian 13 production install (push) Has been skipped
Zulip production suite / 7.0 Version Upgrade (push) Has been skipped
Zulip production suite / 8.0 Version Upgrade (push) Has been skipped
Zulip production suite / 6.0 Version Upgrade (push) Has been skipped
Zulip production suite / 10.0 Version Upgrade (push) Has been skipped
Zulip production suite / 9.0 Version Upgrade (push) Has been skipped
Zulip production suite / 12.0 Version Upgrade (push) Has been skipped
Zulip production suite / 11.0 Version Upgrade (push) Has been skipped
GitHub Actions Security Analysis with zizmor / zizmor (push) Failing after 3s
Zulip CI / Debian 12 (Python 3.11, backend + documentation) (push) Failing after 26s
Zulip CI / Ubuntu 22.04 (Python 3.10, backend + frontend) (push) Failing after 3s
Zulip CI / Ubuntu 24.04 (Python 3.12, backend) (push) Failing after 25s
Zulip CI / Ubuntu 26.04 (Python 3.14, backend) (push) Failing after 25s
Zulip CI / Debian 13 (Python 3.13, backend) (push) Failing after 28s
Zulip production suite / Required jobs (push) Has been cancelled
Zulip CI / Required jobs (push) Has been cancelled
API Documentation Update Check / check-feature-level-updated (push) Has been cancelled
API Documentation Update Check / notify-if-api-docs-changed (push) Has been cancelled
189 lines
9.8 KiB
HTML
189 lines
9.8 KiB
HTML
{% extends "zerver/marketing_page.html" %}
|
||
|
||
{% set PAGE_TITLE = "Jobs | Zulip" %}
|
||
|
||
{% set PAGE_DESCRIPTION = "We're hiring! Learn about our openings and how to
|
||
apply." %}
|
||
|
||
|
||
{% block marketing_content %}
|
||
|
||
<div class="portico-landing jobs why-page">
|
||
<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="main">
|
||
<div class="padded-content">
|
||
<div class="inner-content markdown">
|
||
<div class="open-positions">
|
||
<h1 id="open-positions">Open positions</h1>
|
||
<p>
|
||
|
||
To apply for an open position, please send your <b>resume</b>
|
||
and a brief <b>cover letter</b> (which can be in the
|
||
body of your email) to the email provided in the
|
||
description for the opening. Your cover letter should
|
||
explain what makes you excited about working at Zulip in
|
||
the role you're applying for. Applications without a
|
||
cover letter will not be considered.
|
||
</p>
|
||
<p>
|
||
If you are an experienced
|
||
engineer, and you believe that your background would be
|
||
a great fit for Zulip, please email us at <a
|
||
href="mailto:jobs+engineer@zulip.com">jobs+engineer@zulip.com</a>
|
||
with your resume and cover letter even if you don't see
|
||
an open role that looks like the right fit.
|
||
</p>
|
||
<p>
|
||
<i>All openings are remote.</i>
|
||
</p>
|
||
<hr/>
|
||
<h2 id="leader">Leadership team roles</h2>
|
||
<p>
|
||
<a href="/">Zulip</a> is an open-source team chat
|
||
application designed for seamless remote and hybrid
|
||
work. With conversations organized by topic, Zulip is <a
|
||
href="/why-zulip">ideal</a> for both live and
|
||
asynchronous communication. Zulip’s 100% open-source
|
||
software is available as a <a href="/plans/#cloud">cloud
|
||
service</a> or a
|
||
<a href="/self-hosting">self-hosted solution</a>, and is
|
||
used by thousands of organizations around the world.
|
||
Zulip is a <a
|
||
href="https://zulip.com/values/">values-focused</a>
|
||
organization stewarded by the nonprofit <a
|
||
href="https://blog.zulip.com/2026/05/15/announcing-zulip-foundation/">Zulip
|
||
Foundation</a>.
|
||
</p>
|
||
<p>
|
||
We are looking for experienced leaders familiar with Zulip
|
||
with strengths in the following areas. A single candidate is
|
||
not expected to cover all these areas.
|
||
</p>
|
||
<ul>
|
||
<li>
|
||
<strong>Technical</strong>: Technical leadership for a complex product (with web, desktop, and mobile apps) designed for reliability and maintainability.
|
||
</li>
|
||
<li>
|
||
<strong>Business</strong>: Business strategy and operations (finance, legal, payroll, etc.).
|
||
</li>
|
||
<li>
|
||
<strong>Management</strong>: Thoughtfully managing a remote team.
|
||
</li>
|
||
<li>
|
||
<strong>Marketing</strong>: B2B marketing strategy and execution.
|
||
</li>
|
||
<li>
|
||
<strong>Sales</strong>: Inbound sales and partnership negotiations.
|
||
</li>
|
||
<li>
|
||
<strong>Product</strong>: Managing a complex product that’s part of users’ daily workflows.
|
||
</li>
|
||
</ul>
|
||
<p>
|
||
We anticipate posting full job descriptions and
|
||
starting to interview candidates in June or July of
|
||
2026.
|
||
</p>
|
||
<p>
|
||
<em>Email us at <a
|
||
href="mailto:jobs+leader@zulip.com">jobs+leader@zulip.com</a>
|
||
with your resume and cover letter if you're interested,
|
||
and we’ll be in touch. Or learn more about <a
|
||
href="https://zulip.com/jobs/#how-we-work">how we
|
||
work</a>.</em>
|
||
</p>
|
||
<hr/>
|
||
</div>
|
||
<div class="how-we-work">
|
||
<h1 id="how-we-work">
|
||
How we work
|
||
</h1>
|
||
<p>
|
||
<strong>Open source.</strong> The Zulip software is 100%
|
||
free and open source. We're <a href="/team/">an
|
||
open-source project</a> first, and we’re building an
|
||
independent <a href="/values">sustainable business</a>
|
||
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>.
|
||
</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>
|
||
<p>
|
||
<strong>Globally distributed.</strong> Our company is
|
||
headquartered in San Francisco, CA, but like our
|
||
community, our ~15 person team works from around the
|
||
world. We communicate primarily async, in the <a
|
||
href="/development-community">Zulip development
|
||
community</a> and <a href="https://github.com/zulip">on
|
||
GitHub</a>. Our roles are open to all applicants without
|
||
regard for location.
|
||
</p>
|
||
<p>
|
||
<strong>Maintainable software.</strong> Great
|
||
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>
|
||
|
||
<div class="what-were-building">
|
||
<div class="main">
|
||
<div class="padded-content">
|
||
<div class="inner-content markdown">
|
||
<h1 id="what-were-building">
|
||
What we're building
|
||
</h1>
|
||
<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
|
||
Microsoft Teams; 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>
|
||
</div>
|
||
|
||
{% endblock %}
|