mirror of https://github.com/zulip/zulip.git
portico: Remove Senior Infrastructure Engineer position from /jobs.
This commit is contained in:
parent
8577adcf2e
commit
ede6699d83
|
@ -30,7 +30,6 @@
|
||||||
All openings are remote, or partially in-person in our San Francisco, CA office.
|
All openings are remote, or partially in-person in our San Francisco, CA office.
|
||||||
</p>
|
</p>
|
||||||
<ul>
|
<ul>
|
||||||
<li><a href="#infra">Senior Infrastructure Engineer</a></li>
|
|
||||||
<li><a href="#mobile">Senior Mobile Engineer</a></li>
|
<li><a href="#mobile">Senior Mobile Engineer</a></li>
|
||||||
<li><a href="#fullstack">Senior Full Stack 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="#marketing">Marketing/Growth Lead</a></li>
|
||||||
|
@ -122,126 +121,6 @@
|
||||||
<div class="padded-content markdown">
|
<div class="padded-content markdown">
|
||||||
<h1>Open positions</h1>
|
<h1>Open positions</h1>
|
||||||
|
|
||||||
<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 />
|
|
||||||
|
|
||||||
<h2 id="mobile">Senior Mobile Engineer</h2>
|
<h2 id="mobile">Senior Mobile Engineer</h2>
|
||||||
<p>
|
<p>
|
||||||
Our mobile app is a critical part of the Zulip experience. We’re looking
|
Our mobile app is a critical part of the Zulip experience. We’re looking
|
||||||
|
|
Loading…
Reference in New Issue