Mid-level
Prepare for the Google UX Designer interview with 4 practice rounds and what each one looks for. Pick any round and an AI interviewer runs it with you at full length, with follow-up questions. Afterwards you’ll see what went well and what to work on next.
Your first round is free. No card needed.
Next: your first round
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 what this round looks for, 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. Our research supports this focus, but it does not establish the exact portfolio-review format.
Suggested approach
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.
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?
Portfolio narrative, Live product design challenge, Interaction craft and critique, and Design collaboration and influence have no full round yet.