Google · Mid-level
Recommended next: your first attempt
A complete first attempt shows where you stand before any narrow practice starts.
Pick a round to see what it asks of you and where you stand on it.
Learn whether the candidate can explain an end-to-end design decision, their own contribution, collaboration, iteration, and measured outcome.
Change one important constraint and ask what survives.
Probe the weakest assumption and the evidence needed.
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
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
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
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.
A first attempt takes the full 40 minutes.
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.
Worth redoing if you hear something from the recruiter that contradicts this.
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?
Every session saved against this target, newest first. Standings live on the round cards.
Portfolio narrative, Live product design challenge, Interaction craft and critique, and Design collaboration and influence have no attempts yet.