Company
David AI
Annual salary
$145k – $225k/yr
Location
San Francisco Bay Area, CA
Listed
30d ago
- Experience:
- 2 to 8 years
- Workplace:
- On-site in the San Francisco Bay Area or New York City; no relocation support
- Equity:
- Competitive equity
Open to people who live in the US, Canada or the UK
We can only put candidates forward for this role from those three countries for now. See the contract AI training jobs open in more countries.
On-site in San Francisco Bay Area, CA.
Send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role.
Apply for a referral →The recruiter emails you before anything happens and may suggest other jobs that suit you better.
About this role
We are looking for a Technical Product Manager with 2-8 years of experience to own a core part of David AI's Data Factory, the systems that turn raw audio into high-quality AI training data. We want a builder who has both technical and operational experience: someone who can run complex operations, automate them, and build the first MVP themselves. You'll help solve the training data bottleneck for FAANG companies and leading AI labs.
What you need
- Undergraduate degree in Computer Science or another technical STEM field from a top US or Canadian program
- 2-8 years as a product manager, technical program manager, founder, forward deployed engineer, or technical operator. Candidates with only PM or only SWE experience aren't a fit
- Highly proficient in SQL and able to build lightweight prototypes end-to-end
- Track record of building your own tools in operationally complex roles at a startup, in consulting, or in operations
- Able to work on-site in the SF Bay Area or NYC (no relocation support)
What will you be doing?
- Own the strategy and roadmap for your area of the Data Factory, from first prototypes to production systems running at scale. Your area could be the contributor marketplace, Ops infrastructure, a new business unit, or the systems the ML team relies on.
- Build the first version yourself (SQL queries, scripts, dashboards, prototypes), then work with engineering to scale it.
- Turn the model capabilities customers care about into concrete workflows, requirements, and project plans.
- Work across Operations, Engineering, and Research to take new systems from idea to deployment.
- Use data to make decisions and track throughput, quality, and cost.
Common questions
How do I apply for the Technical Product Manager (US) role at David AI? +
Use the Apply for a referral button on this page to send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role. They'll email you to check you're interested, then put you forward for this job or others that suit you better. It's free.
What does this David AI role pay? +
The listing gives $145k – $225k/yr.
Is this role remote? +
The listing gives the location as San Francisco Bay Area, CA. On-site in the San Francisco Bay Area or New York City; no relocation support.
Product Manager interview prep
Questions Product Manager interviewers often ask. They aren't taken from this listing.
How do you rank competing feature requests when every stakeholder believes theirs is the most urgent one on the list?
I score each request against the outcome the team has committed to for the quarter, then weigh expected impact against the effort engineering estimates. That gives me a defensible order to show stakeholders, and when someone disagrees we argue about the inputs rather than about whose request matters more.
How do you structure a roadmap so it communicates direction without promising dates the team cannot keep?
I organize the roadmap around problems to solve in rough time horizons, now, next and later, instead of a dated list of features. Commitments get firmer as work gets closer, and I state plainly which items are bets and which are committed, so sales and leadership know what they can promise to customers.
How do you plan a round of user interviews so the findings change what you build rather than confirming what you hoped?
I write the riskiest assumption down first and design questions around past behavior, not opinions about a feature idea. Asking people what they did last time the problem came up produces evidence, while asking whether they would use something produces polite agreement that tells me nothing.
How do you combine quantitative usage data with qualitative interview findings when the two seem to disagree?
I treat the numbers as telling me what is happening and the interviews as telling me why, so a disagreement usually means I am measuring the wrong thing or talking to the wrong segment. I go back and check who is in each sample before drawing a conclusion, because resolving that mismatch is often the most useful finding of the whole study.
Related roles
Browse all referral roles
Salaried roles at startups, AI companies and established businesses, all filled by referral. One application covers every role.
See all referral roles →