Technical interview questions for product managers
Technical questions for product managers test whether you can reason about how a system works and where it strains, at the depth a PM needs. The goal is a clear explanation and a sound trade-off, not code.
Below: what the round tests, the method in short, and 15 practice questions, each with a first move and the outline of a strong answer. All free, no sign-up.
What the interviewer is scoring
- Whether you start from what the system is for, in the user’s terms.
- Whether you can trace the main flow from the user’s action to the result.
- Whether you find where it strains and make a trade-off you can defend.
Watch a mock interview from this round
Grace’s first try, Ava’s pushback, then the stronger answer with its scorecard. The question: What happens when you type a URL into a browser and press Enter?
Read what Ava and Grace say
- Ava:
- I'm Ava. Today I'm interviewing Grace, on how a web page loads.
- Grace:
- Hi, I'm Grace. I'm getting ready for PM interviews.
- Ava:
- What happens when you type a URL into a browser and press Enter?
- Grace:
- Easy. DNS, a load balancer, some microservices, and boom, the page.
- Ava:
- Acronyms. Who is waiting, and where do they feel it?
- Grace:
- The goal, in user terms: the page shows up fast and safely, or the user leaves. Two questions. First visit or repeat? I'll assume first, so nothing is cached. How big is the site? Millions of visits a day, from every continent. The path, as five boxes with an arrow between each. One, DNS: the browser asks a directory for the server's address, and without an answer nothing else starts. Two, connection: browser and server shake hands and agree on encryption. Three, request: the browser asks for the page, and a nearby cached copy answers if there is one, otherwise the main server builds it. Four, download: the browser fetches styles, scripts and images, often dozens of files. Five, it draws the page. Pressure. I pick three. Speed: the handshakes in box two are the slow part, about three round trips before any content, each costing a tenth of a second to a far server. Failure: DNS is a single door, so if it is down the site is unreachable even when the servers are fine. Privacy: the request crosses shared networks, like cafe wifi, so the encryption in box two is what stops snooping. My call is on speed: serve from cached copies near the user, because distance is the delay we can remove. I give up freshness, since a copy can be minutes old, so prices and carts skip the cache. I'd know it worked if load time for far users halves and errors stay flat. If stale pages cause complaints, I shorten the cache time.
- Ava:
- That would score well. A user, a path, and a call with its cost.
The method in short
Technical: Goal, Path, Pressure, Call
- GoalWhat the system is for, in user terms, plus one or two questions about scale or scope.
- PathTrace the main flow from the user’s action to the result, in boxes and arrows, not code.
- PressureWhere it strains. Pick the two or three of scale, speed, failure, cost, abuse and privacy that matter here.
- CallDecide the key trade-off, say what you give up and how you would know it worked.
Example
Photo upload in a social app: the phone shrinks the image and sends it in the background while the post appears at once marked “sending”, trading a rare failed post for an app that feels instant.
Most common mistake
A jargon dump (microservices, queues, a named database) with no user, no flow and no decision. Know everything you say one level deeper than you say it.
15 technical questions to practice
Pick one, answer it out loud on a timer, then open its page to compare with the outline. Start with the warm-ups if this round is new to you. Want a score? Paste your answer into the free answer grader, or answer it out loud with Ava.
Warm-up questions (4)
- What happens when you type a URL into a browser and press Enter?First move: Walk the request in order, from finding the server to drawing the page, and say where a PM would see slowness or failure at each step.
- Explain what an API is to someone who isn't technical.First move: Use one everyday analogy, then ground it in a real product example the listener already uses.
- How would you handle technical debt on your roadmap?First move: Treat technical debt as a product risk with costs you can describe, such as slower releases or more bugs, not as an engineering wish list.
- What's the difference between latency and throughput, and how would each show up for users?First move: Use a highway analogy: latency is how long one car takes to arrive; throughput is how many cars get through per hour.
Standard questions (8)
- What's the difference between REST and GraphQL, and when would a PM care?First move: Explain the difference in how clients ask for data, then tie it to product effects such as mobile speed and how fast teams can ship.
- Explain the difference between SQL and NoSQL databases, and when you'd pick each.First move: Frame it as a trade between strict structure and consistency on one side and flexibility and easy scaling on the other.
- How would you design a URL shortener, at the level a PM needs?First move: Start with requirements and scale (how many links created versus clicked), because reads far outnumber writes and that shapes the design.
- Engineering says a feature will take six months. How do you respond?First move: Get curious before reacting. Ask what drives the estimate, then look for a smaller version that delivers most of the value sooner.
- What is a cache, and what could go wrong if your product relies on one?First move: Define a cache in one sentence, then focus on the product risk: showing users old or wrong data.
- Explain how a third-party login like 'Sign in with Google' works.First move: Describe the flow in user terms first, then name what is passed between the parties and why the app never sees the password.
- Should we build our mobile app natively or with a cross-platform framework?First move: Ask what the app needs: heavy device features and top performance favor native; speed of building for both platforms with a small team favors cross-platform.
- Write a SQL query to find the top 10 customers by number of orders last month, and explain how you would check the result.First move: Say the query in words first: filter orders to last month, group by customer, count, sort, take ten. Then name the traps.
Stretch questions (3)
- How would you design the backend for a photo-sharing app's news feed?First move: Clarify what the feed shows and how fresh it must be, then explain the core choice: build feeds when someone posts, or when someone opens the app.
- How would you design a notification system that sends millions of push alerts without spamming users?First move: Split the problem in two: the plumbing that delivers messages at scale, and the rules that decide whether a user should get a message at all.
- Your checkout went down for an hour. What do you do during the outage and after it?First move: Split your answer into two phases: stabilize and communicate during the outage, then learn and prevent after it.
Common questions about this round
Do product managers get system design questions?
Some companies include a technical or system design round for product managers, and it is more common for technical PM roles. It is pitched at PM depth: what the system does for the user, the main flow, where it strains, and which trade-off you would make.
How do I answer a system design question as a PM?
In four moves. Goal: what the system is for and at what scale. Path: the main flow in boxes and arrows. Pressure: the two or three places it strains, chosen from scale, speed, failure, cost, abuse and privacy. Call: the key trade-off, what you give up and how you would know it worked.
How technical do I need to be?
Enough to explain everything you say one level deeper than you said it. If you mention a queue or a cache, be ready to say what it does and why it helps here. A plain explanation you fully understand beats jargon you can’t defend.
Get all 200 questions as a PDF
Every question in the bank, all seven round types, with its first move, a strong opening, the answer outline and the common mistake.
From PMInterviewKit
One method for each interview round, 88 short lessons to read or watch, 66 worked answers and mock interviews with Ava. The first lesson of every module is free. The full kit is $129 once.