> the honest answer, not the myth

Ashby Resume Check: Parsing and Application Guidance

Ashby documents five separate things that touch an application: how your resume file is processed, how recruiters search resume text, rejection rules an employer can attach to the application form, an optional AI-assisted review that checks criteria against a resume, and a separate fraud-signal feature. This page uses Ashby’s public documentation for each one. It is an independent checker, not an integration with Ashby, and it cannot see an employer’s configuration or the reason behind any decision.

Scan my resume free →

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

scan.local — your resume stays in this tab0 bytes uploaded

Paste your resume

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

Don't take our word for it — turn off your wifi and scan again. It still works, because the whole analysis runs on your device.

// what actually happens

What Ashby actually does with your resume

Ashby’s application-form documentation gives two numbers for resumes. The maximum resume upload is 50MB, but a resume must be 16MB or smaller to be processed for full-text search and for auto-filling application fields. A resume question uploads a single file and can appear only once on a form. Other file-upload questions accept PDF, DOC, DOCX, JPG, JPEG, PNG, and common video formats such as MP4 up to 50MB. Executables and certain text formats such as .md are not supported, and Ashby suggests converting those to PDF. Ashby also lists Enhanced Resume Parsing as an opt-in feature that applies only to resumes added after an admin turns it on.

Employers build the form from question types including short answer, multiple choice, checkboxes, Yes/No, number, URL, location, education history, file, and resume. Any of them can be required, and some can be private: candidates answer them, but only organization admins and users with elevated access can read the responses.

Auto-reject rules run once, when the application is submitted, and only on new applications. Conditions on multiple-choice questions can test equals, is empty, or is not empty. Conditions on text questions can test contains, starts with, ends with, or similar to, a fuzzy match that Ashby’s example uses to match “local” against “localization.” Conditions combine with And, Or, and Not, and can be nested. Rules run in the order listed, and once one rejects an application the later ones are skipped. A rejection email can use a template and be delayed by a set number of business days, and recruiters can list auto-rejected candidates with a filter. Applications submitted through an application request link are not checked.

Separately, AI-assisted application review lets recruiters define criteria in job settings. For each criterion the AI looks for evidence in the resume and returns Meets or Does not Meet with a rationale and citations. If it can’t decide, the criterion is marked unknown, and an unreadable resume is marked skipped. Ashby’s page describes no overall score or ranking and says the reviewer, not the AI, advances or rejects. It also says resumes are redacted for personal information before reaching the model, that applicants can be given disclosures and can opt out, and that admins opt in to each AI feature separately.

// myth vs reality

What candidates believe — and what's documented

  • mythEvery Ashby employer uses the same passing score.

    realityAshby’s auto-reject conditions and AI review criteria are written per job. Nothing in the documentation reviewed describes a shared pass mark across employers.

  • mythAshby’s AI scores and ranks my resume.

    realityAshby’s page on assisted review describes a per-criterion answer (Meets, Does not Meet, unknown, or skipped) with citations, and no overall score or ranking.

  • mythA fast rejection means an AI read my resume.

    realityAuto-reject rules documented by Ashby test application answers at submission, and the email can be delayed by business days, so neither a fast nor a slow email identifies a mechanism.

  • mythA resume the AI can’t read gets me rejected.

    realityAshby says an unreadable resume is marked skipped for that criterion, which leaves the decision with the reviewer. Separately, a file over 16MB isn’t processed for full-text search, so recruiters can’t find it by resume keyword even though the file is attached.

// the real rejection mechanism

How recruiters use Ashby on their side

Ashby’s candidate search includes a Full Text Resume Search filter with four match modes. Matches finds resumes that contain all the words in any order and is case-insensitive. Contains finds the exact phrase in order. Equals needs the exact phrase with the same capitalization. Similar finds word variations, so “localization” may also match “localized.” OR, AND, and NOT have symbol forms (| or a comma, & or +, and !), quotation marks keep a multi-word term together, an asterisk matches part of a word, and parentheses group sub-queries.

Practical reading, ours and not an Ashby statement: Contains needs your phrase exactly as typed and in order, while Matches needs only the words. A posting’s term, such as revenue operations, is found by both when written in full. Write the full phrase once, in a sentence that says what you did.

Evidence review · · ATSGrader editorial team

Ashby has several distinct review mechanisms

Ashby documents configurable rejection rules based on application answers and a separate AI-assisted review feature. In assisted review, criteria receive a reasoned assessment for recruiter decisions. An email’s timing does not identify which mechanism an employer used.

  1. Review the vacancy requirements and application answers separately from your resume.
  2. Inspect file extraction before discussing keyword coverage.
  3. Treat an assisted-review explanation and a configured rejection rule as different product features.

A controlled example

Input: A synthetic application has readable resume text but answers No to an employer-defined required condition.

What to check: A local resume score cannot validate that answer or override an employer’s configured question rule.

Limit: This is a conceptual example, not a test of an Ashby tenant.

Inspect the extracted file text, then use the published scoring rules and synthetic benchmark. Run your own local diagnostic →

// before you apply

Resume tips specific to Ashby

  • Keep the resume file under 16MB

    Ashby processes resumes for full-text search and autofill only at 16MB or smaller. A text-based PDF is normally a fraction of that, and embedded photos or graphics are what inflate it. The second half is practical advice.

  • Send a readable file

    Ashby’s assisted review marks an unreadable resume as skipped. Export from your editor rather than scanning, and check that you can select a line of text before you upload.

  • Write multi-word terms in full

    The Contains and Equals search modes need the exact phrase. If the posting says data pipeline, write data pipeline where it is accurate rather than only the pieces. Capitalization matters in Equals mode but not in the other three.

Check your resume before you submit →

Frequently asked questions

Does this tool reproduce Ashby’s scoring?

No. This checker uses ATSGrader’s published rules on text extracted in your browser. Ashby’s documentation describes per-criterion AI analysis and employer-written rejection rules, none of which this tool can see or replicate.

Does Ashby automatically reject applicants?

Ashby documents auto-reject rules that employers write against application answers, run once at submission, and apply only to new applications. Ashby’s page on AI-assisted review says that feature doesn’t reject candidates; the reviewer advances or rejects.

Does Ashby detect fraudulent applicants?

Ashby lists AI fraud signal summaries, under Candidate Fraud Detection, among its opt-in features. Signals are flagged for review. A person has to choose Mark Fraud, Not Fraud, or Unsure, and Mark Fraud archives the candidate with the reason Rejected by Organization: Fraudulent Candidate. The page doesn’t list the signals used.

What should I check before submitting?

Check that the file is under 16MB with selectable text, that your multi-word skills and titles appear in full, and that every required form answer is accurate. Then compare the job description with your experience and add only terms you can back up.

// sources

Evidence reviewed · 6 published sources, including at least three first-party sources from the vendor or current product owner.

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