Working with developers: how to demonstrate design preparation and collaboration

Designer–developer collaboration begins before mockups are handed over. Show how you clarify behaviour, discuss constraints and follow decisions through to reviewing the implemented interface.

1. Prepare useful information

Group selected screens, components, states, content rules and behaviour at different widths. Identify open decisions. A final screen without empty, error or loading states leaves important questions unanswered.

2. Document one component

3. Explain a discussion that changed the design

Fictional situation: a developer explains that the data service does not provide an availability status. You revisit the need, propose a version without that indicator and record when to reconsider it.

Explain the compromise, who approves it and what still needs checking with users.

4. Track decisions and discrepancies

Record the question, decision, reason, owner and date. When reviewing implementation, describe an observable issue, its impact and expected behaviour. Instead of “it looks wrong”, explain that a long title hides the action on a small screen.

5. State your actual contribution

CV wording, if accurate: “UX/UI internship: prepared form states, annotated behaviour and participated in developer reviews under the supervising designer’s approval.”

If you worked alone, label the file as a development-preparation exercise rather than inventing collaboration. Include an annotated specification and one decision record in the portfolio.

Illustrative stock photos; the people shown are not presented as Kamerjob employers. Cover and illustration: Pexels / Pexels.

Find opportunities on Kamerjob and tailor your portfolio to the actual duties in each vacancy.

The Kamerjob team