Job Opening: Support Engineer

Position filled

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.

Full-time. Remote.

tl;dr: We're looking for someone who wants to get into native macOS/Linux development with a focus on real-time communication over WebRTC. We'll train you on these technologies via frequent pairing with our senior engineers. When you're not leveling up, you'll dig into the thornier support issues our front-line support person can't figure out.

Who we are

Tuple is an app that lets developers pair program while working remotely. Think of it a bit like super-powered Zoom screen-sharing, used by developers who are writing code together in real-time from the comfort of home.

Folks tend to switch to Tuple because the screen-sharing is extremely high quality (important when viewing source code together) and the remote control is seamless and low-latency (important when controlling someone else's computer via the Internet).

We founded the company three years ago because we disliked the existing pairing tools, and believed that by focusing on this particular use-case, we could create a tool developers would actually like.

Turns out we were pretty much right! We've grown to millions in ARR and tens of thousands of paid users in three years without any outside funding.

Want even more details on how things are going? Our CEO Ben hosts a weekly podcast where he shares regular updates.

Role overview

Most Tuple calls go well. Our average call quality rating is 4.5 out of 5.

However, this aggregate rating hides the fact that every day, some users are struggling with bugs in our app. With tens of thousands of users, even a 0.1% issue rate can mean dozens of bad calls per day.

When our customers have bad calls, we want to dig in to their issues and help them, but it's hard to justify putting the time in when issues are fairly rare and our engineering team is small.

That's where you come in!

We'd like to add someone to the team who's excited by the idea of doing what it takes to track down these long-tail bugs. At first, you'll simply document reproduction steps so other folks can fix them quickly. Over time, we'll level up your C/C++/Swift/WebRTC knowledge to the point that you can fix them yourself.

You'll be learning these skills from two excellent developers: Spencer and Mikey. Both are great teachers and have a ton of knowlege to share. As you might expect, much of this training will happen via pairing sessions on Tuple.

You can expect to spend roughly half of your time learning and leveling up your programming chops, and half diving into customer issues and attempting to resolve them.

One project you might work on is creating better monitoring infrastructure for Tuple calls. While we do get call quality feedback from our users, it'd be nice to have a more holistic view of Tuple's performance across the user-base. You might also work on changes to our apps to report more diagnostic data to help you resolve customer issues.

About you

  • You've already got some solid programming chops, and are interesting in learning C, C++, Swift, and WebRTC.
  • You're comfortable working remotely.
  • You enjoy pairing.
  • You get a lot of high-quality work done each week.
  • You have excellent written English (you'll frequently be interacting with our customers via our support tool).

Why you might want to work with us

  • Spencer and Mikey are kind, experienced devs with lots to teach.
  • Once you can write C++ and know WebRTC, you will be ridiculously employable. If you don't love working at Tuple, you can have a new job in approximately ten nanoseconds.
  • We're a small company (~6 folks), so there are no layers of bureaucracy to work through. You can have a huge impact here.
  • You can work remotely, but your work day will need to overlap Boston and Paris by at least a few hours (Pacific Time won't work, unfortunately).
  • You'll have a front-row seat at an early-stage, fast-growing company. If you hope to start your own thing someday, this could be great preparation.

Why you might not want to work with us

  • You're going to spend a lot of time chasing down obscure bugs and communicating with customers. If you know you don't enjoy this sort of work, we're probably not a great fit for each other.
  • Tuple is a complicated app! There will be lots to learn before you can be truly productive.
  • You'll be working remotely.
  • We're new at this. We're learning how to run a company, and are bound to make mistakes. We want you to tell us when we do, though!



How to apply

Pitch us!

Please write something that tells us why we're a great fit for each other and what you see the future being like if we work together.

You don't need to include a resume, but that doesn't mean we're not interested in what you've done in the past. We're just leaving it up to you to tell your story the way you want to tell it.

When you're ready, email