Team Lead

Remote

The mission of Speechify is to make sure that reading is never a barrier to learning.

Over 50 million people use Speechify's text-to-speech products to turn whatever they're reading – PDFs, books, Google Docs, news articles, websites – into audio, so they can read faster, read more, and remember more. Speechify's text-to-speech reading products include its iOS app, Android App, Mac App, Chrome Extension, and Web App. Google recently named Speechify the Chrome Extension of the Year and Apple named Speechify its Design award winner for inclusivity for 2025.

Today, nearly 200 people around the globe work on Speechify in a 100% distributed setting – Speechify has no office. These include frontend and backend engineers, AI research scientists, and others from Amazon, Microsoft, and Google, leading PhD programs like Stanford, high growth startups like Stripe, Vercel, Bolt, and many founders of their own companies.

Overview

Our Android app is the most used text-to-speech app in the Play Store, and the user base has grown faster than the way we build for it. We're looking for a Team Lead to own core product work and to raise how the team works around it.

This is a hands-on role, and we want to be clear about the split. You'll be writing code, reviewing code, and owning features of your own — that doesn't shrink when you take this job. The rest of it is the part that doesn't happen on its own: catching when three people have solved the same problem separately, deciding which version everyone should use, and making sure the team's time goes to the work that actually needs a decision. If you want to stop building, this isn't the role. If you want the code you write to be the smaller half of your impact, it is.

We are a flat organization that allows anyone to become a leader by showing excellent technical skills and delivering results consistently and fast. Work ethic, solid communication skills, and obsession with winning are paramount.

What You'll Do

• Own major features end to end, working closely with our design team — from the decision through to release. This is real delivery, not oversight
• Own, maintain, and improve reliability metrics for key features
• Review pull requests and give the kind of feedback people learn from, not just approval
• Unblock the team: notice when someone has been stuck on the same thing for two days, and go take a look yourself
• Notice when something one person built should become the version the team uses, and see that change through
• Keep the shared pieces in working order — tested, clear enough for someone else to pick up, and consolidated when three versions of the same thing appear