RoundHound
?Sign inAccess
Prepare
HomeHomeTargetsTargetsPractice historyHistoryProgressProgress
Get full access?Sign in
Targets/Google

UX Designer

Google · Mid-level

Research from Sep 64 rounds, none tried
How did it actually go?

Recommended next: your first attempt

Do the Portfolio narrative round.

A complete first attempt shows where you stand before any narrow practice starts.

Set up this round →Rehearse the full day
Length40 min · Mid-level

The loop

4 rounds · 2 h 40 min

Pick a round to see what it asks of you and where you stand on it.

Portfolio narrative

Learn whether the candidate can explain an end-to-end design decision, their own contribution, collaboration, iteration, and measured outcome.

Portfolio review · 40 minSet up this round →
Not tried yetNo attempt yet.

What strong sounds like

  • Explain the users, stakes, constraints, and why the problem deserved attention.
  • Distinguish the candidate's decisions and artifacts from the team's work.
  • Connect research or critique to a material design change and explain the rejected alternatives.
  • Give a concrete outcome, limitation, and what would be measured next.

Expect to be pushed on

Change one important constraint and ask what survives.
Probe the weakest assumption and the evidence needed.

Shapes of problem you may get

  • A verbal portfolio walkthrough of one complex shipped project and one sharply different project

How to prepare

  1. 01
    Select two contrasting projects

    Choose one complex shipped project and one sharply different project. Gather evidence for the user problem, stakes, constraints, your decisions, rejected alternatives, collaboration, outcome, limitation, and next measure.

    Google’s official guidance asks for three to five end-to-end case studies with role, collaboration, rationale, and impact. This round requires enough detail without relying on memorized slides.

    Company researchGoogle UX design portfolio tips

  2. 02
    Rehearse the governing decision

    Write one sentence for the governing decision in each project. Briefly explain how research or critique changed the design, which alternative you rejected, and what evidence supported the choice.

    The round values traceable design reasoning and explicit personal contribution. This is a preparation recommendation based on the supplied bar, not a confirmed Google interview requirement.

    Suggested approach

  3. 03
    Prepare an evidence map

    Create a small note for each project that separates team work from your work. Include shipped impact, uncertainty in the evidence, an unresolved risk, and what you would measure next.

    Clear ownership and measured impact matter at mid-level. The supplied research supports this focus, but it does not establish the exact portfolio-review format.

    Suggested approach

Then try the round

You have selected two projects and can point to the decision, your contribution, one material design change, its evidence, and the next measure for each.

Do

  • State the governing decision before adding detail.
  • Use concrete evidence and make trade-offs explicit.
  • Close with the action, measure, and unresolved risk.

Avoid

  • Do not substitute a memorized framework for the supplied facts.
  • Do not hide personal decisions behind vague team language.
  • Do not claim certainty beyond the evidence available.

A first attempt takes the full 40 minutes.

What this loop tests

Researched 27 days ago

Prepare a concise portfolio narrative, a live end-to-end design challenge, craft critique, and collaboration examples. Google’s current mid-level interaction-design postings emphasize user-centered methods, flows, prototypes, design systems, experimentation, and cross-functional work. Candidate evidence supports portfolio and challenge formats, but much of the detailed public reporting is internship-level, so confirm the exact mid-level schedule with the recruiter.

They reward

  • User-centered evidence
  • Clear ownership of design decisions
  • End-to-end interaction quality
  • Rapid learning through prototypes
  • Constructive cross-functional challenge

What to avoid

  • Do not substitute a memorized framework for the supplied facts.
  • Do not hide personal decisions behind vague team language.
  • Do not claim certainty beyond the evidence available.

How sure we are

Worth redoing if you hear something from the recruiter that contradicts this.

Confirmed · 4
  • Google's official portfolio guidance asks for three to five case studies showing end-to-end process, role, impact, collaboration, and design rationale.
  • A current mid-level Interaction Designer posting requires a portfolio and emphasizes user-centered design, cross-functional collaboration, prototypes, and design systems.
  • Recent internship candidates describe two 45-minute interviews and report a live design challenge alongside portfolio expectations.
  • Google's virtual interview guide explicitly anticipates diagramming for some UX interviews.
Likely · 2
  • A defensible mid-level practice loop should evaluate portfolio storytelling, live design reasoning, craft critique, and collaboration without assuming internship timing transfers exactly.
  • The strongest practice bar is a traceable chain from user problem through alternatives and iteration to shipped impact, with the candidate's own contribution explicit.

Worth asking them

Questions that close the gaps above.

Which project should the portfolio walkthrough prioritize for this team?
Will the loop include live diagramming, critique, or another functional exercise?
How does this team evaluate mid-level craft versus design leadership?

Research status

Collected Sep 6. If the recruiter tells you something this brief contradicts, correct it after the interview and the brief updates.

Correct this brief

Attempts

Every session saved against this target, newest first. Standings live on the round cards.

All attempts in History →

Portfolio narrative, Live product design challenge, Interaction craft and critique, and Design collaboration and influence have no attempts yet.