For founders and CTOs hiring engineers

Know who actually wrote the code before the offer goes out.

Send your candidate one link. They talk for 20 minutes about a project they built. You get a one-page report the same day: what they could explain, where they needed help, and what to ask in your final round.

  • First check free
  • Pay only after you see the reports
  • Too little code to judge? No charge

0unveiled · Candidate report

Aarav K.

Backend Engineer · 2 repos · 21-min interview

Interview

Two-minute read

Hire signal: Yes

Built and can defend a payments ledger; one gap on money rounding.

Strength Explained webhook idempotency without a hint

Concern Needed a hint on the rounding rule

7/8

explained live

Clean

integrity

0

critical issues

Ask them in the final round

“Two refunds for the same charge land at once. What would you change so the balance can’t go negative?”

21:04
PDF

Example report, fictional data

The problem

Resumes got better. Knowing who can build didn’t.

Hiring on polished resumes and puzzle rounds shows you how someone performs in an interview, not what they have actually built.

Every resume reads the same

AI writes polished bullet points in a minute. They tell you what someone claims, not what they built.

Your best engineer is interviewing

Each technical round takes an hour of the person your team can least spare, often to learn very little.

Some can’t explain “their” project

You find out in the final round, or a month after they join. In a 20-person team, a wrong hire costs months.

Someone’s own code should speak louder than their CV.

How it works

One link. Twenty minutes. One page.

  1. 01

    Send one link

    Add a candidate, or paste a shortlist. Each gets their own link by email, and a reminder if they haven’t started after two days. They sign in with GitHub and pick one or two public repositories they built.

  2. 02

    They talk about their own code

    A 20-minute voice interview on the projects they chose, from a laptop. No camera, no puzzles, no take-home.

  3. 03

    You get one page

    Usually within the hour: a two-minute read, what they explained, what they couldn’t, and three questions for your final round. Listen to the audio or download the PDF.

The interview

Questions only the person who built it can answer.

Paste a code snippet into a chatbot and you get a fair answer about the code. It can’t tell you why they built it that way. So the interviewer asks about the decisions behind it.

  • The project

    What made you build a job agent that refuses to invent facts, instead of a faster auto-filler?

  • Their decision

    You keep facts in a YAML ledger rather than a normal resume. What did that cost your users?

  • Their commit

    Your commit on 12 Oct rewrote how headlines are matched. What broke that made you change it?

  • Their code

    Two refunds for the same charge land at once. What would you change so the balance can’t go negative?

  • Examples. Every question is written from the candidate’s own README, commits and code.

Helps them recall, then digs in

A nervous candidate gets a hint before the interviewer moves on, and the report notes which answers needed one. A polished answer gets a follow-up only the author could answer.

Notices what a video call misses

Answer timing, tab switches and typing sounds are measured and reported as signals for you to probe, never as verdicts.

AI use is fine. Unexplained code is not.

Candidates declare the AI tools they used and are never marked down for them, only for code they can’t explain.

The report

The page your final round starts from.

It arrives by email when the interview ends, and the link stays live for your team.

A two-minute read

A one-line verdict and a hire signal (Strong yes, Yes, Mixed or Not yet), with strengths and concerns.

What they explained, and what they couldn’t

Each with the file it came from, so you can check it yourself.

Three questions for your final round

Written from their answers and their gaps, so your panel starts where the interview stopped.

Signals and flags

Integrity signals from the interview, AI use, and issues found in their repositories, including critical security ones.

Audio and a PDF

Jump to any answer in their own words, and forward the PDF to your co-founder or panel.

Reviewed by a founder

Ayush or Shiven reads every report and adds what to trust and what to probe.

For your candidates

A screen your candidates won’t resent.

Good engineers like talking about what they built. Twenty minutes on their own project respects their time, and it shows.

20 minutes, not a weekend

Less work than a take-home, so strong candidates finish it.

Their project, their choice

They pick the repositories and declare the tools they used.

No camera

Audio only. It is deleted automatically after 180 days.

Something to keep

They get a Proof Card of the interview to share, if they want to.

Who runs it

We’re engineers. We’ve sat through technical rounds that told nobody anything.

0unveiled is built by Ayush and Shiven. We read every report before it goes out, so we’re taking 10 pilot companies this month. You talk to a founder, not a sales team.

Pricing

Pay after you’ve seen it work.

First check

Free

one candidate

Try it on someone you’re about to make an offer to.

  • The full report, audio and PDF
  • Reviewed by a founder
  • Set up with a founder

The Shortlist Sprint

₹5,000

3 engineers checked before you make the offer

Paid after you see the reports.

  • 3 interviews, compared side by side
  • Every report reviewed by a founder
  • A 30-minute review call
  • Invoice after delivery, UPI or bank transfer

After the pilot

₹2,500

per candidate

No subscription, no seats.

  • Invite one candidate or a shortlist
  • Same report, same day

If a candidate’s public code is too thin to judge, the report says so and that check is free. Candidates never pay.

Questions

Straight answers.

They open the link, sign in with GitHub, pick one or two public repositories they built, and say which AI tools they used. Then they take a 20-minute voice interview from a laptop about those projects: why they built them, the decisions they made, what breaks, and how they would change the code.

Get your first check free

Pick a candidate you’re about to make an offer to. A founder will set it up with you within one working day.

Work email, please. Prefer to talk first? ayush@0unveiled.com