The answer behind the score
“I asked what decision the page needed to support. Once we agreed it was plan comparison, the layout became simpler.”
For your next interview
How did you test whether the new layout helped?
round1 · Candidate reports
A score. And the story behind it.
See how each answer matches your criteria. Read the supporting quotes and bring better questions to your next interview.
Sign up freeSample scorecard
Senior Product Designer
The answer behind the score
“I brought engineering into the first sketch review so we could agree on the trade-offs before building.”
For your next interview
Tell me about a trade-off the team disagreed on.
The answer behind the score
“Testing showed people missed the main action. We changed the flow instead of keeping my preferred design.”
For your next interview
What changed after you shipped the revised flow?
Evidence, not guesswork
Know what to
follow up on.
A score is a starting point. The answer behind it helps you make the decision.
- 01 · The criterion
What you’re looking for.
Every evaluation starts with the criteria you reviewed for the role.
- 02 · The quote
What they actually said.
Read the interview evidence alongside each score.
- 03 · The next question
What’s worth exploring.
See follow-up questions and anything the interview didn’t cover.
Keep your hiring system
The report goes
where you work.
Export to Greenhouse or Lever. No copying notes between tools.
01 · round1
Your report
Scores and supporting quotes.
02 · Export →
One handover
An evaluation note and shareable report link.
03 · Your hiring system
Greenhouse / Lever
Ready for your team to review.
The hiring decision stays with your team. round1 prepares the evidence.
More to explore