Question 1
Walk through how you would design the main flow in this posting, from the first sketch to something a team could build.
Approach. Start with the user and the job, then the constraint, then what you cut.
Product designer interview questions from a job description
Map a product designer job description to the portfolio, critique, research, and accessibility questions it is likely to ask.
Matched in your browser from the requirements in the posting and Luna’s interview-question hub. These are practice prompts, not a claim that this wording will be asked.
Requirements in the posting
Product Designer
Design the flows customers use, and stay with them through build.
You will:
- Explore and specify interaction design in Figma, including the prototype you throw away
- Run user research and usability sessions that end in a decision
- Treat accessibility as a design constraint: keyboard, focus, and screen reader, not a final audit
- Hand work to engineering so the important behavior survives
- Collaborate with product and engineering when they push back
We will ask what you cut, and what you refused to cut.
Design the flows customers use, and stay with them through build.
You will:
- Explore and specify interaction design in Figma, including the prototype you throw away
- Run user research and usability sessions that end in a decision
- Treat accessibility as a design constraint: keyboard, focus, and screen reader, not a final audit
- Hand work to engineering so the important behavior survives
- Collaborate with product and engineering when they push back
We will ask what you cut, and what you refused to cut.
Likely questions
Role
Product design
Explore and specify interaction design in Figma, including the prototype you throw away
Question 2
Tell me about a design a partner pushed back on. What did you change, and what did you keep?
Approach. Quote the objection in one line and show the design decision, not the feelings.
Question 3
How do you hand a design to engineering so the important part survives implementation?
Approach. Name the behavior that must not drift and the detail that can.
Role
Accessibility
Treat accessibility as a design constraint: keyboard, focus, and screen reader, not a final audit
Question 4
Which flow in this job has to work with a keyboard and a screen reader, and how would you check it?
Approach. Name the control, the expected announcement, and the check you would do before shipping.
Question 5
Tell me about an accessibility fix that changed the design, not just the markup.
Approach. Describe the user’s block, the design change, and what you gave up to make the action clear.
Question 6
How do you handle a component library that looks fine and fails a basic keyboard pass?
Approach. Say who you would tell, the smallest fix, and what you would not ship while it is broken.
Role
User research
Run user research and usability sessions that end in a decision
Question 7
Who would you talk to before designing the flow in this posting, and what would you not ask them?
Approach. Name the participant and the decision the conversation is allowed to change.
Question 8
Tell me about a study that contradicted the team’s plan. What happened next?
Approach. Say the evidence, who resisted, and the change in the product.
Behavioral
Collaboration
Collaborate with product and engineering when they push back
Question 9
Tell me about a disagreement with someone who did not report to you. What did you do with their objection?
Approach. Name the objection, what you changed, and what you did not. Do not flatten it into “we aligned.”
Question 10
How do you bring a partner along when this posting’s work depends on their team?
Approach. Say the ask, the artifact you left them, and what you refused to take over.
What to prepare
- Bring one flow: the user, the constraint, and the version you threw away.
- Tab through one flow with your eyes off the screen and note the first place focus gets lost.
- Prepare one research finding that changed a design, and one that you did not act on.
- Have one story where someone disagreed and you kept the working relationship.
- Mark the three requirements you cannot yet support with a story.
- Say each answer out loud once, in under two minutes.
Designer postings interview the portfolio against the bullets, not against your whole history. Figma is a tool. The question is the flow: user, constraint, version you threw away. Research bullets become “who did you talk to, and what did you not ask?” Accessibility bullets become a design change, not a contrast plugin.
Cross-functional lines are the critique story: a partner pushed back, you changed something, you kept something. Engineering handoff lines are “what must not drift in implementation.”
Pick one flow from the kind of product in the posting and be ready to narrate the cut. The sample is a product design role on a web app.
Sample job description
The posting below is already in the tool. The questions are the ones its requirements point to. Replace it with a posting you are actually interviewing for.
Related: Airbnb role-specific questions · Frontend interview tips · Apple interview questions