How do you hand off designs to engineers so that what ships matches what you intended?

What the interviewer is looking for

• This question tests collaboration & critique. Seeks and gives feedback constructively, works closely with engineers through handoff, and does not get defensive.
• What to bring out: Involves engineers early, documents states and edge cases, stays available during build, and reviews the implementation before release.
• Expect a follow-up like: What do you do when engineering says part of your design is too expensive to build?

Another way it may be asked: You have finished a design and engineers are about to build it. What do you do so the final product looks and works right?

A structure to follow: STAR, with the weight on Action and Result

1. Step 1

   Situation

   One or two sentences: where, when and what was at stake. Pick a real example you were close to.

2. Step 2

   Task

   What you personally were responsible for. Say "I", not only "we", so the collaboration & critique you showed is visible.

3. Step 3

   Action

   The two or three things you did and why you chose them over the alternatives. This should be about half your answer.

4. Step 4

   Result

   What changed, in your own measure of it, and what you would do differently. Only use numbers you can stand behind.

This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.

Common slips

• Describing what the team did without saying what you did.
• Choosing an example with no clear outcome, or one you cannot answer detailed questions about.
• Ending on the action and skipping the result and what you learned.

How to practise it

Write two bullet points for each STAR letter, then say the answer aloud in about two minutes.

Related questions

• Tell me about a time you got tough feedback on a design. How did you respond?
• Walk me through a project in your portfolio, starting with the problem you were solving rather than the screens.
• What are a few things you check to make sure a screen works for people using a screen reader or only a keyboard?
• How do you decide on hierarchy, spacing and type on a busy screen? Walk me through a recent example.
• How do you choose between a quick low fidelity sketch and a detailed interactive prototype?

Browse all questions