Team Lead, Android Core Product
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not invent or summarize away detail. Preserve all substantive info.
We need to extract responsibilities list: bullet points under "What You'll Do". Let's list them:
- 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
- Call it when the team is ready to change how it works, rather than waiting for that to happen on its own
- Reduce how much manual intervention it takes to get a correct release out
- When the same problem shows up twice, get the underlying setup changed so there isn't a third time
- Shift verification left: grow what can be checked automatically so the nightly build going to QA is a confirmation rather than the first time anyone finds out
- Run planning so the team's attention goes to the work that still needs decisions rather than the work that's already clear
- Work out how much review each area needs, and where a person always signs off regardless
- Participate in discussions across Product, Design, and Engineering, and bring the team's constraints into those rooms early
- Handle critical issues, own feature releases, and provide nightly builds for the QA team
- Make sure the people early in their careers are getting work they can learn from, and the time to learn from it
- Some of your engineers will be skeptical about parts of how the team is asked to work. In our experience that skepticism tends to be specific and worth acting on, and the people raising it are often the right ones to hand the underlying problem to.
That's a lot; we need to keep them as list items.
Now Requirements/Qualifications: "An Ideal Candidate Should Have" list:
- 5+ years of software engineering experience, including time leading a team or owning a major surface while staying hands-on
- Rock solid Kotlin, Kotlin Coroutines, Kotlin Flow, Dagger 2, MVVM, Clean Architecture, Background Services, Music Player Service, Android animations, Jetpack Navigation, and JUnit tests
- Experience shipping and maintaining background audio or other long-running background work
- Understanding of the importance of tests and how to approach writing them, including what can't be covered by them
- Something you introduced to a team that stuck after you stopped pushing it, and an honest account of what it cost to get there
- Some comfort with the unpopular half of the job: asking people to change how they work, and living with the friction that follows
- A view on which changes need heavy review and which don't, argued from what the system does
- A track record of building things the rest of your team actually used, not only things that made you faster
- The ability to describe how your team works with AI agents, not only how you do personally
- Product design intuition, user empathy, and the drive to push Android UI/UX further than the spec asks for
- Self-drive to improve the app and codebase beyond what's outlined in the spec
- Excellent communication skills
- Bonus: Building, maintaining, or contributing to open source Android projects
- Bonus: Experience with iOS, Web, or NodeJS
We may separate Requirements (must-have) and Qualifications (nice-to-have) or Skills. The instruction: sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where.
We can treat "An Ideal Candidate Should Have" as Requirements (must-have) and the bonus as Qualifications or Skills. But we also have a list of technologies used: "Technologies we use Kotlin Kotlin Coroutines Kotlin Flow Jetpack Navigation Dagger 2 Room Custom Views, Canvas & Paint Jetpack Compose JUnit". That's Skills.
Thus:
- About the role: include mission overview and maybe the opening paragraph about role? Could combine mission and overview. We'll put a prose paragraph describing the role and company.
- Responsibilities: list of duties from "What You'll Do".
- Requirements: the core requirements (first bullet points up to "Excellent communication skills") maybe treat as Requirements.
- Qualifications: the bonus items (open source, iOS/Web/NodeJS experience) maybe as Qualifications.
- Skills: the technologies list.
We must not create sections with placeholder text. Ensure each section has real content.
Now produce HTML fragment.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- Building, maintaining, or contributing to open source Android projects
- Experience with iOS, Web, or NodeJS
Skills
- Kotlin
- Kotlin Coroutines
- Kotlin Flow
- Jetpack Navigation
- Dagger 2
- Room
- Custom Views, Canvas & Paint
- Jetpack Compose
- JUnit
We need to ensure we preserve all substantive info: also mention that it's remote, 100% distributed, no office. That could be in About the role.
Also mention awards: Google Chrome Extension of the Year, Apple Design award winner for inclusivity 2025. Also mention team size ~200, includes engineers from Amazon, Microsoft, Google, Stanford, Stripe, Vercel, Bolt, founders.
Include that the Android app is most used text-to-speech app in Play Store, user base grew faster than we build for it.
Include mission statement: "make sure that reading is never a barrier to learning." Over 50 million users, products list.
We need to include all that in About the role.
Let's craft About the role paragraph:
Speechify’s mission is to make sure that reading is never a barrier to learning. Over 50 million people use its text‑to‑speech products (iOS app, Android app, Mac app, Chrome extension, web app) to turn PDFs, books, Google Docs, news articles, websites into audio so they can read faster, read more, and remember more. Google named Speechify the Chrome Extension of the Year and Apple awarded it the Design award for inclusivity in 2025. The company is fully remote with nearly 200 people worldwide, including engineers from Amazon, Microsoft, Google, PhD programs like Stanford, high‑growth startups such as Stripe, Vercel, Bolt, and many founders. Its Android app is the most used text‑to‑speech app in the Play Store, and the user base has grown faster than the team’s ability to build for it. Speechify is seeking a Team Lead to own core product work and elevate how the team works around it.
That seems comprehensive.
Now Responsibilities list: we need to include each bullet as separate - . Ensure we keep the exact phrasing? We should preserve substance but can trim minor filler? The instruction: do NOT invent or summarize away detail. So we should keep the substance, but we can rephrase slightly as long as we keep meaning. Safer to keep close to original.
Let's list them exactly as bullet points:
- 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
- Call it when the team is ready to change how it works, rather than waiting for that to happen on its own
- Reduce how much manual intervention it takes to get a correct release out
- When the same problem shows up twice, get the underlying setup changed so there isn't a third time
- Shift verification left: grow what can be checked automatically so the nightly build going to QA is a confirmation rather than the first time anyone finds out
- Run planning so the team's attention goes to the work that still needs decisions rather than the work that's already clear
- Work out how much review each area needs, and where a person always signs off regardless
- Participate in discussions across Product, Design, and Engineering, and bring the team's constraints into those rooms early
- Handle critical issues, own feature releases, and provide nightly builds for the QA team
- Make sure the people early in their careers are getting work they can learn from, and the time to learn from it
- Some of your engineers will be skeptical about parts of how the team is asked to work. In our experience that skepticism tends to be specific and worth acting on, and the people raising it are often the right ones to hand the underlying problem to.
We'll put each as
- .
Now Requirements list: we need to include each bullet from "An Ideal Candidate Should Have" except the bonus items.
List:
- 5+ years of software engineering experience, including time leading a team or owning a major surface while staying hands-on
- Rock solid Kotlin, Kotlin Coroutines, Kotlin Flow, Dagger 2, MVVM, Clean Architecture, Background Services, Music Player Service, Android animations, Jetpack Navigation, and JUnit tests
- Experience shipping and maintaining background audio or other long-running background work
- Understanding of the importance of tests and how to approach writing them, including what can't be covered by them
- Something you introduced to a team that stuck after you stopped pushing it, and an honest account of what it cost to get there
- Some comfort with the unpopular half
for prose. We must not invent or summarize away detail. Preserve all substantive info. We need to extract responsibilities list: bullet points under "What You'll Do". Let's list them: - 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 - Call it when the team is ready to change how it works, rather than waiting for that to happen on its own - Reduce how much manual intervention it takes to get a correct release out - When the same problem shows up twice, get the underlying setup changed so there isn't a third time - Shift verification left: grow what can be checked automatically so the nightly build going to QA is a confirmation rather than the first time anyone finds out - Run planning so the team's attention goes to the work that still needs decisions rather than the work that's already clear - Work out how much review each area needs, and where a person always signs off regardless - Participate in discussions across Product, Design, and Engineering, and bring the team's constraints into those rooms early - Handle critical issues, own feature releases, and provide nightly builds for the QA team - Make sure the people early in their careers are getting work they can learn from, and the time to learn from it - Some of your engineers will be skeptical about parts of how the team is asked to work. In our experience that skepticism tends to be specific and worth acting on, and the people raising it are often the right ones to hand the underlying problem to. That's a lot; we need to keep them as list items. Now Requirements/Qualifications: "An Ideal Candidate Should Have" list: - 5+ years of software engineering experience, including time leading a team or owning a major surface while staying hands-on - Rock solid Kotlin, Kotlin Coroutines, Kotlin Flow, Dagger 2, MVVM, Clean Architecture, Background Services, Music Player Service, Android animations, Jetpack Navigation, and JUnit tests - Experience shipping and maintaining background audio or other long-running background work - Understanding of the importance of tests and how to approach writing them, including what can't be covered by them - Something you introduced to a team that stuck after you stopped pushing it, and an honest account of what it cost to get there - Some comfort with the unpopular half of the job: asking people to change how they work, and living with the friction that follows - A view on which changes need heavy review and which don't, argued from what the system does - A track record of building things the rest of your team actually used, not only things that made you faster - The ability to describe how your team works with AI agents, not only how you do personally - Product design intuition, user empathy, and the drive to push Android UI/UX further than the spec asks for - Self-drive to improve the app and codebase beyond what's outlined in the spec - Excellent communication skills - Bonus: Building, maintaining, or contributing to open source Android projects - Bonus: Experience with iOS, Web, or NodeJS We may separate Requirements (must-have) and Qualifications (nice-to-have) or Skills. The instruction: sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. We can treat "An Ideal Candidate Should Have" as Requirements (must-have) and the bonus as Qualifications or Skills. But we also have a list of technologies used: "Technologies we use Kotlin Kotlin Coroutines Kotlin Flow Jetpack Navigation Dagger 2 Room Custom Views, Canvas & Paint Jetpack Compose JUnit". That's Skills. Thus: - About the role: include mission overview and maybe the opening paragraph about role? Could combine mission and overview. We'll put a prose paragraph describing the role and company. - Responsibilities: list of duties from "What You'll Do". - Requirements: the core requirements (first bullet points up to "Excellent communication skills") maybe treat as Requirements. - Qualifications: the bonus items (open source, iOS/Web/NodeJS experience) maybe as Qualifications. - Skills: the technologies list. We must not create sections with placeholder text. Ensure each section has real content. Now produce HTML fragment. Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- Building, maintaining, or contributing to open source Android projects
- Experience with iOS, Web, or NodeJS
Skills
- Kotlin
- Kotlin Coroutines
- Kotlin Flow
- Jetpack Navigation
- Dagger 2
- Room
- Custom Views, Canvas & Paint
- Jetpack Compose
- JUnit
Speechify’s mission is to make sure that reading is never a barrier to learning. Over 50 million people use its text‑to‑speech products (iOS app, Android app, Mac app, Chrome extension, web app) to turn PDFs, books, Google Docs, news articles, websites into audio so they can read faster, read more, and remember more. Google named Speechify the Chrome Extension of the Year and Apple awarded it the Design award for inclusivity in 2025. The company is fully remote with nearly 200 people worldwide, including engineers from Amazon, Microsoft, Google, PhD programs like Stanford, high‑growth startups such as Stripe, Vercel, Bolt, and many founders. Its Android app is the most used text‑to‑speech app in the Play Store, and the user base has grown faster than the team’s ability to build for it. Speechify is seeking a Team Lead to own core product work and elevate how the team works around it.
That seems comprehensive. Now Responsibilities list: we need to include each bullet as separate