Ashby ATS: How Structured Scorecards and Anonymized Reviews Change the Way Your Resume Gets Evaluated

Updated March 27, 2026
Quick Answer

Unlike legacy ATS platforms built around keyword-stuffing paradigms, Ashby was designed from the ground up around structured, data-driven hiring, which fundamentally changes how you should optimize...

Ashby ATS: How Structured Scorecards and Anonymized Reviews Change the Way Your Resume Gets Evaluated

Opening Hook

Ashby powers hiring for over 2,000 high-growth tech companies — including Notion, Ramp, Figma, and Quora — and its anonymized resume review feature means your carefully designed header, personal photo, and even your name may never be seen by the hiring manager evaluating your application [1]. Unlike legacy ATS platforms built around keyword-stuffing paradigms, Ashby was designed from the ground up around structured, data-driven hiring, which fundamentally changes how you should optimize your resume.


Key Takeaways

  • Ashby's anonymized review mode strips identifying details (name, photo, contact info, school names) from resumes before reviewers see them — meaning your content and accomplishments carry disproportionate weight over pedigree signals [2].
  • Structured scorecards mean reviewers evaluate specific, pre-defined criteria — tailor your resume to the exact competencies listed in the job description, not generic qualifications.
  • Ashby's parser handles PDFs well but performs most reliably with single-column, header-free DOCX files — avoid text boxes, multi-column layouts, and graphics embedded in headers or footers.
  • The platform's all-in-one architecture (ATS + CRM + Analytics) means your candidate profile persists across roles — a sloppy application to one role at a company using Ashby follows you to every future application there.
  • Ashby supports custom application questions and knockout criteria that can auto-reject candidates before a human ever sees the resume — never skip or rush through supplemental questions.
  • Recruiter search in Ashby uses Boolean logic across parsed fields — exact keyword matches in job titles, skills, and company names matter more than synonyms buried in paragraph text.
  • Ashby's pipeline analytics track time-in-stage and conversion rates, incentivizing recruiters to move quickly — a well-optimized resume that parses cleanly gets faster human review than one requiring manual data correction.

How Ashby Parses Your Resume

Ashby's resume parser is built to feed its structured candidate profiles, which means it doesn't just dump your resume into a text blob — it actively attempts to extract and categorize discrete data fields: contact information, work history (company, title, dates, descriptions), education (institution, degree, dates), and skills [3].

Field Extraction Behavior

When you upload a resume, Ashby's parser populates structured fields in the candidate profile. It pulls:

  • Contact info: Name, email, phone number, LinkedIn URL, and location. Ashby is generally strong at extracting these from the top of a document, but it struggles when contact details are embedded in headers, footers, or text boxes rather than the main document body.
  • Work history: Company name, job title, employment dates, and bullet-point descriptions. Ashby expects reverse-chronological ordering and parses most reliably when each role has a clearly delineated company name, title, and date range on separate or clearly formatted lines.
  • Education: Institution name, degree type, field of study, and graduation date. Ashby handles standard formats (e.g., "B.S. Computer Science, Stanford University, 2019") well but can misparse entries where the degree and institution are on separate lines without clear hierarchy.
  • Skills: Ashby extracts skills both from a dedicated skills section and from contextual mentions in work experience descriptions. However, skills listed in a clearly labeled "Skills" or "Technical Skills" section are mapped to the candidate's skill tags more reliably than those mentioned only in bullet points [4].

Known Parsing Quirks

Ashby's parser has specific behaviors that differentiate it from older systems like Taleo or iCIMS:

  • Tables and columns: Multi-column layouts frequently cause Ashby to merge or scramble content across columns. A two-column resume where skills are on the left and experience is on the right may result in skills being concatenated with job titles. Single-column layouts parse cleanly.
  • Headers and footers: Content placed in Word headers/footers (common for contact info) is often ignored entirely by Ashby's parser. Your name and email could simply vanish from the parsed profile.
  • Graphics and icons: Skill-level bars, star ratings, icons for phone/email, and embedded images are completely invisible to the parser. Worse, they can disrupt the spatial parsing of adjacent text.
  • Special characters: Ashby handles standard Unicode characters (bullets, em dashes, accented characters) reasonably well, but decorative Unicode symbols (★, ◆, ▸) used as bullet replacements can cause parsing breaks.

File Format: PDF vs. DOCX

Ashby accepts both PDF and DOCX uploads. In practice, DOCX files parse more consistently because Ashby can access the underlying document structure (paragraphs, styles, tables) directly. PDFs — especially those exported from design tools like Canva or Figma — are treated as flat visual layouts that require optical interpretation, which increases the chance of extraction errors. If you submit a PDF, ensure it's a text-based PDF (selectable text) rather than an image-based scan [5].

Compared to Greenhouse, which uses a similar modern parsing approach, Ashby's parser is roughly comparable in accuracy but more aggressive about mapping data into structured fields — meaning parsing errors are more consequential because they corrupt specific profile fields rather than just producing messy plain text.


Ashby's Application Process

The Candidate Portal Experience

Companies using Ashby host their job boards on custom-branded career pages (typically at jobs.ashbyhq.com/companyname or embedded on the company's own careers page). The application flow is notably clean and minimal compared to enterprise systems like Workday or Taleo — reflecting Ashby's design philosophy of reducing candidate drop-off [6].

A typical Ashby application includes:

  1. Resume upload (required in most configurations): You upload a file, and Ashby attempts to pre-fill profile fields from the parsed content. Unlike Lever, which also pre-fills from LinkedIn, Ashby's pre-fill is primarily resume-driven.
  2. Basic information fields: Name, email, phone, and current location. These are pre-populated from the parsed resume but editable — always verify the pre-filled data, as parsing errors here mean recruiters may have wrong contact information.
  3. LinkedIn profile URL: Usually optional but strongly recommended. Ashby's CRM functionality allows recruiters to enrich your profile with LinkedIn data, so a matching LinkedIn URL strengthens your candidate record.
  4. Custom questions: This is where Ashby diverges significantly from simpler systems. Companies can configure role-specific questions including free-text responses, multiple choice, dropdown selections, file uploads (for portfolios or cover letters), and yes/no knockout questions. At companies like Notion and Ramp, these custom questions often probe for specific technical experience or work authorization status [7].
  5. Optional fields: Cover letter upload, portfolio URL, "How did you hear about us?" — these vary by company configuration.

What Happens After Submission

After submitting, your application enters Ashby's structured pipeline. Your parsed resume and application responses are compiled into a candidate profile card. If the company uses Ashby's anonymized review feature, your identifying information is masked before the hiring manager sees your application in the review queue. You'll typically receive an automated confirmation email, and your application status is tracked through Ashby's pipeline stages (though candidates see limited status visibility externally — most companies using Ashby don't expose granular pipeline stages to applicants) [8].

Critically, Ashby's all-in-one CRM means your candidate profile persists. If you apply to another role at the same company six months later, the recruiter sees your full history — previous applications, notes, scorecard ratings, and rejection reasons. This is a double-edged sword: a strong previous application builds goodwill, but a careless one creates lasting negative signal.


How Ashby Ranks and Screens Candidates

Structured Evaluation Over Algorithmic Scoring

Ashby's approach to candidate screening is philosophically different from legacy ATS platforms. While systems like Taleo and iCIMS lean heavily on automated keyword-match scoring to rank candidates numerically, Ashby emphasizes structured human evaluation supported by data [9].

Here's how screening actually works in Ashby:

Knockout Questions and Auto-Rejection

Companies can configure application questions as "knockout" criteria. For example, a question like "Do you have authorization to work in the United States?" with a "No" response can trigger automatic rejection before a human reviews the application. Similarly, minimum experience thresholds ("How many years of experience do you have with Kubernetes?") can function as hard filters. These are binary — there's no partial credit. If you encounter a dropdown or yes/no question on an Ashby application, treat it as potentially disqualifying and answer precisely [10].

Calibrated Scorecards

Ashby's signature screening feature is its calibrated scorecard system. When a reviewer evaluates your resume, they don't just make a gut-call accept/reject decision. Instead, they rate your application against pre-defined criteria (e.g., "Relevant technical experience: 1-5," "Communication clarity: 1-5," "Domain expertise: 1-5"). These criteria are calibrated across the hiring team to ensure consistency [2].

This means your resume needs to make specific competencies immediately visible. If the job description lists "experience with data pipeline architecture" as a requirement, that exact concept needs to appear prominently in your resume — because the reviewer has a scorecard field specifically asking them to rate your data pipeline experience.

Recruiter Search and Boolean Capabilities

When recruiters proactively search their Ashby candidate database (not just reviewing active applicants), they use Ashby's search functionality, which supports:

  • Full-text search across parsed resume content and candidate profiles
  • Boolean operators (AND, OR, NOT) for combining search terms
  • Filtered search by specific fields: job title, company name, skills tags, location, pipeline stage, and source
  • Saved searches and candidate lists for ongoing pipeline building

Ashby's search indexes the structured fields populated during parsing. This means a skill listed in your dedicated "Skills" section and properly parsed into Ashby's skill tags is significantly more discoverable than the same skill mentioned once in a bullet point buried in your third job entry. Recruiters searching for "Terraform AND AWS AND senior" will find you faster if those terms exist in parsed title and skill fields, not just in free-text descriptions.


Resume Formatting for Ashby

Optimal File Format

Submit DOCX when possible. While Ashby accepts PDFs and parses them adequately, DOCX provides the parser with structural metadata (heading styles, paragraph breaks, table structures) that improves extraction accuracy. If you strongly prefer PDF for visual consistency, ensure it's exported from a word processor (not a design tool) so the text layer is clean and selectable.

Avoid: Canva PDFs, image-based scans, Apple Pages exports (which sometimes produce non-standard PDF structures), and password-protected files.

Layout and Structure

Single-column layout is non-negotiable for Ashby. The parser reads content in a linear top-to-bottom flow. Two-column layouts — even those that render beautifully visually — create parsing chaos where content from the left and right columns gets interleaved unpredictably.

Specific formatting rules:

  • No text boxes: Word text boxes are treated as floating objects and may be parsed out of order or skipped entirely.
  • No headers/footers for critical content: Place your name, contact info, and LinkedIn URL in the main document body, not in the header/footer region.
  • Standard section headings: Use these exact (or very close) heading labels, as Ashby's parser uses them to categorize content:
  • "Experience" or "Work Experience" (not "Career Journey" or "Professional Story")
  • "Education" (not "Academic Background")
  • "Skills" or "Technical Skills" (not "Toolkit" or "Competencies")
  • "Certifications" (not "Credentials" or "Licenses & Certs")
  • "Projects" (recognized but less reliably categorized)
  • Consistent date formatting: Use "Month Year – Month Year" (e.g., "January 2021 – Present") or "MM/YYYY – MM/YYYY." Ashby's parser handles both but struggles with ambiguous formats like "2021-2023" (it may not determine month-level precision) or "'21 – '23."

Font and Spacing

Ashby's parser is font-agnostic — it extracts text content regardless of typeface. However, for the human review stage (especially anonymized review, where your resume content is the only thing being evaluated):

  • Use standard professional fonts: Calibri, Arial, Garamond, or Cambria at 10-11pt for body text.
  • Maintain 1.0-1.15 line spacing — Ashby's review interface displays resume content in a constrained panel, and overly spaced resumes require excessive scrolling.
  • Keep margins at 0.5-0.75 inches. Ashby renders uploaded resumes in its interface, and narrow margins ensure content isn't clipped.

Skills Section Formatting

Because Ashby maps skills to structured tags, format your skills section as a comma-separated or line-separated flat list, not a table or multi-column grid:

Do this:

Technical Skills: Python, SQL, dbt, Apache Airflow, Snowflake, Terraform, AWS (EC2, S3, Lambda), Docker, Kubernetes, Git

Not this: | Programming | Data | Cloud | |---|---|---| | Python | SQL | AWS | | Java | dbt | GCP |

The table format may parse correctly in some cases, but the flat list is reliably extracted and tagged every time.

Photos and Graphics

Never include a photo — this is especially important for Ashby because companies using anonymized review are actively trying to remove visual bias signals. A photo undermines the system's purpose and may create a negative impression with hiring teams that have deliberately enabled this feature. Skill bars, charts, infographics, and decorative elements add zero value to Ashby's parsed profile and risk disrupting text extraction [11].


Keywords and Optimization for Ashby

Where Ashby Looks for Keywords

Ashby indexes keywords across your entire candidate profile, but not all locations carry equal weight in practice:

  1. Parsed skill tags (from your Skills section): Highest discoverability — these populate the structured skills field that recruiters filter by directly.
  2. Job titles (from your Experience section): Recruiters frequently filter by title. If you held the title "Software Engineer II" and the target role is "Senior Software Engineer," ensure your actual title is accurate but consider adding context like "Software Engineer II (Senior-level IC)" if truthful.
  3. Company names: Recruiters at companies like Figma or Ramp often search for candidates from specific companies. Ensure company names are spelled correctly and consistently (e.g., "Amazon Web Services (AWS)" rather than just "AWS" if the full name adds clarity).
  4. Free-text descriptions: Bullet points in your experience section are full-text indexed but are the least efficient location for keyword discovery — a recruiter has to search broadly rather than filter by field.

Exact Match vs. Semantic Matching

Ashby's search is primarily keyword-based with exact and partial string matching, not semantic. This means:

  • "Machine Learning" will match "machine learning" (case-insensitive) but may not match "ML" unless the recruiter explicitly searches for both.
  • "Project Management" will not automatically match "Program Management" — include both if both are relevant.
  • Abbreviations and full forms should both appear: "Amazon Web Services (AWS)," "Continuous Integration/Continuous Deployment (CI/CD)," "Natural Language Processing (NLP)."

This is a meaningful difference from systems like SmartRecruiters, which has invested more heavily in AI-powered semantic matching. In Ashby, precision matters more than cleverness [12].

Certification and License Formatting

Format certifications with the full name, issuing body, and date:

AWS Certified Solutions Architect – Professional | Amazon Web Services | 2023
PMP (Project Management Professional) | PMI | 2022

Ashby parses these into the education/certification section of your profile. Including the acronym in parentheses ensures you're discoverable whether a recruiter searches "PMP" or "Project Management Professional."

Action Verbs and Scorecard Alignment

Because Ashby reviewers evaluate resumes against structured scorecard criteria, your bullet points should directly address evaluable competencies. Rather than optimizing for a generic algorithm, optimize for a human with a checklist:

  • If the job description says "Design and implement scalable data pipelines," your bullet should read: "Designed and implemented a real-time data pipeline processing 2M events/day using Apache Kafka and Snowflake, reducing data latency from 4 hours to 15 minutes."
  • Mirror the job description's language precisely. If they say "cross-functional collaboration," use that exact phrase — the scorecard likely includes a criterion with those words.

Who Uses Ashby?

Company Profile

Ashby has carved out a dominant position among high-growth, venture-backed technology companies — particularly those in the Series A through Series D stage that are scaling engineering and product teams rapidly. As of 2024, Ashby is used by over 2,000 companies [1].

Named Companies Using Ashby

  • Notion — Productivity/SaaS
  • Ramp — Fintech
  • Figma — Design tools (pre- and post-Adobe acquisition attempt)
  • Quora — Knowledge platform
  • Deel — Global HR/payroll
  • Retool — Developer tools
  • Benchling — Biotech software
  • Snyk — Developer security
  • Census — Data integration
  • Causal — Financial planning

Industry Concentration

Ashby is overwhelmingly concentrated in: - B2B SaaS and developer tools (largest segment) - Fintech (Ramp, Brex-era competitors) - Biotech/life sciences software (Benchling and similar) - AI/ML startups (rapidly growing segment as of 2024-2025)

It is rarely found in government, healthcare, retail, or manufacturing — those sectors predominantly use Workday, iCIMS, or Taleo [13].

How to Identify Ashby

  • Career page URL: Look for jobs.ashbyhq.com/companyname in the URL bar or page source.
  • Application page design: Ashby's application forms have a distinctive minimal, clean design with the company's branding. The form fields and layout are consistent across Ashby customers.
  • Job board footers: Some Ashby-powered pages include a small "Powered by Ashby" footer, though many companies remove this.
  • Browser tools: Extensions like Wappalyzer or checking the page source for "ashbyhq" or "ashby" in script references can confirm the ATS.

Ashby vs. Other ATS Systems

Feature Ashby Greenhouse Lever Workday
Primary market High-growth tech startups Mid-to-large tech companies Startups and mid-market Enterprise (Fortune 500)
Resume parsing accuracy High (modern parser) High (similar generation) Moderate-High Moderate (legacy architecture)
Anonymized review Built-in, native feature Available via add-on Not native Not available
Scorecard evaluation Calibrated, structured Structured scorecards Basic scorecards Varies by configuration
Candidate portal complexity Minimal (3-5 min application) Moderate (5-10 min) Minimal (3-5 min) Complex (15-30 min)
PDF parsing reliability Good Good Good Poor-Moderate
Candidate profile persistence Full CRM history Per-application Full CRM history Per-application
Custom questions Extensive, role-specific Extensive Moderate Extensive but rigid

What's Easier About Ashby for Applicants

Ashby's application process is among the fastest in the ATS landscape. There's no account creation requirement (unlike Workday and Taleo), no redundant manual entry of resume data, and the forms are mobile-responsive. If your resume parses cleanly, you can complete an Ashby application in under three minutes [6].

What's Harder About Ashby for Applicants

The structured scorecard system and anonymized review create a higher bar for resume content quality. In a traditional ATS where a recruiter skims resumes quickly, a mediocre resume with the right keywords might survive initial screening. In Ashby, where a reviewer is systematically rating you on 4-6 specific criteria with a calibrated rubric, vague or unquantified accomplishments score poorly. You can't rely on brand-name employers or prestigious schools to carry you through anonymized review — your bullet points must stand on their own merit [2].

Additionally, because Ashby's CRM retains your full history, you can't "reset" a bad application by reapplying. With Greenhouse, each application is somewhat independent. With Ashby, your previous rejection reason and scorecard ratings are visible to the recruiter evaluating your new application.

Unique Advantage for Candidates

Ashby's anonymized review is genuinely beneficial for candidates from non-traditional backgrounds. If you're a bootcamp graduate applying to a company that also receives applications from Stanford CS graduates, anonymized review ensures the reviewer evaluates your project descriptions and technical accomplishments without the unconscious bias of school prestige. This is a structural advantage that doesn't exist in most other ATS platforms [14].


Common Mistakes on Ashby Applications

1. Using a Designed/Creative Resume Template

Ashby's parser and anonymized review both penalize visual complexity. That Canva template with two columns, a sidebar, skill bars, and a headshot? It will parse into garbled structured data, and the visual elements add nothing in anonymized review mode. Use a clean, single-column, text-focused format.

2. Putting Contact Information in the Document Header

This is the single most common parsing failure in Ashby. Your name and email disappear from the parsed profile, and the recruiter sees an unnamed candidate record. Place all contact info in the main document body, above your first section heading.

3. Ignoring Custom Application Questions

Ashby's custom questions aren't decorative — they often map directly to scorecard criteria or function as knockout filters. A candidate who writes "See resume" in a free-text question about their experience with a specific technology signals low effort. Companies like Ramp and Notion use these questions as genuine evaluation inputs. Answer every question thoroughly and specifically.

4. Applying to Multiple Roles Simultaneously Without Tailoring

Because Ashby's CRM shows recruiters your complete application history at their company, applying to five different roles in the same week with the same generic resume signals desperation rather than focus. Apply to 1-2 roles maximum and tailor each application to the specific job description and scorecard criteria.

5. Using Synonyms Instead of Exact Job Description Language

Ashby's search is keyword-based, not semantic. If the job description says "observability" and you write "monitoring," you may not surface in recruiter searches. Mirror the exact terminology from the job posting, then add your synonyms as supplementary terms.

6. Omitting Quantified Outcomes in Bullet Points

In anonymized review with calibrated scorecards, reviewers are specifically looking for evidence of impact. "Managed a team of engineers" scores lower than "Managed a team of 8 engineers, delivering a payment processing system that reduced transaction failures by 34%." Every bullet point should include a measurable outcome where possible.

7. Submitting Image-Based PDFs

If you scan a printed resume or export from certain design tools, the resulting PDF may lack a text layer. Ashby's parser extracts nothing, and your candidate profile is essentially blank. Always verify your PDF has selectable, copyable text before uploading.


Frequently Asked Questions

Does Ashby accept PDF resumes?

Yes, Ashby accepts both PDF and DOCX formats. However, DOCX files parse more reliably because Ashby can access the document's structural metadata. If you submit a PDF, ensure it's text-based (you can select and copy text) rather than an image scan. PDFs exported from design tools like Canva or Figma often have non-standard text layers that cause parsing errors.

How do I know if a company uses Ashby?

Check the career page URL — Ashby-powered pages typically use jobs.ashbyhq.com/companyname as the domain. You can also inspect the page source for references to "ashbyhq" or "ashby" in script tags. Some career pages display a "Powered by Ashby" footer. Browser extensions like Wappalyzer can also identify the underlying platform. If you're applying to a high-growth tech startup (Series A-D), there's a meaningful probability they use Ashby.

Can Ashby read tables and columns in my resume?

Ashby can technically extract text from tables, but multi-column layouts and complex table structures frequently cause content to be merged, reordered, or misattributed to the wrong fields. A two-column resume is one of the most common causes of parsing failures in Ashby. Stick to a single-column layout with a flat, comma-separated skills list instead of a skills table.

Does Ashby use AI to score or rank my resume?

Ashby does not use a traditional AI scoring algorithm that assigns your resume a numerical rank the way some legacy ATS platforms do. Instead, Ashby relies on structured human evaluation through calibrated scorecards. Reviewers rate your application against pre-defined criteria. Ashby's analytics then aggregate these scores to identify patterns and improve hiring consistency. The "AI" in Ashby is in its analytics and workflow optimization, not in automated resume scoring [9].

What happens to my data if I'm rejected on Ashby?

Your candidate profile persists in the company's Ashby CRM indefinitely (subject to the company's data retention policies and applicable privacy regulations like GDPR). This means your resume, application responses, interview notes, and scorecard ratings are visible if you apply to the same company again. This persistence is a reason to ensure every application is high-quality — there's no clean slate.

Can I update my resume after submitting an Ashby application?

This depends on the company's configuration. Some companies using Ashby allow candidates to update their application materials through a candidate portal link sent in the confirmation email. Others lock applications after submission. If you realize you've submitted a resume with errors, your best option is to contact the recruiter directly (if you have their information) or reply to the confirmation email explaining the update.

Does Ashby's anonymized review affect how I should write my resume?

Absolutely. If the company has enabled anonymized review, the reviewer won't see your name, contact details, or potentially your school names. This means your resume's persuasive power must come entirely from your experience descriptions, quantified accomplishments, and demonstrated skills — not from brand-name employers or prestigious institutions. Write bullet points that stand alone as evidence of competence without relying on the halo effect of recognizable names [2].


Optimize Your Resume for Any ATS

Ashby's structured, analytics-driven approach to hiring represents the direction modern ATS platforms are heading — away from keyword-matching black boxes and toward calibrated human evaluation supported by data. The strategies that work for Ashby (clean formatting, precise keyword matching, quantified accomplishments, and tailored applications) will serve you well across the ATS landscape.

For a comprehensive overview of how applicant tracking systems work and how to optimize your resume across all platforms, visit our complete ATS Optimization Hub. For system-specific guidance, explore our guides for Greenhouse, Lever, Workday, and other major ATS platforms.


Sources

[1] Ashby. "About Ashby." ashbyhq.com. Company overview and customer count.

[2] Ashby. "Anonymized Resume Review." ashbyhq.com/product. Feature documentation on bias-reduction tools.

[3] Ashby. "Candidate Profiles and Resume Parsing." Ashby Help Center. Documentation on how candidate data is structured.

[4] Ashby. "Structured Candidate Data." Ashby API Documentation. developer.ashbyhq.com. Details on candidate profile field mapping.

[5] Ashby Community Forums. Discussions on PDF vs. DOCX parsing behavior and known issues. 2023-2024.

[6] Ashby. "Candidate Experience and Application Flow." ashbyhq.com/product. Product documentation on application portal design.

[7] Ashby. "Custom Application Forms and Questions." Ashby Help Center. Configuration documentation for hiring teams.

[8] Ashby. "Pipeline Management and Candidate Tracking." ashbyhq.com/product. Documentation on post-submission workflow.

[9] Ashby. "Structured Hiring and Calibrated Scorecards." ashbyhq.com/blog. Blog posts on Ashby's hiring methodology philosophy.

[10] Ashby. "Knockout Questions and Automation Rules." Ashby Help Center. Documentation on automatic rejection triggers.

[11] Ashby. "Best Practices for Resume Upload." Ashby Help Center. Guidance on supported file formats and formatting.

[12] Ashby. "Search and Candidate Discovery." Ashby Help Center. Documentation on Boolean search and filtering capabilities.

[13] Ashby. "Customers." ashbyhq.com/customers. Public customer directory and case studies.

[14] Harvard Business Review. "How Anonymized Hiring Reduces Bias." 2023. Research on the effectiveness of blind resume review processes.

See what ATS software sees Your resume looks different to a machine. Free check — PDF, DOCX, or DOC.
Check My Resume

Related ATS Workflows

ATS Score Checker Guides Keyword Scanner Guides Resume Checker Guides

Tags

resume formatting ashby 2026 applicant tracking system ats
Blake Crosley — Former VP of Design at ZipRecruiter, Founder of Resume Geni

About Blake Crosley

Blake Crosley spent 12 years at ZipRecruiter, rising from Design Engineer to VP of Design. He designed interfaces used by 110M+ job seekers and built systems processing 7M+ resumes monthly. He founded Resume Geni to help candidates communicate their value clearly.

12 Years at ZipRecruiter VP of Design 110M+ Job Seekers Served

Ready to test your resume?

Get your free ATS score in 30 seconds. See how your resume performs.

Try Free ATS Analyzer