TL;DR
The right answer is not “pick the biggest city,” it is “pick the city where Uber can prove durable demand with the least launch risk.” Interviewers are testing whether you can turn a vague market-entry prompt into a sequence of decisions, not whether you can improvise a growth slogan. In a debrief, the candidate who named one launch city, one wedge, one risk, and one metric usually looked more senior than the candidate who produced a longer answer.
Who This Is For
This is for PM candidates interviewing for Uber strategy, growth, marketplace, or regional expansion roles who can talk fluently about products but lose the room when the prompt becomes open-ended. It also fits senior ICs and APMs who know how to analyze a market but fail to state a crisp judgment when the hiring manager wants a decision, not a tour of possibilities.
What is the interviewer really testing in an Uber PM strategy round?
They are testing your judgment under uncertainty, not your knowledge of ride-hailing trivia. In a real debrief, the hiring manager is asking whether you can narrow a messy problem fast enough to be useful to the business.
I have seen this round collapse in under ten minutes because the candidate treated it like a brand brainstorm. The panel did not want ten city names. They wanted to see whether the candidate could build a decision tree, state assumptions, and defend a launch sequence.
The hidden principle is organizational, not technical. Strategy interviews reward people who reduce ambiguity without pretending the ambiguity is gone. That is why “it depends” is weak, but “it depends, so I would compare these three variables first” is strong.
Not a geography quiz, but a prioritization test. Not a market-sizing exercise, but a sequencing exercise. Not a creativity prompt, but an ownership prompt.
In one Q3 hiring debrief, the strongest feedback on the winner was not that the answer was novel. It was that the candidate made the room feel safer by deciding what mattered first. That is the real signal: not brilliance, but controlled judgment.
How should you structure an answer to an enter a new city question?
Use a three-part answer: define the objective, choose the city, then explain the launch plan. Anything else sounds like a candidate trying to demonstrate knowledge instead of making a decision.
A good structure keeps the round clean. Spend a minute clarifying whether the goal is revenue, density, new-user growth, or strategic presence. Then state the selection criteria, choose one city, and explain what you would do in the first 30, 60, and 90 days.
This is not a feature interview, so do not answer like a product spec. It is not a TAM interview, so do not spend six minutes deriving a spreadsheet. It is not a consulting case, so do not hide behind a deck-shaped narrative. The interviewer wants a decision memo in spoken form.
A practical timing pattern helps. Use about 5 minutes to clarify the business goal, 10 minutes to evaluate cities, 10 minutes to explain the wedge and launch motion, and 5 minutes for risks and metrics. If you spend all 30 minutes on market definition, you have already lost the room.
The strongest answers sound compressed but complete. A weak answer sounds exhaustive but uncommitted. In Uber strategy loops, the hiring manager usually trusts the candidate who narrows the scope, because narrowing is what operators do when capital, headcount, and time are limited.
How do you decide which city Uber should enter first?
Choose the city with the cleanest path to repeatable rides, not the city with the largest headline population. That is the counterintuitive answer most candidates miss.
The wrong instinct is to reach for the biggest market because it feels ambitious. That looks impressive in the abstract and weak in a debrief. A large city with brutal supply constraints, regulatory friction, or intense competitor lock-in can be a terrible first move.
What matters is launchability. I would look for demand density, reliable supply acquisition, manageable regulation, and a clear wedge where Uber can win fast enough to learn. A smaller city with dense airport traffic, commuter corridors, and low operational friction often tells you more about the business than a giant city that eats money before it teaches you anything.
In one hiring discussion, the candidate argued for New York because “the market is huge.” The panel pushed back immediately. The better answer was not the most famous city, but the one where Uber could establish a repeatable operating model and get clean signal in weeks, not quarters.
The deeper insight is that a new city launch is a test of whether the business can create liquidity. Liquidity is not a slide title. It is the practical relationship between rider demand, driver availability, and service reliability. If that loop is weak, the city does not matter.
Not the most famous city, but the most legible city. Not the largest total addressable market, but the fastest path to operational proof. Not a trophy launch, but a learning launch.
If you want to sound sharp, say this directly: “I would choose the city where Uber can win the first 10,000 trips with the least friction and the most learning value.” That sentence sounds like an operator because it reflects tradeoffs, not vanity.
What should your launch plan and metrics look like?
Your launch plan should show how the city becomes operational in the first 90 days. If you cannot describe the first 90 days, you do not have a strategy, you have a destination.
The answer should include one primary goal and a small set of leading indicators. For a city launch, I would usually expect a metric tree around rider activation, driver supply health, match rate or ETA quality, and repeat usage. You do not need a full P&L in the interview. You need evidence that you know what signal looks like.
A good launch plan starts with a wedge. That might be airport rides, downtown commutes, nightlife, or a business-travel corridor. The point is not to cover the entire city on day one. The point is to create a narrow zone where Uber can make the service work well enough to earn expansion.
Then define the operating motion. In a real debrief, I would expect to hear how supply gets seeded, how demand is concentrated, and what breaks first. If the candidate never talks about supply acquisition, the answer is incomplete. If they never talk about guardrails, the answer is naive. If they never talk about customer retention, the answer is cosmetic.
The best candidates do not over-index on one metric. They frame one primary metric and two guardrails. That is enough to show discipline. More than that often means the candidate is hiding behind precision theater.
Not a finance answer, but a learning plan. Not a launch checklist, but an operating thesis. Not “what will the city be worth,” but “how will we know the launch is working.”
The organizational psychology here is simple. Hiring teams trust candidates who can name the first failure mode before it happens. That is what real operators do when they are responsible for a market, not a classroom exercise.
What does a strong debrief-worthy answer sound like?
A strong answer sounds like a decision memo the hiring manager would defend in HC. It is not polished for its own sake. It is defensible.
In one debrief, the hiring manager pushed back because the candidate named twelve cities and tried to keep every option open. The room read that as caution, not sophistication. The better candidate picked one city, explained why it was the best first bet, and then named the second choice and the condition that would flip the decision.
That is the level of judgment Uber interviewers respect. They do not need perfection. They need a line of reasoning that survives pushback. If you can say, “I would start in City A because the supply-demand loop is easier to close, but I would switch to City B if regulation blocked fast entry,” you sound like someone who can operate under pressure.
The best answers also show you understand company context without becoming hostage to it. Uber is not a pure software company, so platform rules, local regulation, supply economics, and city-level behavior all matter. But do not drown the answer in internal jargon. The issue is not whether you know the company’s vocabulary. The issue is whether you can make a good call with incomplete data.
Not jargon, but judgment. Not breadth, but prioritization. Not certainty, but a decision that can be tested.
If you want the answer to land, make it easy for the interviewer to repeat in debrief. If they can summarize your position in one sentence, you have probably done enough. If they need to explain your answer for you, you have not.
Preparation Checklist
You need a repeatable structure, not more raw brainpower. The interview rewards disciplined judgment, and that has to be rehearsed.
- Build a city-selection rubric with five criteria: demand density, supply availability, regulatory friction, competitive pressure, and a plausible wedge.
- Practice answering in two formats: a 5-minute version for clarity and a 15-minute version for pushback.
- Prepare one example where a smaller city beats a larger city, because that is the counterintuitive move interviewers remember.
- Write a simple 30/60/90-day launch plan with one primary metric and two guardrails.
- Work through a structured preparation system (the PM Interview Playbook covers city prioritization, marketplace sequencing, and debrief-style signal reading with real debrief examples).
- Rehearse two explicit “not X, but Y” contrasts so your answer sounds like a decision, not a list.
- Prepare one assumption flip, such as what changes if regulation tightens or supply acquisition gets harder than expected.
Mistakes to Avoid
The same three failures show up again and again. They are easy to spot in the interview and expensive in the debrief.
- BAD: “I would start in the biggest city because it has the most users.”
GOOD: “I would start in the city where Uber can create liquidity fastest and learn the operating model with the least friction.”
- BAD: “I would improve the app, run promotions, and expand awareness.”
GOOD: “I would choose one launch wedge, seed supply, measure service quality, and only then expand the city footprint.”
- BAD: “It depends on too many factors.”
GOOD: “It depends on three factors first, so I would rank them by launch risk and reversibility.”
The pattern matters more than the wording. Weak candidates answer with nouns. Strong candidates answer with tradeoffs. Weak candidates hide behind completeness. Strong candidates make a choice and name the cost of that choice.
FAQ
- Is the best answer always the biggest city?
No. The better answer is usually the city with the clearest path to liquidity and the fastest learning loop. Big markets can hide weak execution because the baseline demand is so large.
- How much math do I need in this round?
Enough to prove you can think in metrics, not enough to turn the interview into a spreadsheet. A simple metric tree and a few directional assumptions are enough if the logic is clean.
- Should I mention Uber-specific facts like airports, regulation, or driver supply?
Yes, but only to support the decision. The point is not trivia. The point is showing that you understand what actually makes a city launch work or fail.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.