{% extends "zerver/portico.html" %} {% set entrypoint = "landing-page" %} {% set PAGE_TITLE = "Jobs | Zulip" %} {% set PAGE_DESCRIPTION = "We're hiring! Learn about our openings and how to apply." %} {% block customhead %} {% endblock %} {% block portico_content %} {% include 'zerver/landing_nav.html' %}

Work with us

We're 100% open source, and we're hiring.

Open positions

We are not actively recruiting for any roles at this time. However, if you are an experienced engineer, and you believe that your background would be a great fit for Zulip, please email us at jobs@zulip.com with your cover letter and resume.

All openings are remote, or partially in-person in our San Francisco, CA office.

How we work

Open source. The Zulip software is 100% free and open source. We're an open-source project 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 git clone. We get paid by enterprises for support, and by smaller companies using our rapidly-growing hosted service.

Open project. 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.

Inclusive community. 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.

Globally distributed. 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.

Maintainable software. 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 documentation clearly, to share with each other and future contributors our understanding of how and why it works, so we can build on it tomorrow.

What we're building

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.

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.

{% endblock %}