The brief.
A US startup builds an all-in-one organizer for busy households: a shared family calendar, smart reminders, to-dos with points and rewards for kids, and a smart grocery list. Everyone in the home gets their own profile with role-based permissions, from parents and children to the nanny or driver, so the family stays in sync without endless messages. The roadmap includes AI features, such as turning a photo of a school flyer into a calendar entry.
It needed an experienced product manager to own the vision, roadmap and execution: working with the founder, the CTO and engineering to turn business and user needs into clear requirements, writing user stories and acceptance criteria, running the backlog, sprint and release planning, and acting as the voice of the customer. The role was remote, full-time on contract, and close to the founders, on a consumer product where a missed reminder or a wrong calendar entry disrupts a real family's day.
- 6+ years in product management, including consumer-facing digital products
- Product strategy, roadmapping, discovery and feature definition
- Requirements, PRDs, user stories and acceptance criteria
- Backlog prioritization, sprint and release planning (Agile, Scrum, Kanban)
- Mobile (iOS and Android) and web products, and the SDLC
- Jira, Confluence or similar
- Clear communication and documentation, working independently with a US team
- Startup or fast-paced experience (preferred)
The funnel.
The problem.
Product manager is a common title with very different jobs behind it. Many profiles came from enterprise, B2B or internal tools, where the user is a business buyer and the roadmap follows contracts. This role needed someone who had owned a consumer mobile and web product, where success depends on everyday usability and retention. Titles could not separate the two; what each candidate had shipped, and for whom, could.
Product thinking, not just process, was the harder filter. Many candidates were strong on Agile ceremonies, Jira hygiene and ticket writing, and less able to show how they had defined a product, chosen what not to build, or changed a roadmap because of what users did. This product has a hard design problem at its center: very different users inside one household, each with their own permissions and habits. How should rewards work for a young child? What should a helper be able to see? The funnel drops from 256 to 26 at the second internal round because that is where we asked.
Working directly with US founders added a third bar: confident writing and speaking, strong documentation, and enough seniority to push back and prioritize rather than wait for instructions, across time zones.
What we did.
We sourced 856 product managers, prioritizing consumer mobile and web experience, screened to 750, and kept 550 after separating real product ownership from adjacent project or program management.
256 reached our first internal round on strategy, roadmapping, requirements writing and Agile practice. The second round was a working conversation: each candidate walked us through a product they had owned and the decisions behind it, and we probed how they would handle the household's multi-user problems. 26 cleared it on product judgment, communication and readiness to work remotely with founders, each scored on its own.
13 candidates reached the client, and the client shortlisted 2 for final consideration.
Where it landed.
The search produced a strong, well-vetted shortlist: 13 interview-ready product managers from 856 profiles, and two finalists the client wanted to take forward. Before an offer was made, the client put the role on hold. In founder-led companies, hiring plans move with priorities, timing and resourcing, and a search can pause for reasons outside it.
Nothing from the search is lost. The calibrated rubric, the interview evidence on all 13 candidates and the two finalists are on file, so if the client reopens the role it restarts from a shortlist, not a job post.
What the client has in hand.
The value of a search is not only the hire. This is what the work left the client with.
Product managers screened on consumer product ownership, product judgment and founder-facing communication.
Candidates the client chose to take forward, ready to re-engage.
856 sourced, 13 presented. Both internal rounds ran on our time, not the founders'.
The rubric and interview notes are on file, so a reopened search starts from candidates, not a job post.
How we ran it.
Brief and calibration
Weighted the rubric to consumer product ownership, product judgment beyond process, and independent work with US founders.
Source and screen
856 profiles to 750, then 550 with real product ownership.
Product round
256 tested on strategy, roadmapping, requirements and Agile practice.
Judgment and client rounds
26 cleared a working session on products they had owned. 13 reached the client and 2 were shortlisted.
What we learned.
Screening for product judgment, not PM vocabulary, gave the client a shortlist it could evaluate with confidence. It also showed that for a role this close to the founder and CTO, the outcome depends on things screening cannot control: priorities, timing and resourcing.
We now confirm the hiring timeline and commitment in more depth at the start of founder-level searches, and hold a short joint calibration with the client after the first few profiles. Both bring a shifting plan to the surface sooner, while there is still time to adjust the search around it.