> the honest answer, not the myth

Will Your Resume Pass Workable?

You applied for a role through a Workable-powered careers page — uploaded your resume, filled in the fields, answered a few yes/no questions — and shortly afterward found a rejection notice in your inbox without any human having seemed to look. If that sounds familiar, the explanation is almost certainly Workable's auto-disqualify feature, not a resume-reading algorithm. Here's what Workable actually does with your resume and application, based on Workable's own help documentation — and a free in-browser check that shows what the parser sees without your file ever leaving your device.

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.

// what actually happens

What Workable actually does with your resume

When you submit an application through a Workable-powered careers page, the system does two things: it stores your resume file exactly as submitted, and it runs a parser that extracts your contact details, work history, education, and skills into a searchable candidate record. That parsed record is what recruiters can search later using keyword and boolean queries — it's not your PDF, it's the structured data the parser pulled from it. Workable's parser handles PDF and DOCX formats; complex layouts, tables, and two-column designs reduce parse accuracy and leave fields empty or wrong.

The documented automatic rejection path in Workable is the auto-disqualify feature tied to Yes/No application questions. According to Workable's help documentation, employers can mark specific Yes/No questions as knockout questions — and candidates who answer 'No' to at least one of them are automatically placed in the Disqualified tab within the Applied stage, without the recruiter taking any action. The feature works only on Yes/No question types. The candidate is not told which answer triggered the disqualification; they receive an application-received confirmation and may later receive a rejection email if the employer has configured automated rejection emails for disqualified candidates.

Outside of the knockout question path, Workable moves candidates through a pipeline the recruiter configures: Applied → Shortlisted → Interview stages → Offer. Recruiters work through the Applied queue, using keyword search against parsed resume text, filtering by application question answers, and reviewing Workable's AI-generated candidate match suggestions. There is no documented Workable feature that automatically rejects a candidate based on resume content, keyword density, or a resume score — the resume informs recruiter decisions, it doesn't drive automated ones.

// myth vs reality

What candidates believe — and what's documented

mythWorkable's AI scored my resume and rejected me automatically.
realityWorkable's AI assists recruiters with candidate recommendations and resume matching suggestions — it does not make rejection decisions. The only documented automatic rejection path in Workable is the employer-configured knockout question: a Yes/No application question where a 'No' answer triggers auto-disqualification, per Workable's own help docs.
mythI was rejected instantly, so a bot read my resume and binned it.
realityAn instant rejection in Workable almost always traces to a knockout Yes/No question. According to Workable's documentation, candidates who answer 'No' to an employer-designated knockout question are automatically placed in the Disqualified tab — without a recruiter touching anything. That's a rule on your question answer, not software analyzing your resume.
mythMy resume needs to score above a threshold to be seen by a recruiter.
realityThere is no public match-score threshold in Workable that blocks resumes from reaching recruiters. Every submitted application lands in the Applied queue. Workable's AI matching surfaces candidate recommendations, but all applications are accessible to the recruiter — the AI narrows focus, it doesn't auto-reject.
mythWorkable can't parse PDFs — you have to submit a Word document.
realityWorkable parses both PDF and DOCX. What genuinely hurts parsing is layout complexity: tables, two-column designs, text boxes, headers, and footers. A clean, single-column text-based PDF parses accurately. The format matters less than the layout.

// the real rejection mechanism

How recruiters use Workable on their side

Inside Workable, a recruiter opens a job and sees a candidate list in the Applied stage — sorted by application date by default, with disqualified candidates already in a separate tab. The recruiter can filter by screening question answers, run keyword searches across parsed resume text, and use Workable's AI-powered candidate match scores to prioritize who to review first. Harvard Business School research found more than 90% of employers use software this way to filter or rank applicants — and 88% admit this screens out qualified candidates. The AI match score is a signal, not a gate.

When a recruiter clicks into a candidate, they see both the original uploaded resume file and the parsed profile fields side by side. Rejection — in Workable's pipeline terminology, 'disqualifying' — is an action a recruiter takes when they decide a candidate isn't moving forward; it's not something the software does automatically based on resume content. The exception is the knockout question: that disqualification is automatic, happens at the moment of application, and is logged in the activity trail as 'Auto-disqualified.'

// before you apply

Resume tips specific to Workable

Answer every Yes/No application question carefully
Workable's only documented automatic rejection path is an employer-configured knockout question — a Yes/No question where 'No' triggers instant disqualification. These cover requirements like work authorization, required certifications, or location. There's no way to know which questions are knockouts before you apply, so read every one.
Use a single-column layout without tables or text boxes
Workable's parser reads linear text. Two-column designs, tables, and content in text boxes or shapes break the extraction and leave your parsed profile incomplete. A recruiter searching for a skill you have won't find it if the parser missed it.
Submit a text-based PDF or a clean DOCX
Workable accepts PDF and DOCX. Image-based PDFs (scanned or graphic-design exports) produce empty parsed profiles. To verify: open your PDF and try to select and copy the text. If you can't, neither can Workable's parser.
Keep contact information in the document body
Text placed in headers and footers is often skipped by parsers. Put your name, phone, email, and location as the first lines of the document body — before any section heading — so the parser captures your contact record correctly.
Use the same skill and title language as the job posting
Recruiters search the parsed text with keywords from the job description. Workable also uses the parsed keywords for its AI candidate match suggestions. If the posting says 'Google Analytics' and your resume says 'web analytics platforms,' a search for the specific tool won't surface you.

Check your resume before you submit →

Frequently asked questions

Does Workable auto-reject resumes?

Not based on resume content. Workable's documented automatic rejection (called auto-disqualification) is triggered by a candidate answering 'No' to an employer-configured knockout Yes/No question on the application form. Resume content, keywords, or formatting do not trigger automatic rejection in Workable.

How does Workable's auto-disqualify feature work?

Employers can designate specific Yes/No application questions as knockout questions. If a candidate answers 'No' to at least one knockout question, Workable automatically moves them to the Disqualified tab — without recruiter action. The candidate receives a confirmation email but isn't told which answer caused the disqualification. This feature works only with Yes/No question types, per Workable's help documentation.

Is my resume safe with ATSGrader's Workable checker?

Yes. ATSGrader runs entirely in your browser — your resume is never sent to any server, and we are not affiliated with Workable. Nothing leaves your device.

Does Workable score or rank my resume?

Workable uses AI to generate candidate match suggestions that help recruiters prioritize, but this is a ranking signal visible to recruiters — not a threshold that automatically rejects applications. Every submitted application is accessible in the recruiter's queue regardless of match score.

Why did my Workable application status never change?

Workable pipeline stages only advance when a recruiter takes action. On high-volume roles, candidates in the Applied stage may sit for weeks before anyone reviews them. Silence usually means 'not yet reviewed,' not 'rejected.' A formal disqualification in Workable generates a log entry and, if configured, a rejection email.

// sources

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