Role guide and interview toolkit

Technical Product Manager

What the work looks like, the products behind the title, what each level means and the training that helps, then how interviews run and how to prepare for each step.

APIs·Developer platforms·Data products·System design·SQL·OpenAPI
See open jobs Back to the role map
The role in practice

What a technical product manager actually does

A product manager for technical products, whose users are often developers, data teams or other engineering teams.

The work

A technical product manager is responsible for products where the technology is the product itself: APIs, developer platforms, data products or infrastructure. They decide what the team builds and why, like any product manager, with users who are often engineers.

The role asks for real technical depth. Technical product managers understand the architecture well enough to discuss trade‑offs with engineers, read code or API specs when needed, and query the data with SQL.

They write clear specs and technical roadmaps, and they follow the adoption of their product by developers once a feature is live.

A typical week
  • A design review with engineers on a new API or feature
  • Interviews with developers who use the product
  • Writing or updating a spec or an API contract
  • A review of usage and adoption metrics
  • A roadmap discussion with engineering leads
TPM, two roles behind the same letters

At large tech companies such as Google and Amazon, TPM often means Technical Program Manager, a role that runs complex programs across several engineering teams. Amazon uses the title Product Manager, Technical for the role in this guide.

Read the job ad closely: a technical product manager decides what to build and why, while a technical program manager plans and coordinates how and when it gets delivered.

Often confused with
Technical Program ManagerPlans and coordinates complex programs across engineering teams, with the delivery as the main goal.
Product ManagerOwns a product for business or consumer users, with less technical depth expected.
Solution ArchitectDesigns the technical solution for a client or a project, often on products built by other companies.
Engineering ManagerLeads a team of engineers and owns how the team builds, while the product manager owns what it builds.
Focus areas and tools

The same title, very different products

Most technical product manager searches are defined first by the type of technical product the company builds, then by the ground every technical product manager shares.

Developer platforms and APIsUsersDevelopers · PartnersTypical workAPIs · SDKs · Documentation
Data productsUsersData teams · AnalystsTypical workPipelines · Connectors · Quality
Infrastructure productsUsersEngineering teamsTypical workReliability · Scale · Costs
Technical skillsSystem design, APIs
DataSQL, adoption
RoadmapsTechnical roadmaps
SpecsSpecs, API contracts
ToolsJira or Linear, OpenAPI
Levels

What each level means in practice

Titles vary from one company to the next. What changes from one level to the next is the scope you own and the decisions you take.

01Associate
  • Works on a part of the product with a senior product manager
  • Learns the architecture, the users and the team
  • Writes specs with review and guidance
02Product Manager
  • Owns a technical product area end to end
  • Sets priorities with the engineering lead
  • Measures adoption by developers
03Senior
  • Owns a platform or a product used by many teams
  • Shapes the technical roadmap with architects
  • Mentors other product managers
04Group and Principal
  • Group product managers lead a team of product managers
  • Principal product managers own the most complex platforms
  • Sets the product strategy across several teams
Education and certifications

The paths into the role, and what really counts

Companies look first at the technical products you have shipped and how developers adopted them. Education and certifications help most early in a career, or to change field.

Common paths
  • Engineering school or master's in computer scienceThe most common path in France, and often expected for this role.
  • University degree in computer scienceThe most common path in the US, at bachelor's or master's level.
  • Software engineering firstMany technical product managers start as engineers before moving to product.
  • Product management with a technical scopeProduct managers who worked on APIs or platforms also move into the role.
Certifications
AWS, GCP or Azure certificationsSometimes askedUseful for infrastructure and cloud products, where you discuss architecture with engineers.
PSPO or CSPORarely decisiveScrum certifications help in teams that run Scrum, and companies look more at your technical depth.
Pragmatic InstituteRarely decisiveA product management certification with several levels, delivered through paid courses.

Our view: for this role, a technical product you shipped and can explain to engineers, from the architecture to adoption, often says more than any certificate.

Your interview with us

A conversation with a senior tech recruiter

Your first interview is with one of our senior tech recruiters, who knows the role, the products and the levels in this guide. The conversation covers your own work through real examples, and the product and technical cases come later, with the company. Before the call, we send you the six themes we will cover so you can prepare your examples.

The six themes we share before the call
  1. What you owned yourselfThe APIs, platforms or technical products you were responsible for, and your own part in the team's decisions.
  2. Your environment and its constraintsYour users, the architecture, technical debt, security rules or deadlines: what shaped your choices.
  3. The decisions you madeWhat to build first and what to plan for later, the technical options you compared and the reasons for your choice.
  4. The impact of your workWhat changed thanks to your work, with numbers when you have them: adoption, API calls, time saved or incidents.
  5. How you work with other teamsYour work with engineers, architects, design and customers, and how you settle a disagreement.
  6. What you want nextThe kind of technical product, users and scope you are looking for in your next role.
What we look at
  • Technical credibility with engineers
  • Roadmaps for platforms or APIs
  • Clear written specs
  • Adoption by developers

The same ground for every candidate. For a given role, every candidate answers the same final questions, built with the hiring manager around what the role really needs.

Ready for the next steps. After our call, we tell you how the company runs its interviews, who you will meet at each step and what each step is meant to assess.

Interviews with the company

What the company will assess, step by step

Each company runs its own process, and we walk you through its steps before you start. Technical product manager processes often combine the steps below, and the depth expected at each step grows with your level.

The steps you will often meet
  1. A technical product caseA technical product to design or improve, such as an API or a platform feature, and how you frame the users, the problem and the priorities.
  2. A technical discussionA system design or architecture discussion with engineers, at the level a product manager needs to take good decisions.
  3. A deep dive on a product you shippedOne technical product you owned, discussed in depth: the users, your decisions, the trade‑offs and the adoption.
  4. Meeting engineering leads and the managerHow you work with engineers day to day, how you take decisions with them and what the team expects in your first months.
What changes with your level
  • Product ManagerYou frame the problem clearly, ask the right questions about the users and explain each technical choice in simple words.
  • SeniorYou lead the discussion, weigh the technical trade‑offs with engineers and point out risks before you are asked.
  • Group and PrincipalYou run most of the interview as a peer, link the case to the platform strategy and show how you align several teams.
Your interview toolkit

How to prepare as a technical product manager

Practical advice for each step of a technical product manager process, from the way you introduce yourself to the questions you ask at the end of each interview.

01Introduce yourself in two minutes

Start with the technical products you worked on, their users and your part in them. Mention your technical background in one sentence, then close with what you want next.

02Prepare two technical products

For each one, prepare the users, the architecture, your decision, the options you set aside, the result and what you would change today. Say "we" for the team and "I" for your own part.

03Know your architecture

Interviewers often ask you to draw the system behind your product. Practise drawing it in five minutes, with the main components and the data flows.

04Start a case with the users

In a technical product case, ask who the developers or teams are, what they need and how they will use the product before you propose anything.

05Explain trade‑offs simply

Prepare one technical trade‑off you made with engineers and explain it in plain words, as you would to a business leader.

06Check the rules on AI tools

Rules on AI tools differ from one company to the next, especially for take-home cases. Ask before each step, and when they are allowed, explain what you asked the tool and how you checked its output.

Questions you will often hear
  • Walk us through the architecture of a product you owned.
  • How do you decide between building a feature and opening an API for it?
  • How do you measure the adoption of a developer product?
  • Tell us about a disagreement with engineering on a technical choice, and how you settled it.
Questions worth asking them
  • Who are the main users of the product: developers, data teams or other teams?
  • How do product and engineering share the technical decisions?
  • How does the team measure adoption and developer experience?
  • How much technical depth do you expect in specs and design reviews?
  • How does the roadmap balance new features and platform work?
  • How does the team use AI tools in product work?
Where the role leads

Where technical product managers come from, and where they go

The roles people most often hold before this one, and the ones they most often move to.

See open jobs Join our community