mirror of https://github.com/zulip/zulip.git
portico: Remove Senior Flutter Engineer position from jobs page.
And go back to the note about not currently having any open positions.
This commit is contained in:
Greg Price
Tim Abbott
parent
b90505699a
commit
18fad546de
|
|
@ -28,12 +28,16 @@
|
||||||
<div class="inner-content markdown">
|
<div class="inner-content markdown">
|
||||||
<div class="open-positions">
|
<div class="open-positions">
|
||||||
<h1 id="open-positions">Open positions</h1>
|
<h1 id="open-positions">Open positions</h1>
|
||||||
|
<p>
|
||||||
|
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 <a href="mailto:jobs@zulip.com">jobs@zulip.com</a>
|
||||||
|
with your cover letter and resume.
|
||||||
|
</p>
|
||||||
<p>
|
<p>
|
||||||
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>
|
|
||||||
<li><a href="#flutter">Senior Flutter Engineer</a></li>
|
|
||||||
</ul>
|
|
||||||
</div>
|
</div>
|
||||||
<div class="how-we-work">
|
<div class="how-we-work">
|
||||||
<h1 id="how-we-work">
|
<h1 id="how-we-work">
|
||||||
|
|
@ -112,136 +116,6 @@
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
<div class="open-positions">
|
|
||||||
<div class="main">
|
|
||||||
<div class="padded-content markdown">
|
|
||||||
<h1>Open positions</h1>
|
|
||||||
|
|
||||||
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
|
|
||||||
<a href="mailto:jobs@zulip.com">jobs@zulip.com</a>. 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.
|
|
||||||
|
|
||||||
<h2 id="flutter">Senior Flutter Engineer</h2>
|
|
||||||
<p>
|
|
||||||
We're building the next generation of Zulip's mobile apps in Flutter.
|
|
||||||
We're looking for a senior engineer with Flutter experience
|
|
||||||
to join our small core team and help define the future of team chat.
|
|
||||||
Our Flutter prototype is just a few months old, so this is a
|
|
||||||
greenfield opportunity to help shape the app's architecture from
|
|
||||||
early on.
|
|
||||||
</p>
|
|
||||||
<p>
|
|
||||||
We take an "upstream first" approach: when we find problems in
|
|
||||||
Flutter itself, we make fixes upstream for the whole community.
|
|
||||||
Our upstream work so far has already led to one of our team
|
|
||||||
<a href="https://chat.zulip.org/#narrow/stream/2-general/topic/Flutter/near/1524757"
|
|
||||||
>being recognized as a Flutter core contributor</a>.
|
|
||||||
</p>
|
|
||||||
<p>
|
|
||||||
For this role, we expect a candidate to have substantial software
|
|
||||||
engineering experience, and at least some experience with Flutter.
|
|
||||||
</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>
|
|
||||||
Take responsibility for large, yet-unwritten, areas of Zulip's new
|
|
||||||
Flutter mobile app: design the architecture and write the code,
|
|
||||||
while collaborating with the rest of our small mobile team.
|
|
||||||
</li>
|
|
||||||
<li>
|
|
||||||
Diagnose and fix bugs small and large and across several
|
|
||||||
layers of our stack, including spelunking in Flutter itself
|
|
||||||
and third-party dependencies to find the best possible solution.
|
|
||||||
</li>
|
|
||||||
<li>
|
|
||||||
Work upstream with Flutter and other dependencies, by crafting
|
|
||||||
actionable bug reports and easy-to-merge pull requests to get
|
|
||||||
issues that affect Zulip fixed.
|
|
||||||
</li>
|
|
||||||
<li>
|
|
||||||
Work directly with Zulip’s product and design leads to add new
|
|
||||||
Zulip features in our Flutter app.
|
|
||||||
</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 Dart, with some Kotlin and Swift as needed.
|
|
||||||
No previous Kotlin or Swift experience is required.
|
|
||||||
</li>
|
|
||||||
</ul>
|
|
||||||
|
|
||||||
<h3>Extra credit for any of the following:</h3>
|
|
||||||
<ul>
|
|
||||||
<li>
|
|
||||||
You have extensive software engineering experience, with
|
|
||||||
deep expertise in mobile development, in reactive UIs,
|
|
||||||
or in Flutter.
|
|
||||||
</li>
|
|
||||||
<li>
|
|
||||||
You have significant experience as a technical lead for
|
|
||||||
your team, including designing systems and collaborating
|
|
||||||
to get them built, coaching people in writing
|
|
||||||
high-quality code, and other aspects of technical
|
|
||||||
leadership.
|
|
||||||
</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 contributed to open-source projects; better
|
|
||||||
yet, maintained a project and helped many people
|
|
||||||
contribute to it.
|
|
||||||
</li>
|
|
||||||
</ul>
|
|
||||||
<p>
|
|
||||||
Learn more about <a href="/jobs/#how-we-work">how we
|
|
||||||
work</a>, or apply by sending your resume and a brief cover
|
|
||||||
letter explaining what makes you excited about this role to
|
|
||||||
<a href="mailto:jobs@zulip.com">jobs@zulip.com</a>.
|
|
||||||
</p>
|
|
||||||
<br />
|
|
||||||
<hr />
|
|
||||||
|
|
||||||
<h2>How to apply for a job</h2>
|
|
||||||
<p>
|
|
||||||
You can email us at <a href="mailto:jobs@zulip.com">jobs@zulip.com</a> with your resume.
|
|
||||||
</p>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
{% endblock %}
|
{% endblock %}
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue