Company
Asha Health (YC F24)
Annual salary
$180k – $347k/yr
Location
New York, NY
Listed
35d ago
- Experience:
- 3 to 6 years
- Workplace:
- 5 days in-office in Manhattan, New York
- Equity:
- 0.5-1.25%
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 New York, NY.
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're looking for a Head of Product, AI to lead our currently (and hopefully always) small engineering team. The twist: you’ll also be coding & building every day. Let us explain ~
As AI models evolve, engineering, product management, and design are all changing. We believe old job descriptions should be completely tossed out the door. The future belongs to “builders”: people that are strong engineers, but essentially act as their own PM’s, designers, and user researchers. They talk to customers, decide what to build, how to build it, and have the highest bar for product & UX “taste”.
As Head of Product, AI you will call the shots - talk to customers, decide what we build, why we build it, and how we build it. You will lead an engineering team (of both humans & agents). However, you will also be an IC building a lot yourself. Why?
Now, more so than ever, it is impossible to be good at product without being deep, hands on building AI products using AI products every day. You have to be deep in the weeds if you want to call the shots.
The era of middle management is gone. With the power of AI, the next generation of product leaders will drive impact through both people and agents, master both breadth & depth over vast amounts of product surface area, and earn their influence through not just their ideas but what they build.
What you need
- Graduated with a bachelors in computer science or related degree.
- At least 2 years of software engineering experience in industry.
- (Preferred) at least 1 year of experience as a Product Manager.
- Strong engineering experience AND PM experience. Asha is building an AI operating system for outpatient care. Demand is ahead of what the team can deliver, contracted ARR is piling up, and engineering is the #1 lever for growth. This is a bet on an ambitious builder, not a seasoned 10+ YOE product leader, who is ready to step up and possibly lead a team for the first time.
What will you be doing?
Talking directly to customers and deciding what to build, why to build it and how to build it
Coding and shipping AI products end-to-end every day as a hands-on IC
Leading a small, high-ownership engineering team made up of both humans and AI agents
Owning the product roadmap and the bar for product and UX "taste" across a large product surface
Working side by side with the CEO, CTO and CMO every day to turn contracted ARR into shipped product
Common questions
How do I apply for the Senior AI Product Manager (US) role at Asha Health (YC F24)? +
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 Asha Health (YC F24) role pay? +
The listing gives $180k – $347k/yr.
Is this role remote? +
The listing gives the location as New York, NY. 5 days in-office in Manhattan, New York.
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 →