Sample Report
This is an anonymized real interview analysis
Senior UX Designer
Shows solid design fundamentals and genuine user empathy, but struggles to connect design work to business outcomes. Portfolio presentation lacked clear structure—jumped between projects without establishing context. When challenged on design decisions, became defensive rather than curious. The whiteboard exercise showed good process but took too long to reach a testable solution. Major gap: can't articulate how designs impacted metrics. This is fixable with focused preparation on storytelling and stakeholder communication.
5.9
Communication
6.4
Relevance
5.7
Confidence
6.2
Preparation
Strengths
- +Genuine empathy for users—consistently centers their needs in discussion
- +Good understanding of accessibility and inclusive design principles
- +Comfortable with ambiguity in early design phases
- +Clean visual design skills evident in portfolio work
Areas for Improvement
- -Cannot articulate business impact or metrics for any portfolio project
- -Became defensive when design decisions were challenged
- -Portfolio presentation lacked structure—context was buried or missing
- -Whiteboard exercise took 25 minutes to reach a testable concept
Pillar Assessment
Communication
Clarity and structure of your responses
Needs Work
Relevance
Answer alignment with questions
Needs Work
Confidence
Tone and assertiveness
Needs Work
Preparation
Knowledge of role and company
Needs Work
🎬Key Moments
“Before I design anything, I want to understand: who is this for, what are they trying to accomplish, and what's getting in their way? The visual design is the last 20% of my job.”
This shows mature design thinking—you understand that design is about solving problems, not making things pretty. This is exactly the mindset senior roles require.
“I made that choice because I'm the designer and that's my expertise.”
This response shut down a legitimate design discussion. The interviewer was testing how you handle pushback—a daily occurrence in design work. Becoming territorial is a red flag for collaboration.
“I think the design was successful. Users seemed to like it and we got positive feedback from stakeholders.”
'Users seemed to like it' isn't evidence. How did you measure success? What metrics changed? Without data, you can't claim impact—and senior designers are expected to measure their work.
🚀Action Plan
- 1Add one metric to each portfolio project—even estimates help establish credibility.
- 2Script your portfolio presentation: 3 projects, structured as problem → process → solution → impact.
- 3Prepare a response template for design challenges: 'Here's my reasoning. Tell me more about your concern.'
- 4Research the target company's product and identify 2-3 design opportunities.
đź“ŠStatistics
64%
Speaking time
4521
Your words
188
Words/answer (avg)
2
Questions asked
Filler words detected
Hedging phrases detected
Detailed Feedback
Your design fundamentals are solid, and you clearly care about users—that empathy came through in how you discussed their needs. The philosophy you expressed ('design is problem-solving, not decoration') is exactly right and differentiates you from less mature designers. However, there are significant gaps that would prevent a hire at the senior level: 1. **Business impact**: You couldn't articulate metrics for any project. 'Users liked it' isn't evidence of success. Senior designers are expected to measure their work and connect it to business outcomes. Even rough estimates are better than nothing. 2. **Defensiveness**: When your design choices were challenged, you became territorial. 'I'm the designer' is not a defense. Senior designers collaborate constantly and should welcome pushback as an opportunity to either strengthen their reasoning or learn something new. 3. **Portfolio structure**: Your presentation lacked a clear narrative. You jumped between projects without establishing context, and it was hard to understand the impact of your work. Interviewers are busy—make your value obvious. 4. **Relevance**: Several answers drifted from the question asked. When asked about engineering collaboration, you talked about tools instead of relationships. Listen carefully and answer directly. The good news: these gaps are entirely fixable with focused preparation. Spend a week restructuring your portfolio stories with metrics, practicing how to receive challenges gracefully, and researching target companies. Your design instincts are sound—it's the communication that needs work.
Common Questions
What metrics should designers track?
Depends on your work. For product design: task completion rates, time-on-task, error rates, conversion rates, NPS changes. For UX research: hypothesis validation rates, research-to-implementation ratio. You don't need to track everything—pick 1-2 meaningful metrics per project and know them cold.
How do I handle challenges to my design decisions?
With curiosity, not defensiveness. Template: 'Here's my reasoning based on [user research/data/principles]. That said, I hear your concern about X. Can you tell me more?' This shows you can defend with evidence while remaining open to new information. Senior designers welcome pushback.
How should I structure my portfolio presentation?
For each project: problem (with metric or context), your specific role, key insight that drove the solution, the solution itself (briefly), and measurable impact. Total time: 3-4 minutes per project. Lead with why this project is relevant to the interviewer. Make impact obvious, don't bury it.
đź“‚Explore More Sample Reports
Get Your Own Analysis
Upload your interview recording and get the same detailed feedback tailored to your performance.