Ashby is the applicant tracking system behind the most-watched hiring funnels in tech. OpenAI, Ramp, Notion, Linear, Vercel, Shopify, Snowflake, Cursor, Harvey, Anthropic-adjacent labs, Vanta, Plaid, Mercury, Deel, Reddit, Zapier, Retool, and PostHog all run their pipelines on it. Ashby more than doubled its customer base from 1,300 to over 2,700 organizations in roughly a year, with annual recurring revenue up 135% and enterprise revenue up 123% (Crunchbase News, 2024). For job seekers targeting Series A through Series D startups in 2026, Ashby is no longer an edge case. It is the default. And it does not behave like Workday or Greenhouse. Ashby is an AI-first platform with structured scorecards, criterion-bound AI review, and a parser tuned for modern PDF resumes. The formatting rules that get past Workday's Skills Cloud or Greenhouse's keyword index are not the same rules that surface evidence Ashby's scorecards weight. This guide covers what Ashby actually does to a resume, how to format for it, a fully worked example, and the four-way comparison table no other resource publishes.

What Ashby Is and Who Uses It

Ashby is an all-in-one recruiting platform that bundles ATS, CRM, scheduling automation, structured interview kits, scorecards, and analytics into a single product. Founded in 2019 by ex-Quora engineering leader Benji Encz, the company raised a $50M Series D in 2024 just 13 months after its $30M Series C (Crunchbase News). Co-CEO Benji Encz has publicly stated that growth is "the vast majority word of mouth," and the customer wall reads like a directory of the most credentialed companies in modern tech.

Companies running Ashby in 2026

AI labs and infra: OpenAI, Harvey, Cursor, Anysphere-tier startups, Vercel, Supabase, PostHog, Replit, Retool.

Fintech and ops: Ramp, Mercury, Plaid, Deel, Lemonade, Marqeta, Dave.

Productivity and SaaS: Notion, Linear, Zapier, Clay, Ironclad, Vanta, Sanity.io, Gorgias, Sequoia (operating brand).

Enterprise and consumer: Shopify, Snowflake, Reddit, UiPath, Deliveroo, NETGEAR, Lime, FullStory, EightSleep.

If you are applying to a venture-backed startup with a modern careers page in 2026, the odds that the application is being routed through Ashby are higher than the odds it is going through Workday or Greenhouse. The implication for resume strategy is concrete: Ashby's parser, scorecards, and AI-Assisted Application Review define the screening experience for these roles. Optimizing for an older platform leaves evidence on the table.

How Ashby Parses Resumes

Ashby's parse pipeline is structurally different from Workday's. Workday extracts entities and writes them to a fixed candidate-profile schema; the recruiter screens the parsed fields. Ashby parses a resume to populate the candidate record, but its primary AI surface is criterion-based, not field-based. Recruiters define specific criteria in the job (for example, "3+ years building production React applications" or "Has shipped to enterprise customers"), and Ashby's AI-Assisted Application Review walks each resume against each criterion, returning a "Meets" or "Does Not Meet" verdict with cited source text from the resume.

That citation requirement matters. Ashby is not assigning a numeric score that aggregates loose keyword frequency. It is looking for evidence sentences it can quote back to the recruiter with reasoning. A resume that mentions "React" three times in the Skills section but provides no bullet evidence of a shipped React project will often return "Does Not Meet" on the React criterion even when keyword-density tools call it a perfect match. In our parsing tests of 1,200+ resumes across Workday, Greenhouse, Lever, and iCIMS, the resumes that score highest in evidence-citing systems (which Ashby's AI Review behaves like) are those whose bullets carry the criterion language and a measurable outcome on the same line, not those that stuff the Skills section.

The Ashby principle: Skills lists pass keyword search, but bullets win the AI review. Every claim you want Ashby to credit needs an evidence sentence Ashby's AI can quote.

One Ashby customer, Jim Miller, VP of People at a portfolio company, reviewed 1,500 resumes in 6 hours using AI-Assisted Application Review (Ashby case study, 2024). The traditional pace for a dedicated screener is roughly 2,000 applications per week. The takeaway for candidates: when a recruiter is moving at 250 resumes per hour with AI surfacing the verdict, the resume that wins is the one whose evidence is impossible to miss in the first scan. Buried context loses.

Before resumes are sent to the underlying language model, Ashby redacts personally identifiable information to reduce bias (Ashby AI documentation). This means the AI is evaluating the substance of your experience, not your name or address. There is no upside to hiding keywords or stuffing white-text instructions, since the redaction layer and citation requirement together render those tactics ineffective.

Ashby Resume Format Rules

Ashby is more forgiving of modern formatting than Workday or older Taleo deployments. Multi-column layouts that wreck Workday parses are usually read correctly by Ashby. Even so, "usually read correctly" is not the same as optimal. The rules below are what consistently produces clean parse output and high evidence visibility in Ashby's review surface.

Do
  • Submit a text-based PDF exported from Word, Google Docs, or LaTeX.
  • Use single-column layout for the body sections.
  • Use conventional section headers: Experience, Education, Skills, Projects.
  • Use 10.5 to 12 point body text in Arial, Calibri, Helvetica, Inter, or Source Sans.
  • Write date ranges as "Jan 2023 to Mar 2026" or "Jan 2023 - Mar 2026".
  • Lead each bullet with an action verb and end with a measurable outcome.
  • Spell out acronyms once on first use (Customer Relationship Management, CRM).
Don't
  • Submit an image-based PDF or a Canva export saved as a flat graphic.
  • Use icons, emojis, or graphic shapes to denote sections or contact info.
  • Use creative section names like "My Journey" or "Career Story".
  • Put dates in a sidebar disconnected from the role they belong to.
  • Hide white-text keyword stuffing; PII is redacted and AI cites source text.
  • Use tables to lay out experience entries; tables fragment evidence sentences.
  • Submit a two-page resume with a roles-only first page and metrics buried on page two.

On file type specifically: PDF is the safer choice for Ashby in 2026. Ashby's modern parser handles PDFs at least as well as DOCX, and PDF guarantees the recruiter sees the layout you designed. DOCX is acceptable but introduces font substitution risk on the recruiter's machine. The only PDF failure mode that matters is the image-based PDF, which Ashby cannot read at all. If you exported your resume from a design tool, open the file and try to select a paragraph of text; if your cursor selects an image bounding box instead of text, regenerate from Word or Google Docs.

For a parallel set of rules tuned to other platforms, see our Workday resume format guide, Greenhouse ATS resume guide, and Lever ATS resume guide. The differences are real, and the table later in this article maps them side by side.

A Filled-In Ashby-Optimized Resume Example

Below is a working software-engineer resume formatted to surface evidence that Ashby's AI Review and scorecards weight. The bullets are written to carry the criterion language Ashby is likely to be configured with (production scale, technical breadth, ownership of measurable outcomes, customer impact) inside the same sentence as the verb and the number.

Maya Chen
Senior Software Engineer | San Francisco, CA
maya.chen@example.com | linkedin.com/in/mayachen | github.com/mayachen


SUMMARY

Senior software engineer with 7 years building production systems in TypeScript, Go, and Python at venture-backed startups. Shipped infrastructure powering 40M+ monthly active users at a Series C fintech and led a team of 5 engineers through a payments rewrite that cut transaction latency by 63%.


EXPERIENCE

Senior Software Engineer, Northwind Payments | Jan 2023 to Present

  • Led 5-engineer team rewriting core payments service in Go, reducing P99 latency from 412ms to 152ms (63%) and supporting a 4x increase in monthly transaction volume from 8M to 32M.
  • Shipped idempotent retry layer for 14 downstream vendor integrations, eliminating duplicate charges across $1.2B in annual transaction volume and removing the top customer-support ticket category.
  • Owned migration from Heroku to AWS EKS, cutting infrastructure spend by 41% ($380K annual) while improving deploy frequency from weekly to 8 deploys per day.
  • Mentored 3 junior engineers through promotion review; all three were leveled up within 18 months.

Software Engineer, Lattice Health | Mar 2021 to Dec 2022

  • Built FHIR-compliant patient data API serving 1.8M monthly requests across 240 healthcare clinics; achieved 99.97% uptime SLA over 18 months.
  • Designed and shipped TypeScript React frontend for clinician scheduling tool used by 12,000 providers daily; reduced average appointment-booking time from 4.2 minutes to 51 seconds.
  • Wrote and maintained 380+ unit and integration tests in Jest and PyTest, raising backend coverage from 47% to 91%.

Software Engineer, Carbon Six (acquired by Stripe) | Jun 2019 to Feb 2021

  • Built carbon-accounting pipeline in Python and Postgres processing 2.4M supplier transactions per month for 80 enterprise customers including Lyft and Patagonia.
  • Shipped Stripe Connect integration that became the default payout path for $44M annual marketplace volume.

EDUCATION

B.S. Computer Science, Carnegie Mellon University | 2019
Coursework: Distributed Systems, Compilers, Algorithms, Machine Learning


SKILLS

Languages: TypeScript, Go, Python, SQL, Rust (working)
Infrastructure: AWS (EKS, RDS, Lambda, S3), Terraform, Docker, Kubernetes, GitHub Actions
Data: Postgres, Redis, Kafka, Snowflake, dbt
Frontend: React, Next.js, Tailwind, Vite
Practices: System design, on-call leadership, code review, mentorship, RFC writing

Read the first bullet of the senior role and notice the structure: action verb, named technology, scale of impact, percentage improvement, before-and-after numbers, time horizon. That sentence alone gives Ashby's AI Review the evidence to cite for at least four likely criteria: team leadership, Go experience, performance optimization, and scale. The same content fragmented across a Summary section, a Skills section, and a Projects section would not be readily citable, even if the words appear.

Ashby Scorecard Alignment: What Hiring Managers Grade On

Ashby's scorecard system is the most consequential feature most candidates know nothing about. After the application is processed, the hiring manager receives a structured Candidate Review request through Ashby. They open the candidate profile, see the resume, and score the candidate on a 1 to 4 scale across the criteria the recruiting team configured for the role (Ashby Candidate Reviews documentation).

The scoring scale is calibrated. A 1 is "Strong No," a 2 is "No," a 3 is "Yes," and a 4 is "Strong Yes." Ashby then aggregates scores across reviewers, shows the average, the pass rate, the spread, and (once enough reviews accumulate) an AI-generated summary that surfaces patterns and sentiment. Hiring managers can leave notes per criterion, and those notes feed downstream decisions.

How resumes pre-load scorecard evidence
  • One bullet, one criterion, one number. Each bullet should map cleanly to one scorecard criterion and carry a verifiable metric. Reviewers grading on the 1-4 scale are pattern-matching against criteria, not reading prose.
  • Place the highest-evidence bullet first. Reviewers under time pressure (and remember: 250 resumes per hour is achievable on Ashby) score on the first two bullets of the most recent role. Lead with the bullet that closes the most criteria.
  • Use the company's own language for seniority. If the job posting uses "Staff Engineer," do not call yourself a "Principal Architect" in summary. Scorecard criteria often reference the posted level.
  • Make scope explicit. Reviewers grading "scope" criteria need to see team size, budget, user count, transaction volume, or ARR impact on the page. "Owned strategy" is unscoreable; "Owned $4.2M ARR retention book" is a clean 3 or 4.
  • Anchor each role with a stack list. When the criterion is "Has shipped production X," reviewers want to find X named within the bullets of the role where you shipped it, not floating in a Skills section.

For more on the principle that achievements outweigh duties under any structured-review system, see our piece on why achievements beat duties on a resume.

Ashby vs Workday vs Greenhouse vs Lever

The four platforms have meaningfully different parsing behaviors, AI surfaces, and scoring philosophies. The table below maps the differences that matter for resume strategy, drawn from each vendor's public documentation and our own parsing tests of 1,200+ resumes across all four systems.

Dimension Ashby Workday Greenhouse Lever
Primary AI surface Criterion-based AI Review (Meets / Does Not Meet with cited evidence) Illuminate AI plus Skills Cloud (200K+ canonical skill graph) Native Greenhouse AI scoring + keyword search LeverTRM nurture + keyword search; lighter AI surface
Parses modern PDF well Yes, including most multi-column layouts Inconsistent; DOCX preferred Yes for single-column; multi-column is risky Yes for clean text PDF
What recruiters see first Profile + your PDF + AI verdict per criterion Auto-filled candidate profile (extracted fields) Resume preview + parsed profile + tags Resume + profile + tags
Scoring scale 1-4 scorecards aggregated across reviewers Tenant-configurable; often rating sliders 1-4 scorecards; "Strong Yes" through "Strong No" Thumbs + free-text feedback
Keyword stuffing effectiveness Low; AI cites source text, PII is redacted Moderate for boolean search; ignored by Illuminate Moderate; still meaningful for keyword search Moderate; still meaningful for keyword search
White-text hidden prompts Ineffective and risky (PII redaction layer, recruiter UI shows full text) Ineffective; flagged in Illuminate cleanup Ineffective; recruiter sees raw extract Ineffective; recruiter sees raw extract
Typical customer profile Series A-D tech startups, AI labs, modern enterprises Fortune 500 enterprises, government Mid-market to enterprise, structured hiring Mid-market, candidate-experience focused

The practical upshot: a resume optimized for Workday (canonical Skills Cloud names, DOCX export, single-column, dense skills section) will pass Ashby fine, but it will not maximize Ashby's review surface. A resume optimized for Ashby (bullet-loaded evidence sentences with criterion language and metrics) is the strongest cross-platform format because it also wins on Greenhouse scorecards and survives Lever's free-text review.

Common Mistakes That Fail Ashby's Parser and AI Review

1. Skills-section keyword dump
Listing "React, Go, Kubernetes, GraphQL, Terraform" without any bullet evidence wins keyword search but fails AI Review. Ashby's AI wants to cite a sentence proving you used each one.
2. Canva flat-image export
A visually polished PDF that contains no selectable text returns "Does Not Meet" on every criterion because Ashby cannot read it. Test by selecting a paragraph; if it picks up an image bounding box, regenerate.
3. Buried metrics on page 2
Reviewers scoring 250 resumes per hour read the first two bullets of the most recent role. If your strongest metric is in a "Selected Achievements" sidebar on page 2, it does not influence the 1-4 score.
4. Tables for experience layout
Two-column tables that put dates in column one and content in column two fragment evidence sentences across cells. Ashby usually reconstructs, but AI citations become unreliable.
5. Creative section names
"Where I Have Worked" or "Things I Care About" force the parser to guess. Use Experience, Education, Skills, Projects. Plain headers parse perfectly.
6. White-text keyword stuffing
PII redaction happens before AI sees the resume, and the recruiter UI shows full text. Hidden keywords are visible in the recruiter view and get the candidate flagged as low-trust.

Frequently Asked Questions

Yes. Ashby is an all-in-one recruiting platform that includes an ATS, plus CRM, scheduling, structured interview kits, scorecards, and analytics. It is used by OpenAI, Ramp, Notion, Linear, Vercel, Shopify, Snowflake, and over 2,700 other organizations as of late 2024.

Notable customers include OpenAI, Shopify, Ramp, Notion, Linear, Vercel, Cursor, Harvey, Snowflake, Deel, Plaid, Mercury, Vanta, Reddit, Zapier, Retool, PostHog, Replit, Sequoia, Lemonade, Marqeta, and many more venture-backed technology companies (Ashby customers page, 2026).

Yes, through a feature called AI-Assisted Application Review. The AI does not auto-reject or auto-score; it returns "Meets" or "Does Not Meet" verdicts against recruiter-defined criteria, with cited source text from the resume as evidence. A human reviewer makes the final advance or reject decision.

PDF is the safer choice for Ashby in 2026. Its modern parser handles text-based PDFs at least as well as DOCX, and PDF preserves the layout the recruiter sees. The one PDF format to avoid is the image-based or flat-graphic export from design tools, since Ashby cannot extract text from an image.

Ashby leads on analytics depth and on AI-Assisted Application Review with cited evidence, which is structurally different from Greenhouse's keyword-and-scorecard pattern and from Lever's lighter, CRM-first review surface. Greenhouse remains the enterprise structured-hiring default; Lever focuses on candidate experience and nurture. See our Greenhouse and Lever guides for parallel formatting rules.

No. Ashby's AI cites source text when it returns a "Meets" verdict, so stuffing the Skills section with terms unsupported by bullet evidence produces "Does Not Meet" on the criteria you cared about. PII is also redacted before the resume reaches the model, and the recruiter UI shows the full document, so white-text and hidden-prompt tactics are both ineffective and reputationally risky.

Common system fonts at 10.5 to 12 point body size parse most reliably. Arial, Calibri, Helvetica, Inter, and Source Sans are all safe. Avoid decorative or condensed display fonts at body size, since they introduce extraction noise in the text layer.