Interview scorecard
UI Designer
Score each skill from 1 to 5. A 1 is below the bar for this role, a 3 meets it, and a 5 is above it. The examples show what each sounds like. Use 2 and 4 for answers that fall in between.
Visual design
Uses layout, type, color, and spacing to make interfaces clear, attractive, and easy to scan.
Questions
- Tell me about a screen you designed. How did you guide the user's eye?
- Walk me through how you chose the type and colors for a recent project.
- Tell me about a time you changed a visual design after critique. What changed?
1: Below the bar
Describes choices as personal taste. Cannot explain how layout, type, or color helped the user.
3: Meets the bar
Explains main choices like hierarchy and contrast with clear reasons. Accepts feedback but leans on examples or trends.
5: Above the bar
Ties every visual choice to a user goal, explains trade-offs, and shows how critique measurably improved the design.
Design systems
Builds and maintains reusable components so interfaces stay consistent as products and teams grow.
Questions
- Tell me about a component or pattern you built to be reused. Who used it?
- Tell me about a time a design didn't fit the existing system. What did you do?
- How have you kept a shared library up to date as the product changed?
1: Below the bar
Treats each screen on its own. Can't explain why shared components or rules help, or how others use them.
3: Meets the bar
Uses and extends an existing system with care. Explains when to reuse a component and when to propose a change.
5: Above the bar
Builds components others adopt, documents the reasons, and sets up a way to review and update them as needs change.
Attention to detail
Catches small visual and interaction flaws and fixes them before work reaches review or engineers.
Questions
- Tell me about a small flaw you caught late in a design. How did you find it?
- How do you check your own work before sharing it? Walk me through it.
- Tell me about a time a detail slipped through. What did you change afterward?
1: Below the bar
Can't name a flaw they caught. Relies on others to spot errors and describes no checking routine.
3: Meets the bar
Describes a regular self-check for spacing, alignment and text. Admits some slips and fixes them once someone points them out.
5: Above the bar
Describes a repeatable checklist, catches edge cases like long text or error states early, and explains how they stopped repeat slips.
Prototyping
Builds interactive prototypes that test ideas quickly and shows what users or teammates learned from them.
Questions
- Tell me about a prototype you built. What question was it meant to answer?
- Describe a time a prototype changed your design. What did you see?
- How do you decide how realistic a prototype needs to be?
1: Below the bar
Treats prototypes as polished demos. Cannot say what they tested or what changed afterward.
3: Meets the bar
Builds a clickable prototype for a clear purpose. Shares it for feedback and makes some changes from it.
5: Above the bar
Picks the simplest prototype that answers a specific question, tests it with users, and names exactly what changed because of it.
Working with engineers
Partners with engineers to turn designs into working product, resolving constraints and disagreements together.
Questions
- Tell me about a time an engineer said your design was hard to build. What happened?
- Describe how you hand off a design. What do engineers get from you?
- Tell me about a time you and an engineer disagreed. How did it end?
1: Below the bar
Blames engineers when the build differs from the design. Hands off files and waits, with no talk beforehand.
3: Meets the bar
Shares designs with notes and answers questions. Adjusts the design when engineers raise limits, though usually after the problem appears.
5: Above the bar
Involves engineers early, learns their limits, and offers options that keep the design intent. Checks the build with them and agrees on fixes.
Overall recommendation
Decide on your own, before you compare notes with the rest of the panel.