Hire product designers without reading two hundred résumés

A portfolio shows the final screens. It doesn't show which constraint forced them. Career1 asks designers to walk through the decisions, and scores the reasoning.

No card required · Candidates never pay

Ended Senior Backend Engineer · Jordan C. 05:10
Scorecard 3 of 3 signals
  • System design 86
  • Depth under follow-up 92
  • Ownership 84
Overall
87
Scoring as it listens
Hire recommended

For your interview: ask how they handled replica lag for reads straight after writes.

Example Career1 interview with a fictional candidate for a Senior Backend Engineer role. Career1 at 02:06: Your resume says you scaled the order service at Brightcart. What broke first when traffic doubled? Jordan at 02:30: The Postgres connection pool. Every request opened its own connection, so at peak we hit the limit and requests queued. We put PgBouncer in front and moved reads to a replica. Career1 at 03:09: Why PgBouncer, rather than just raising max_connections? Jordan at 03:27: Each Postgres connection is a separate process with its own memory. Raising the limit would have swapped queueing for memory pressure on the primary. Pooling kept it to about forty real connections. Career1 at 04:10: Who owned the incident when the pool saturated? Jordan at 04:25: I did. I was on call, I wrote the postmortem, and I added the pool-saturation alert the team still uses. Scorecard: System design 86, Named the bottleneck and two fixes, in order. Depth under follow-up 92, Defended the choice with the actual trade-off. Ownership 84, On call, wrote the postmortem, shipped the alert. Overall 87, hire recommended.

An example interview with a fictional candidate. Each score links to the answer it came from.

Want the full version? See a sample report with every section, the scores and the whole transcript, for a fictional applicant.

What makes product designers hard to screen

Portfolios are edited

You see the version that worked, presented after the fact. The three that failed and taught them something are not in the PDF.

Team credit is invisible

Beautiful case studies routinely come from teams of six. Nothing in the artefact says who decided what.

Craft and judgement look identical on a slide

Someone who executes a given direction perfectly and someone who chose the direction produce the same-looking page.

How Career1 does it

  1. 01

    Post the role

    Type a job title and Career1 drafts the description, or dictate it, or upload the JD you already have. You choose what the application form asks for: phone, city, and any screening questions of your own.

  2. 02

    Everyone gets interviewed

    Every applicant, not a filtered subset, gets a link to a spoken interview they can take at 2am on a phone. It asks about their actual experience, follows up when an answer is thin, and runs about eight minutes.

  3. 03

    Read a ranked shortlist

    You get a match score, the verified strengths, the risks, a hire recommendation, and the full transcript and video behind every claim. The evidence ships with the score, so you can check the reasoning instead of trusting it.

What the interview probes for in product designers

The constraint behind the decision
Why this layout and not the obvious one, and what they gave up.
Their own contribution
What they personally decided versus what the team handed them.
Evidence they used
Whether the design changed because of something they learned from users, or because of taste.
Handling disagreement
How they describe a time engineering or a stakeholder pushed back, and what happened to the design.

Questions people ask

How do you screen designers beyond the portfolio?

By asking them to talk through the decisions in their own work, the constraint, the alternatives, what they'd change. Career1 runs that conversation with every applicant and attaches the video, so your design lead reviews reasoning rather than thumbnails.

Can candidates submit a portfolio link?

Yes. Add a required link question to the job's application form and it's captured alongside the résumé and the interview report.

Is this suitable for senior design roles?

It's a first round. For staff and principal roles it's most useful for deciding who your team spends an hour with: the depth of the decision-making comes through quickly.

Also hiring for

Start with two candidates, free

Post a role, send the link, and read the first scored report tonight. No card, and nothing for your candidates to pay or install.

Vet your first product designers free

Career1 help

Answers in seconds, any time

Ask anything about Career1. Leave your email so we can reply if the answer needs a person.

Thinking…

Passed to a person. We will reply to .