← Soreno for PM interviews

Sample report · Product sense

How would you improve Google Maps for tourists?

This is what you get after every mock. It's a real report from Soreno, written for a sample answer we recorded, not a user's.

69 / 100

Fair

PM skills

Goal and users17/20
Pains and prioritization17/25
Solutions and the pick11/20
Success metric and guardrail13/15
Trade-offs and risks11/20

Summary

You established a clear goal, chose a relevant tourist segment, and selected a strong metric for trip-long reliance on Maps. Your proposed day planner addresses a credible user problem and accounts for opening hours and travel time. The main gaps were explaining why this pain outranks the others, comparing alternative solutions, and describing the first-version user experience concretely.

Your weakest PM skill

Solutions and the pick

Offers a few distinct ideas, picks one and says what version one does and leaves out.

In this mock

You committed to a trip mode that plans days around opening hours and travel time, and explicitly excluded social sharing and reviews from version one. However, you did not compare distinct solution options or explain the core first-version workflow, inputs, and outputs when asked about scope.

The report then offers a question that trains this skill, and tracks it across your mocks.

What worked

  • You clarified the objective before suggesting features, then translated the engagement goal into a meaningful success metric.
  • You chose a specific tourist segment and gave a relevant reason for prioritizing it.
  • You identified concrete travel difficulties and committed to one primary problem instead of producing an unconnected feature list.

What to fix

  1. 1. You identify a concrete problem and commit to a solution, but the reasoning behind that priority is underdeveloped. Explain why deciding what to do matters more than the connectivity and language barriers you also identified, for example its frequency and effect on daily reliance on Maps.
  2. 2. The first-version answer specifies exclusions and launch geography, but leaves the actual product scope unclear. I looked for what the traveler inputs, what the planner produces, how the traveler changes the plan, and which planning capabilities are deferred. These details were not provided.
  3. 3. You recognize a meaningful trust risk, but navigation accuracy and opening-hours accuracy are different failure modes. A route can be correct while its destination is closed.

The interview, out loud

Interviewer: How would you improve Google Maps for tourists?

Candidate: Before I start, what is the goal for Google here, and what metrics should I be optimizing for?

Interviewer: The goal is for Google Maps to be the app tourists rely on for their entire trip. We're prioritizing engagement during the trip over revenue for now. Regarding metrics, what would you pick to measure that, and why?

Candidate: I'd measure it by the share of tourist trips where Maps is used on most days. I'll focus on first-time international visitors, because they have the least local knowledge.

Interviewer: What are the biggest pain points for first-time international visitors during their trip?

Candidate: Losing mobile data abroad, not knowing which places are worth their limited time, and transit in a language they don't read. The biggest is deciding what to do with limited time, so I'd build a trip mode that plans each day around opening hours and travel time.

Interviewer: Given a team of about eight engineers for six months, what does the first version of this trip planner look like?

Start your free week

Get your own report on your first PM mock.