> the honest answer, not the myth

Will Your Resume Pass Ashby?

You applied through a jobs.ashbyhq.com link, got the confirmation email, and then — silence. It's easy to assume a robot read your resume, scored it, and binned it. The truth about Ashby is more specific, and more useful: a parser autofills your application, optional AI labels criteria, and a human clicks reject. This page explains exactly what Ashby does with your resume, sourced from Ashby's own documentation — and our free checker shows how your resume parses, right in your browser. Nothing is uploaded anywhere.

Scan my resume free →

no account · no email · 100% private — runs in your browser

Paste your resume

🔒 100% private: analysis runs entirely in your browser. Your resume is never uploaded to any server.

// what actually happens

What Ashby actually does with your resume

When you upload your resume to an Ashby application form, Ashby extracts the text and tries to autofill fields like name, contact details, and location. Per Ashby's documentation, resumes must be 16MB or smaller to be processed for autofill and full-text search — fine for any normal file, but a red flag for image-heavy scanned PDFs, which can also lack a readable text layer entirely. That extracted text matters later: it's what recruiters keyword-search and what any AI criteria are checked against.

After you submit, your application lands in an Application Review queue. Recruiters and hiring managers open a bulk review screen where they can see your full application, just your form answers, or just your actual resume file — then advance or reject. Rejecting requires selecting a rejection reason, and rejection emails can be scheduled to send later, which is one documented reason a 'no' can arrive weeks after the decision. The core product does not score or rank your resume.

Two optional automations exist, and the distinction matters. Ashby's Auto-Reject feature acts only on application form answers — empty required fields, exact or fuzzy text matches on what you typed — never on resume content. Separately, AI-Assisted Application Review reads your resume against criteria a recruiter writes (e.g. '2+ years B2B SaaS experience') and labels each one 'Meets', 'Does not meet', or 'Undecided', with citations. Ashby's docs are explicit that the reviewer, not the AI, advances or rejects. Whether either feature is switched on varies by employer.

// myth vs reality

What candidates believe — and what's documented

mythAshby's AI scored my resume and auto-rejected me.
realityAshby's AI-Assisted Application Review produces no score and no ranking — it labels recruiter-written criteria 'Meets / Does not meet / Undecided' with cited reasoning, and Ashby's documentation states the reviewer makes the advance/reject decision. A VP of Talent who used it on 1,500 resumes put it plainly in Ashby's own blog: 'No decisions are made for me. No scoring or ranking is involved.'
mythAshby auto-rejects resumes that are missing the right keywords.
realityAshby does have a documented Auto-Reject feature, but it triggers only on application form answers — empty required fields or text matches on what you typed into questions. Ashby's docs are explicit that it does not analyze resume content. If you were knocked out automatically, it was a form answer (location, work authorization, a screening question), not your resume's wording.
mythIf I never heard back, the parser must have garbled my resume.
realityPossible, but usually not the cause. Reviewers in Ashby's bulk review screen see your actual uploaded resume file, not just parsed fields — so a parsing hiccup rarely hides you completely. Silence more often means high volume, a human 'reject' with a delayed rejection email, or a role that stalled. Still worth checking your parse: garbled text does hurt keyword search and AI criteria checks.
mythBeating Ashby means stuffing the page with keywords.
realityRecruiters in Ashby run boolean full-text searches over resume text ('matches', 'contains', 'similar', combined with AND/OR/NOT). Your real skills need to appear in plain text, in the words recruiters actually search — but a human reads the same document seconds later, and obvious stuffing reads as exactly what it is. Write for the search query and the reader at once.

// the real rejection mechanism

How recruiters use Ashby on their side

The real rejection mechanism in Ashby is a person working through the bulk Application Review queue. The interface is built for speed: tabs to flip between your resume and your form answers, keyboard shortcuts, sort by newest or oldest, and a reject action that just requires picking a reason. At startup-scale application volume, that means your resume often gets seconds of human attention on first pass — which is why a skimmable top third matters more than any trick. Research backs up how lossy this stage is: in a 2021 Harvard Business School study, 88% of employers admitted their screening processes vet out qualified candidates.

Beyond the queue, recruiters search. Ashby supports full-text boolean search across resume text — 'matches', 'contains', and 'similar' operators combined with AND, OR, and NOT (e.g. python & react & nodejs) — plus filters on location, stage, tags, and application answers. Where AI-Assisted Review is enabled, they can also filter the pipeline to candidates who meet specific criteria. If a skill exists in your head but not as searchable text on the page, you don't surface in any of it.

// before you apply

Resume tips specific to Ashby

Check the autofilled fields before you hit submit
Ashby parses your resume to autofill application fields like name, contact info, and location. Autofill errors become your application of record, so verify every prefilled field — especially location, which can also set your timezone and feed location-based screening.
Treat the application questions as the real knockout layer
Ashby's documented Auto-Reject works on form answers, not your resume: empty required fields and exact or fuzzy text matches can trigger automatic rejection with an archived reason. Never leave a required question blank, and answer location and work-authorization questions in plain, direct terms.
Submit a text-based file, not a scanned image
Ashby's parsing, full-text recruiter search, and AI criteria checks all run on extracted text, and files over 16MB aren't processed for autofill or search at all. A standard text-based PDF exported from your editor is safe; a scanned or screenshot PDF can be invisible to search even though a human can still open it.
Write skills the way recruiters type search queries
Ashby's boolean resume search matches words and phrases literally. Include both the acronym and the spelled-out form of key skills — 'AWS (Amazon Web Services)', 'CI/CD (continuous integration)' — so you match either query, and keep skill names in real text rather than inside graphics or icons.
Keep formatting simple, but don't panic about it
Clean single-column layouts with standard headings (Experience, Education, Skills) parse most reliably. But remember Ashby shows reviewers your actual uploaded file in bulk review — so a slightly imperfect parse won't erase you; it mainly weakens autofill and keyword search.

Check your resume before you submit →

Frequently asked questions

Does Ashby automatically reject resumes?

Not based on your resume. Ashby has a documented Auto-Reject feature, but its docs state it acts on application form answers only — empty required fields or text matches on your typed responses — and does not analyze resume content. Its AI review tool labels criteria but doesn't reject; per Ashby's documentation, a human reviewer makes the advance/reject decision.

Does Ashby score or rank my resume?

No documented score or rank exists in Ashby. The optional AI-Assisted Application Review outputs 'Meets / Does not meet / Undecided' per recruiter-defined criterion with cited reasoning — Ashby's own blog quotes a talent leader using it: 'No scoring or ranking is involved.' Recruiters can filter by those labels, but disposition is manual.

Why has my Ashby application gone silent for weeks?

Usually humans, not software. Applications sit in a review queue until someone works through it, and Ashby lets employers schedule rejection emails to send well after the actual decision. Silence typically means high volume, a delayed rejection notice, or a paused role — not a parser failure, since reviewers can see your actual resume file.

Should I use a PDF or Word document for Ashby applications?

Ashby's docs don't restrict file types, so both work. What matters is that the file contains real extractable text (not a scanned image) and stays under 16MB, the documented ceiling for autofill and full-text search processing. A standard text-based PDF preserves your layout and parses reliably — then double-check what Ashby autofilled.

// sources

Our scoring is rule-based and documented — see how ATSGrader scores resumes. We are not affiliated with Ashby; employer configurations vary.