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.
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.
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.
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 firstname.lastname@example.org.