For hiring teams
Interview software engineering candidates with one link
Create an interview link for a software engineering role and send it to your candidates. They talk with an AI interviewer about their real work, on their own time. You read the transcript and scores that quote their own words, and your team makes the decision.
Free to start while Aethel is in early access. No card needed.
How it works
How to interview software engineering candidates with a link
- Step 1
Create a link for the role
Add the role title, choose Software engineering as the field, and set the level. If you want, add a specialty, focus areas, and up to three questions the interviewer must ask word for word.
- Step 2
Send it to your candidates
Share the link however you already reach candidates. Aethel does not message them for you.
- Step 3
Candidates interview on their own time
The interview takes about 15 minutes. Candidates are told up front that the interviewer is an AI, and they agree to share the result with your company before they start.
- Step 4
Review and decide
Read each transcript and the scores, with the quotes behind them. Mark each candidate Advance, Not a fit, or Undecided, and keep private notes.
The interview
What the interviewer covers
It asks about real software engineering work and follows up on each candidate's answers. It draws on these topics and picks what fits the role.
- A production system they owned and what made it hard
- Debugging a failure or outage from first alert to fix
- A design tradeoff 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
Focus areas on your link steer it further, for example toward a tool, a regulation or a type of client.
Your questions
Sample must-ask questions
Each link can carry up to three must-ask questions. The interviewer asks each one as written. Here are examples for this field.
- Tell me about the last production incident you were part of. What did you check first, and what changed afterwards?
- Describe a technical decision you pushed back on. What was the tradeoff, and how was it settled?
- How do you decide what to test when the deadline is tight?
Results
What you see for each candidate
A result you can check for yourself. Every score points to what the candidate actually said.
The full transcript
Every question and every answer, in order.
“Not enough evidence” instead of a guess
If the interview did not cover an area, the result says so. It is never shown as a low score. The overall score uses only the areas with evidence.
Your decision and private notes
Track where each candidate stands. Candidates never see your notes.
Four scored areas for software engineering
Each is scored from 1 to 100, with the exact quotes behind it.
- Problem Solving
- Counts as evidence when the candidate describes a specific problem, its cause, a fix, a trade-off, or a measured result.
- Architecture
- Counts as evidence when the candidate describes how a system is built: components, data flow, storage, queues, APIs, scaling or consistency choices.
- Communication
- 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). Answering clearly is not, by itself, communication evidence.
- Collaboration
- 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.
What Aethel does not do
- Recommend who to hire or guess at seniority.
- Score faces, voices, accents, backgrounds or video.
- Screen anyone out. Everyone who finishes your interview appears in your list.
- Verify degrees, licenses or work history.
Details are on how Aethel uses AI.
FAQ
Questions about interviewing for software engineering
Can we interview for a specific role in this field?
Yes. Choose Software engineering as the field for the link and add the specialty, such as Full-Stack AI Engineer or ML Platform Engineer. Focus areas and must-ask questions steer the interview further.
Can the interviewer ask our own questions?
Yes. You can add up to three must-ask questions to each link, and the interviewer asks each one as written. It picks the other questions from the role, the field and the candidate's answers.
How are candidates in this field scored?
An AI review reads the transcript and scores four areas for this field: Problem Solving, Architecture, Communication, and Collaboration. Each area gets a score from 1 to 100 only when the review can quote the candidate's own words, and every quote is checked against the transcript. Otherwise the area shows "Not enough evidence". The overall score is the average of the areas that have evidence.
Does Aethel check licenses, degrees or work history?
No. Aethel does not verify degrees, licenses, certifications or employment history. Check those the way you do today.
Does Aethel decide who to hire?
No. Aethel does not recommend who to hire, guess at seniority, or screen anyone out. Every candidate who completes your interview appears in your list, and your team makes every decision.
Will Aethel contact our candidates?
No. You send the link and follow up with candidates yourself. Aethel does not message candidates on your behalf.
What do candidates need?
Your link, a free Aethel account, and about 15 minutes. They can type or speak their answers. A camera is not required.
What does it cost?
While Aethel is in early access, you can create an employer account and keep one interview link open at a time for free. Monthly plans are listed on the pricing page. Experts never pay.
Plans are on the pricing page.
Send your first software engineering interview link
Create an employer account, describe the role, and copy your link. It takes a few minutes.
Want to show candidates what to expect? What the interview covers for software engineers