We're hiring a WebRTC Expert
tl;dr: We’d like to hire a WebRTC expert (or someone intent on
becoming one and well on their way) to help us bring multiway calls
to the app, to reduce its latency and improve performance, and
maybe even build an RTC pipeline from scratch some day.
Who we are
Tuple is a macOS app for remote pair programming.
We (Ben, Spencer, and Joel) founded the company 2
years ago because we hated pairing over Slack and Zoom. We believed
that by focusing on remote pairing exclusively, we could create a tool
that developers would actually like.
We bootstrapped the company from our own savings, and only hired our first full-time employee last month (an awesome engineer named Mikey).
Despite these constraints, things are working really well. We have hundreds of happy customers and thousands of paid users. We're growing revenue way faster than most bootstrapped businesses and are quite profitable.
Want even more details on how things are going? Ben hosts a weekly podcast where he shares regular updates.
We're looking for a heavy-hitter to work full-time with our CTO, Spencer, and engineer, Mikey.
WebRTC is our core dependency, and the degree to which we use it
well is critical to our business. We want to hire someone for the
long-haul to make sure this foundation is incredibly solid. The right
person has the skills and the drive to help us make Tuple faster and
more reliable every month.
Day-to-day, you should expect to pair (using Tuple, naturally) somewhat regularly.
We love junior developers, but this role is for someone senior.
Here's how to tell if you'd be a good fit for this job.
- You have substantial experience building things with WebRTC. Ideally, you've built some sort of native app rather than just using the version compiled into browsers.
- You’re an expert at programming in C++. You’re unintimidated by the idea of reading (and forking, and modifying!) WebRTC’s C++ codebase.
- You’re excited about the idea of shaving 1-10ms off of our latency, or 10% off of our CPU usage. What’s more, you’ve done that sort of work before and know how to go about tackling optimization problems.
- You know your way around video codecs and how to tune them.
- You believe in the power of pair programming (here's our take on it).
- You write well.
- You have experience dealing with audio devices, and want to help us prevent the phrase “I can hear you, can you hear me?” from ever being uttered on a Tuple call.
- You're not afraid of sitting down with a tasty beverage and digging into an RFC. Low-level internals excite, rather than scare you.
- You have experience collecting stats on and monitoring WebRTC-based calls. You’re excited about building out our monitoring infrastructure so we always know how Tuple calls are going in the real world.
- You’ve had patches accepted into WebRTC.
- You read the discuss-webrtc mailing list.
Big projects you’re likely to work on
- Bringing multiway calls to Tuple. Our app currently supports up to three people on a call, but our customers want to invite even more folks to their pairing sessions. We’d like your help setting up the media server infrastructure and tuning WebRTC for this use-case.
- Finding perf wins that reduce our CPU usage and remove latency.
- Maybe someday: rewriting portions of the RTC pipeline from scratch to make it even better at low-latency screen sharing.
Why you might want to work with us
- We're tiny, so there are no layers of bureaucracy to work through. You can have a huge impact here.
- We rarely have meetings.
- You can work remotely, though we need you to have reasonable overlap with Boston's time zone (EST).
- 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 good preparation.
Why you might not want to work with us
- We're still figuring out how we want to run the company, so some processes are missing or unrefined. If you need a lot of structure to thrive, this might not be ideal for you.
- We're a bootstrapped company, rather than VC-backed, so we don't offer equity as part of your compensation. We do have profit-sharing, though.
We're looking for someone great, not someone cheap.
If you're expensive but incredible, we can make it work.
How to apply
Please fill out this Typeform.