Application ReviewY Backed by Y Combinator

A person is morethan a PDF.

Portfolio, demos, papers, video and references, read together against your bar.

PORTFOLIO
DEMOS
PAPERS
CODE
VIDEO
REFERENCES
READ AS A WHOLE
EVERY OTHER PDF

Portfolio · Demos · Papers · Code · Video · References
Read together. One person, beyond the PDF.

[THE RESUME PROBLEM]

Both sides automated the resume.

Applicants write it with AI. Screeners reject it with AI. A keyword score says how many words matched, and nothing about what the person can do.

01 / WRITTEN BY AI

The applicant writes the CV with a chatbot.

02 / SCORED BY KEYWORDS

The screener counts matches. The line stays flat.

03 / COMPRESSED TO A PAGE

Whatever did not fit the page is what they get rejected for.

[APPLICANT INTELLIGENCE]

Connect the proof across their work.

Everything an applicant shares is read together against the bar. What they did lands on a criterion. What is missing becomes a question.

WHAT THEY SHARED
PORTFOLIO
CODE
DEMOS
PAPERS
VIDEO
REFERENCES
ONE APPLICANT
THE BAR
BUILT IT THEMSELVES
PROOF · DEMO
SHIPPED TO PRODUCTION
PROOF · CODE
LED A LAUNCH
NO PROOF · ASK NEXT
STILL HANDS-ON
PROOF · REFERENCE

Built it themselves

PROOF · DEMO

Shipped to production

PROOF · CODE

Led a launch

NO PROOF · ASK NEXT

Still hands-on

PROOF · REFERENCE

Everything they shared, linked to one person.

Portfolio, code, demos, papers, video and references, read as one body of work.

Each criterion gets its proof, with the source.

The bar you agreed at kickoff is the bar every applicant is read against.

A gap is a question, not a rejection.

What the application could not show becomes the first thing the screen asks.

[DOWNSTREAM]

The gap becomes the first question.

Review hands its findings to the next agents. Nobody re-reads the application.

APPLICATION REVIEW
AI INTERVIEWS
Opens with the missing proof.
MEETING INTELLIGENCE
Carries the proof into the debrief.
ANALYTICS
Shows which criterion is hardest to meet.

Your next great hire may write a bad resume. They still get seen.

SHORTLIST APPROVED BY A RECRUITER

A WORKED EXAMPLE · ILLUSTRATIVE WORKFLOW

Read the evidence beyond the CV

An applicant submits a CV, a project portfolio and a recorded demo for a product engineering role.

  1. Bring the materials together against the agreed hiring criteria.
  2. Look for what the applicant personally contributed and the evidence supporting it.
  3. Carry unresolved questions into the interview instead of treating missing information as proof.

The team reviews the evidence and decides what to investigate next.

This example explains the workflow; it is not a customer result or a live product output.

COMMON QUESTIONS

Questions about application review

What does Application Review consider?

The page brings together applications, portfolios, demos, papers, video and references against your team’s hiring bar. The aim is to understand the evidence across the applicant’s work.

Is a CV enough to assess an applicant?

A CV is one source. Work samples and supporting materials can provide context that a short document leaves out.

What happens when evidence is missing?

Keep the gap visible as an open question for the next stage. Missing evidence should be investigated rather than presented as something the applicant has proven.

Can our criteria change?

Your team owns the bar. Approved changes become shared hiring context so review and the downstream stages use the same standard.

Your next great hiremay be bad at resumes.

Book a demo