This position has been filled. We're flattered that you'd consider applying to work here, though.
You can always tell us why we should hire you anyway or get notified when we post new openings.
tl;dr: We're looking for someone with exquisite taste and a high bar for quality to design thoughtful features, produce high-fidelity mocks, and work with our engineers to implement them.
Tuple is an app for remote pair programming available on macOS and Linux
We (Ben, Spencer, and Joel) founded the company four years ago because we disliked pairing over Slack and Zoom. We believed that by focusing on remote pairing exclusively, we could create a tool that developers would actually like.
Turns out we were right! We've grown to millions in revenue and tens of thousands of paid users in four years without any outside funding. Our product is used by the savvy engineers at companies like Shopify, Stripe, Spotify, and Netflix.
(Want the latest on how things are going? Ben hosts a weekly podcast where he shares regular updates.)
For the sake of simplicity, imagine shipping a new feature consists of only three steps:
Today, we need the most help with step three, some help step two, and the least with step one.
Step one is generally handled by our CEO Ben, who owns the product roadmap.
Ben will also tend to provide significant guidance (aka "sometimes annoyingly-specific opinions") on the second step. This could range from a broad-strokes description to a shaped pitch.
Much of your initial work will consist of taking this step-two guidance and turning it into high-fidelity designs for our engineers to implement.
As an example, you'll frequently be answering questions like "We know we want a button, and we know what happens when you click it, but where do we put it? What does it look like? What's the label? Should it have an icon? Does it need to micro-copy to explain common questions? Should it always be displayed or only when X is true?"
As the feature gets implemented, you'll make decisions on questions that come up, improvise clever workarounds when we hit technical roadblocks, and ensure we ship something that achieves the broad-strokes goal.
Along the way, you will be an absolute stickler about getting the details right at many levels of abstraction:
As you get to know our product and users and demonstrate your competence through shipped work, you can expect to own more of the second step described above. Eventually, we'd love to have you contribute substantially to the entire process, though it's likely that Ben will continue to make the final calls on the product roadmap for some time to come.
Please try our macOS app and suggest a UX improvement you think would most improve the product. (Please refrain from commenting on small visual details like contrast or colors. We know there's lot of low-hanging fruit there (and we'll get to it) but it doesn't reveal much about your abilities.) Email your thoughts (and links to your best work) to firstname.lastname@example.org.