MBOX-Line: From mg at mit.edu  Mon Aug 25 23:09:12 2014
To: imap-protocol@u.washington.edu
From: Michael Grinich <mg@mit.edu>
Date: Fri Jun  8 12:34:53 2018
Subject: [Imap-protocol] [ADVERTISEMENT] open position for IMAP sync
	developer at Inbox
Message-ID: <CAO3aFYuvgh9gwedtG7Or5aJjdr-WDnhLEkC29RzmYwyK1Mch+Q@mail.gmail.com>

** NOTE: This is a IMAP developer job announcement. **

The Inbox team is looking for exceptional engineers to work on the IMAP
sync components that power the Inbox API. We are a team of engineers that
previously worked at Dropbox, Nest, Ksplice, Google, and elsewhere, and
we're building the next-generation platform for email apps.

https://www.inboxapp.com


This position is for an engineer to join our backend systems team and work
on the core Inbox sync engine, which is an essential part of the Inbox API.
Our sync engine handles downloading mail, performing queued actions,
resolving conflicts, and maintaining compatibility across all various IMAP
providers and protocol quirks. Nearly all of this code is free open source
software on GitHub: https://github.com/inboxapp/inbox


Our ideal candidate has

- Substantial experience with the IMAP protocol
- A desire to bring great software design and implementation to a
mainstream audience
- Strong Python coding skills with a deep understanding of language
fundamentals
- Experience with operating systems, performance instrumentation, and
service-oriented architectures
- Familiarity with SQLalchemy, MySQL, Gevent, or web services is a plus,
but not required


When applying, please include

- Brief statement about yourself and how you see a potential mutual fit
with the team
- Resume in Text or PDF form.


You can do this job from anywhere in the world. But if you would like to
move to San Francisco, we will cover relocation and help you get settled.


Please forward to anyone who may be interested. Thanks!


Michael Grinich

cofounder / CEO of Inbox
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20140825/2d23ec01/attachment.html>
