Skip to content

For hiring teams

Interview software engineering candidates with one link

Send a software engineering candidate one link. An AI interviewer asks about their real work, and you decide from the quoted scores.

Free while Aethel is in early access: one interview link, up to 25 interviews a month, about 3 of them with a video interviewer, the rest by voice. No card needed.

Hiring for software engineering

What makes this hard to screen

A resume lists languages and frameworks, but it cannot show how someone thinks when production breaks at 2 a.m. Take-home tasks eat a weekend and reward whoever has the most free time. What you want to know is how they reason about trade-offs on systems they actually owned.

Roles this field covers: backend engineer, frontend engineer, mobile engineer, site reliability engineer, security engineer, full-stack AI engineer, ML platform engineer, AI product engineer, data / infra engineer.

Listen for these in a transcript

  • Walks through a real outage step by step: the first alert, what they ruled out, the fix, and what they changed so it would not recur.
  • Names the trade-off behind a design choice, such as latency against cost, and says what they would revisit now.
  • Explains a technical risk in words a product manager could repeat back.

Warning signs

  • Lists tools and buzzwords but never describes a system they were responsible for.
  • Says "we" for every decision and cannot say which part was theirs.
  • Treats tests and code review as something that slows the team down.

How it works

How to interview with a link

  1. Step 1: Create a link for the role

    Choose the field "Software engineering", the level, and a specialty such as backend engineer or frontend engineer.

  2. Step 2: Send it to your candidates

    Share it wherever you already find software engineering candidates.

  3. Step 3: Candidates interview on their own time

    It takes about 15 minutes, and they know the interviewer is an AI.

  4. Step 4: Review and decide

    Mark each one Advance, Not a fit, or Undecided.

The interview

What the interviewer covers

It follows up on each answer and picks the software engineering topics that fit the role.

  • A production system they owned and what made it hard
  • Debugging a failure or outage from first alert to fix
  • A design trade-off between speed, reliability, cost and maintainability
  • Scaling a system or codebase as usage grew
  • Keeping quality high with tests and code review under a deadline
  • Explaining a technical risk to people who are not engineers
  • Working with product and design on what to build
  • A technical decision they would make differently now and what they learned

Your questions

Sample must-ask questions

Up to three per link. The interviewer is told to ask each one as written, and every result shows whether it was asked word for word, asked in other words, or not asked. Examples:

  1. Tell me about the last production incident you were part of. What did you check first, and what changed afterwards?
  2. Describe a technical decision you pushed back on. What was the trade-off, and how was it settled?
  3. How do you decide what to test when the deadline is tight?

Starter templates

Start from a common role

Start a link from one of these and edit anything.

  • Engineering manager

    Focus: Leading and growing an engineering team, planning and delivery, technical decisions, hiring and feedback

  • Frontend engineer

    Focus: Building web interfaces, managing state, page speed, accessibility

  • Mobile engineer

    Focus: Building iOS or Android apps, app performance, offline support, releasing through the app stores

  • QA automation engineer

    Focus: Test strategy, automated tests, fixing flaky tests, release quality, working with developers

  • Security engineer

    Focus: Threat modeling, secure code review, finding and fixing vulnerabilities, cloud and access security, incident response

  • Senior backend engineer

    Focus: API design, databases and data modeling, running services in production, code review

  • Site reliability engineer

    Focus: Running services in production, monitoring and alerting, incident response, infrastructure as code, deploy pipelines

Results

What you see for each candidate

  • The full transcript

    Every answer, in order.

  • “Not enough evidence”

    Shown instead of a guess, never as a low score.

  • Your decision and private notes

    Only your team sees them.

The four scored areas

Each out of 100, with quotes.

Problem solving (approach, debugging, edge cases)
Counts as evidence when the candidate describes a specific problem, its cause, a fix, a trade-off, or a measured result.
Architecture (system design, components, data flow)
Counts as evidence when the candidate describes how a system is built: components, data flow, storage, queues, APIs, scaling or consistency choices.
Communication (clarity, structure, ability to explain)
Counts as evidence when the candidate describes explaining, documenting or presenting work to other people (for example a design doc, a runbook, or walking a team through a change). Answers that respond to the question asked, in a clear order, with a concrete example, also count, but only up to 80 on their own. Grammar, word choice and fluency are never judged.
Collaboration (teams, reviews, feedback)
Counts as evidence when the candidate describes working with other people: teammates, stakeholders, reviews, mentoring, feedback or cross-team work. Saying "we" is not, by itself, collaboration evidence.

See a whole result the way your team would: the sample software and data result, with a made-up candidate.

Aethel never scores faces, voices or accents, and does not verify degrees, licenses or work history. How Aethel uses AI

FAQ

Questions hiring teams ask

Does the interview include a coding test?

No. Nobody writes or runs code. It is a spoken or typed conversation about systems the engineer built, broke and fixed. If you need a coding exercise, run it as a later step in your own process.

Can we point it at our stack, like Kubernetes or React Native?

Yes. Put the stack in the focus areas and it will ask about work with those tools. It hears how they describe that work; it does not test hands-on skill with the tool.

Is this useful for senior and staff engineers?

Set the level on the link to Senior or Staff. The level is part of the interviewer's instructions, which tell it to pitch its questions to that level. The level does not change how long the interview runs or how many follow-up questions it asks, and the score uses the same scale for every level. For those roles you may still want a system design session with your own engineers.

See also the questions companies ask and the pricing page.

Send your first software engineering interview link

Want to show candidates what to expect? What the interview covers for software engineers