Find the strong engineers in a pile of polished résumés.

Vesna turns the job into must-haves, checks every applicant against them and asks candidates about missing technical details, so your engineers interview people who have shown the work.

One applicant, five must-haves. Select a must-have to see what it rests on.

Chrystian SchutzSenior software engineer Experience Built the invoice-sync service in Node.js; in production14 months, about 40k writes a day. Full-stack feature work across React and Node. Ran a multi-agent C#-to-Java migration pipeline. SkillsTypeScript, Node.js, React, PostgreSQL, AWS Shown Owned a TypeScript service in productionShown on the résumé Claimed Shipped features across a React front end and its backendClaimed, no feature named. Asked next. For the interview Kept writes correct in systems they did not controlFor the interview. Questions prepared. For the interview Found the cause of a hard production failureFor the interview. Questions prepared. Claimed, question sent Changed how they work with coding agentsClaimed. Question sent.
What counts as shown

Names real engineering work they handed to a coding agent and something they changed when the agent got stuck or got it wrong. Saying they use AI tools does not show this.

Built for engineering rolesEach must-have is written the way an engineer would judge it.
Evidence, not a scoreEvery reading points at the résumé line or answer behind it.
Polish isn’t punishedAI-written résumés are fine. Filler is set aside and substance is read.

The problem

Inbound is a pile nobody can read.

A role gets 500 polished résumés. A team reads the first 150 and stops. The strong people further down are never opened.

150of 500 opened
2of 5 strong candidates found
OpenedNever openedStrong, foundStrong, missedIllustrative numbers. Drag to change how many get opened.
Résumés look alikeAI polish makes weak and strong applicants read the same.
Skills are claimed, not shownA keyword says nothing about who did the work.
Good people are missedNobody reaches the bottom of the pile.

The process

How Vesna fits your hiring process.

Vesna checks each résumé against the must-haves your team agreed, and emails the candidate when the résumé doesn’t cover one. Only a person rejects.

Step 1

Agree on what counts.

Vesna turns your job description into must-haves and says how each one gets checked. Your team edits them before any applicant is read.

RequirementOwned a TypeScript service in production
What counts as shown

Names a backend service or feature they built in TypeScript or Node.js and ran in production for real users or other systems. Listing TypeScript or Node.js as a skill does not show this.

Kind
How Vesna checks it

Vesna asks the candidate. A résumé line can claim it; only the candidate can ground it.

Step 2

Connect your applicant flow.

Applicants come in from Greenhouse, Ashby, Lever or Workable, by email, through the API or as an upload.

Greenhouse Ashby Lever Workable Email API Upload Senior Software Engineer Open, 500 applicants

Step 3

Read every applicant against the role.

One reading per must-have, with the résumé lines it rests on. No overall score.

Applicant
TypeScript in production
React and its backend
Writes in others’ systems
Production failure
Coding agents
Status
Chrystian Schutz
Asking
Emily Presser
Asking
Behbod Karimi
Advanced
Mei Lin Tan
Asking
Arjun Mehta
Asking
Sara Kowalczyk
Asking
Nouri Nouri
Asking

Shown: the résumé or an answer proves it. Claimed: the résumé says it, without detail. No evidence yet: Vesna asks the candidate.

Step 4

Ask before you rule anyone out.

When a résumé doesn’t mention a must-have, Vesna emails the candidate one question about it and tells you whether the answer meets it.

Chrystian Schutz

Ran a multi-agent C#-to-Java migration pipeline.

Claimed. It doesn’t say what he changed when it went wrong.

Hooli via Vesna

Hooli has one quick question about your application

“When the generator silently improved legacy logic instead of replicating it: what exactly did you change, and how did you know that change was the fix?”

Answer the question

It takes a couple of minutes. This is not a test.

vesnaOpen until 17 November

What exactly did you change to fix that

I split the pipeline so a second agent only compares the Java output with the C# build.
I don’t remember thisTalk it throughNot answer this one

Thank you for this thoughtful question. As a results-driven engineer I always strive to uphold the highest standards. I split the pipeline so a second agent only compares the Java output with the C# build. This reflects my deep commitment to robust engineering. Mismatched totals went from 31 modules to none on the next run.

What he changedHow he knew it worked
Shown. Advanced to the shortlist.

It asks only when the answer can move the candidate.

Five must-haves, ranked by how far an emailed answer could move him. Bar lengths are illustrative.

Ranked 1 of 5

Changed how they work with coding agents

Vesna asks this first

His résumé names a real pipeline and how it failed, so a precise question is possible. A clear answer settles this must-have.

Strong answer: shownWeak answer: stays on hold

“When the generator silently improved legacy logic instead of replicating it: what exactly did you change, and how did you know that change was the fix?”

Typed or spokenSenior people answer a short question. They close a video bot.
A way out, alwaysCandidates can ask to talk it through, or decline.
Open about the AIThe email tells the candidate an AI tool wrote the question, and that it isn’t a test.

Step 5

Hand over the shortlist.

The hiring manager gets each shortlisted person with why they advanced and what to ask, and replies on the same page.

Mei Lin Tan

Senior Backend Engineer, Node.js and TypeScript

Evidence to build onCode review that changed a colleague’s practice.

“I did not review it until it was finished, and the Kafka consumer already wrote each batch to Postgres in a single transaction…”

Where to spend interview timeSelf-initiated technical-debt work.

What risk did she identify? What did she change? What improved?

Your assistant + Vesna

“Prepare my interview with Mei. Skip what we already know; give me the gaps and the evidence.”

At the scale of a real pool

Everyone is read. Some are asked. No one is rejected by a machine.

Open a role to inbound without dreading the pile. Vesna advances the people who show the work and leaves everyone else on hold for a person.

500inbound résumés
12already show the work
380get one question, up to three each
108nothing a question could change
58advanced
442on hold for a person
0 rejected by VesnaIt advances or holds. Only a person rejects.
Recruiters stay in chargeVesna sends the questions and reminders. Your recruiters set the must-haves, review everyone on hold and own the relationship.
Example poolThe counts here are illustrative, not measured.

The evidence trail

Every step is on the record.

What Vesna read, what it concluded and when. You can always answer “why?”, to a hiring manager or to a candidate.

VesnaCandidateSystem
What went in

His answer and the “what counts as shown” text

What came out

Shown: names what he changed and how he checked it

Who

Vesna

Stored with input and outputEach AI step keeps what went in and what came out.
Nothing edited afterwardsEntries are read-only once written.
Yours to exportOnly your organisation can see the record.

What you get back

Give engineering a shortlist with the groundwork done.

Your engineers see what each candidate has shown before the interview, so the interview goes on what is still unknown.

How much of the pile nobody reads

Your numbers. It assumes your team reads in the order applications arrive, so strong people are spread through the pile.

500
150
How rare a strong applicant is
350applications never opened
about 4strong applicants among them
OpenedNever openedStrong, openedStrong, never opened

With VesnaEvery applicant is read against the must-haves, the 500th as closely as the first.

Fewer engineering hours in interviews

One engineer’s week of first interviews. Illustrative.

Today9 hours, 5 ending on a basic
With Vesna4 hours, each on what is still unknown
InterviewEnded on something the résumé couldn’t showInterview with a briefHour back

No second shortlist

From open role to first interviews. Illustrative lengths.

Today
Screen résumésShortlistHiring manager: “not it”Screen againSecond shortlistInterviews
With Vesna
Read and askShortlist, with evidenceInterviewsTime you keep

Compare

What happens when the résumé isn’t enough?

How Vesna and other screening tools handle a résumé that doesn’t answer a must-have.

WorkflowWorkable AgentVesna
When the résumé is vagueAsks for missing details and updates evaluations from the repliesAsks about one requirement, in that requirement’s terms: “Describe one comment you left that you later saw reflected in how that engineer wrote code on their own.” Then shows you whether the answer meets the must-have your team agreed.
How a candidate is judgedCriteria-based evaluation with reasoning and a normalized scoreNo overall score. One reading per must-have, with the résumé line or answer it rests on.
Prepare the next stepConfigurable pipeline actionsFor each candidate: what is shown for each must-have, and what to ask in the engineering interview.
Keep your workflowInside WorkableAlongside your existing ATS

From Workable’s product documentation. Reviewed 25 October 2026.

Questions a hiring team asks first.

Does Vesna reject anyone on its own?

No. Vesna advances candidates or leaves them on hold. Only a person rejects.

What does the candidate see?

An email with one plain question and a page to answer it, typed or dictated.

Do you reject résumés written with AI?

No. A polished résumé still needs detail behind its claims, and a sparse one gets a question instead of a rejection.

Who can see our applicants’ data?

Only your organisation: each company’s data is kept apart in the database. Résumés are read through Anthropic’s commercial API. How Vesna protects hiring data

What is recorded?

Every action and every AI call is logged with who, when and the evidence, and can’t be edited. You can export it.

Which ATS do you work with?

Greenhouse, Ashby, Lever and Workable. Email, API and upload work too.

How long does setup take?

About a day. You send a job link, edit the must-haves Vesna proposes, and it starts reading applicants.

Try Vesna on one of your open roles.

Send a public job link. Within one working day you get the proposed must-haves and the questions Vesna would ask.

See Vesna on your role

Send a public job link. Within one working day you get the proposed must-haves and the questions Vesna would ask.

We’ll use these details to review your role and reply. Form submissions are retained for 90 days. Privacy

You’ll hear back from Valerii, who builds Vesna.