Hire software engineers without reading two hundred résumés

Everyone's CV lists the same eight technologies. Career1 asks each applicant what they actually built with them, follows up where the answer is thin, and scores what's left.

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 software engineers hard to screen

The stack list tells you nothing

React, Node, Docker, AWS, on almost every CV in the pile, at wildly different depths, described identically.

Take-home tests lose the good ones

A strong engineer with a job and a family will decline a four-hour unpaid exercise, and you never learn they applied.

Live coding tests nerves as much as skill

It measures performance under observation, which is not how anyone on your team writes code on a Tuesday.

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 software engineers

What they personally built
Not what the team shipped, but which part they wrote, and what they decided along the way.
Debugging instinct
How they found the cause of the worst bug they can remember, which separates people who read stack traces from people who restart the server.
Trade-offs they've regretted
Engineers who have owned a system in production talk about trade-offs. Engineers who have only built features talk about features.
Explaining to a non-engineer
Whether they can describe their architecture to someone who doesn't know the codebase.

Questions people ask

How do you screen software engineers without a coding test?

By asking them to explain work they've actually done in enough detail that it can't be faked: what they built, what broke, what they'd do differently. Career1's interviewer follows up on each answer, so borrowed experience runs out quickly. Use it as the first round, then spend your engineers' time on the shortlist.

Can it screen for a specific stack?

Yes. The interview is grounded in your job description, so a role asking for Go and Kubernetes produces questions about Go and Kubernetes, and the report scores against what you asked for.

What do I get back for each engineer?

A match score, the strengths the interview verified, the risks, a hire recommendation, and the full video and transcript so your team can check any of it.

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 software engineers 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 .