Ashby is the applicant tracking system you encounter when you apply to Linear, Vercel, Ramp, Notion's product roles, Anthropic, Mercury, or any of the roughly 2,000 well-funded post-2020 startups that picked Ashby over Greenhouse. The product launched in 2021 and grew quickly inside a specific niche: AI-native and developer-focused startups that wanted a hiring system built around data, not around the workflow conventions of previous ATS generations.
That design choice matters to applicants because Ashby behaves differently in ways that affect what gets your resume opened by a human. The differences are not cosmetic. They reflect a coherent point of view about how hiring should work.
Applying through an Ashby portal? Check these first.
- - Applications are short. The signal-per-field ratio is high. Treat every required question seriously.
- - If the posting asks for work samples or links, include them. Ashby surfaces these prominently to interviewers.
- - Custom questions in Ashby applications are usually drafted by the hiring manager, not boilerplate. Answer them like you would in a screening call.
- - Referrals carry significant weight. If you know someone at the company, ask for the formal Ashby referral link rather than emailing a recruiter your resume.
The unified data model
Most ATS platforms were built by stitching together separate modules over years: an application-tracking module, a sourcing CRM, an analytics dashboard, a scheduling tool. Each module has its own data model, and the integrations between them are often imperfect. Recruiters end up with summary numbers that do not quite add up.
Ashby was built later and took a different approach: every entity in the hiring pipeline (candidate, application, interview, scorecard, offer, hire) lives in the same data model. Recruiters and hiring managers see consistent numbers because the same record drives every view.
The implication for applicants is concrete: every action taken on your candidate record is visible to everyone in the loop. Interview feedback from a previous role you applied to, notes from a recruiter call two years ago, the source you came from originally, the score on a take-home from a different team. All of it sits on one record that any reviewer can see. Older systems lose this context across silos. Ashby preserves it.
Scorecards with weights tied to hire outcomes
Like Greenhouse, Ashby uses scorecards. Each role has a defined set of attributes that interviewers rate candidates on after every interview. The difference is that Ashby's scorecards have configurable weights, and a growing number of Ashby customers tune those weights based on data from past hires: which scorecard attributes correlated with strong performance on the job, and which did not.
The practical version: a "communication" attribute might be weighted higher than "technical depth" for a customer-facing engineering role, and the reverse for an infrastructure role on the same team. The weights are not arbitrary; they are tuned against the company's own hiring data over time.
For an applicant this means the job posting bullets matter more than usual. A bullet that reads "experience writing for non-technical audiences" in the requirements is likely a high-weight scorecard attribute, not boilerplate. Your resume should give the interviewer evidence to score you well on it.
The custom application questions are read carefully
Ashby applications tend to be shorter than Workday or iCIMS but typically include two to four custom questions written for the specific role. These questions are not screening tools the way iCIMS knockouts are. They are signal-gathering tools for the recruiter and hiring manager.
Most Ashby-customer hiring managers write these questions themselves. Examples observed across Ashby-powered hiring funnels: "What is a product you have shipped that you are most proud of, and why?" "Describe a technical decision you would make differently in hindsight." "Why this company, specifically?"
A short generic answer here is read as low interest. A two-paragraph answer with specifics about your actual experience is treated as meaningful signal. Recruiters at Ashby-powered companies routinely reject candidates whose resumes look strong but whose custom answers are perfunctory.
What "good" looks like on Ashby custom questions
Specific over general. One concrete project, one concrete decision, one concrete reason. Not a list of three things. The reviewer is looking for evidence that you have thought specifically about this company and this role, and that you can communicate clearly under a small constraint. The format of the answer is itself a sample of how you would communicate on the job.
Native analytics that drive recruiter behavior
Ashby ships analytics natively, and recruiters at Ashby-customer companies use them. Pipeline conversion rates, time-to-fill by source, offer-to-acceptance rates by referral source, scorecard pass rates by interviewer, all of it surfaces in the recruiter's daily view.
The relevant implication: source attribution affects how a recruiter treats your application. Sources with historically high quality (employee referrals, direct outreach from this recruiter, certain hand-picked job boards) get prioritized review. Sources with historically low quality (broad job aggregators, mass-application tools) get deprioritized.
Ashby tracks source automatically from the URL parameters on the application link. Applying directly through the company's careers page typically tags you as "direct." Applying through LinkedIn Easy Apply or Indeed tags you with that source. A referral link from an employee tags you as a referred candidate, and the referrer is recorded on your record. The tags are visible to the recruiter from the first glance.
Resume parsing in Ashby
Ashby's parser is competent on standard formats and indistinguishable from Greenhouse's or Lever's in terms of what it handles well and what it fails on. Single-column PDF or DOCX with conventional section headers parses cleanly. Multi-column layouts, embedded tables, content in headers or footers, and creative section titles produce degraded structured profiles.
Unlike strict-screening ATS systems, the parsed profile is supplementary at Ashby. Recruiters open the original PDF and read it. The parsed data is used for searches, filters, and pipeline analytics, not for first- pass automated screening. A badly parsed resume still gets opened. It just becomes less discoverable in later searches.
What recruiters see when your application lands
The Ashby recruiter view is a candidate card showing your resume thumbnail, parsed summary, source attribution, custom question answers, and a panel of pipeline analytics for the role (how many candidates are in each stage, what the conversion rates look like). The default sort is by application date, not by automated match score; recruiters work through their queue in order.
The recruiter sees the custom question answers prominently in the card, typically above the resume thumbnail. As in Lever, the cover-letter equivalent (the custom questions in Ashby's case) is read first and determines whether the resume is read carefully or skimmed.
Ashby is the ATS where small-effort signals (specific custom answers, clean source attribution, referral links used correctly) compound into meaningful queue priority. The applicant who treats every field as if a thoughtful person is reading it tends to outperform the applicant with a slightly stronger resume who treats the application as a form to fill out.
How Ajusta accounts for Ashby-specific behavior
When Ajusta detects an Ashby job posting (URL contains jobs.ashbyhq.com or ashbyhq.com/careers), the optimization weights scorecard-mapping and custom-question signal higher than at strict-screening ATS systems. Ajusta also surfaces the requirements list as likely scorecard attributes and checks that your resume gives an interviewer specific evidence to score you on each one. The keyword check still runs, but readability and per-requirement evidence outweigh keyword density in the final score.
Frequently asked questions
What is Ashby and who uses it?
Ashby is an applicant tracking system launched in 2021. It is concentrated among post-2020 tech startups that wanted a hiring system designed around data and analytics rather than around the workflow conventions of older ATS platforms. Linear, Vercel, Ramp, Anthropic, Mercury, and Notion (for some teams) are representative customers.
Is Ashby better for applicants than Greenhouse?
Similar in many ways. Both are recruiter-first systems that do not aggressively auto-screen. The differences are at the margin: Ashby's custom questions are typically more role-specific and weighted more heavily in review, Ashby's source attribution is more visible to recruiters, and Ashby's scorecards have configurable weights tied to past hire outcomes. The applicant playbook is similar.
How does Ashby use AI in candidate evaluation?
Ashby offers AI-assisted features for recruiters (resume summaries, similar-candidate searches, draft outreach messages), but it does not run automated screening that removes candidates from the queue. The matching engine surfaces ranking suggestions; a human recruiter is in the loop for every meaningful decision.
Why do Ashby applications ask custom questions instead of just a resume?
The questions are designed by the hiring manager, not generic boilerplate, and they are read carefully by the recruiter as part of the first review. Ashby-customer companies treat custom question answers as a writing sample and an interest signal. A perfunctory answer often closes the door even when the resume is strong.
Does Ashby track where my application came from?
Yes. Ashby uses URL parameters on the application link to attribute source automatically. Direct applications through the company careers page tag as direct. LinkedIn, Indeed, and other job boards tag as those sources. Employee referral links tag the application with the referring employee. Source attribution affects how recruiters prioritize review.
How important are referrals at Ashby-powered companies?
Substantially. Ashby's analytics make the outcome difference between referred candidates and other sources visible to recruiters, and referred candidates are reviewed faster and at higher rates at most Ashby customers. If you know someone at the company, ask for the formal Ashby referral link rather than sending a recruiter your resume separately.
Can I tell if a company uses Ashby?
Check the careers page URL. Ashby-powered postings live at jobs.ashbyhq.com/[company-name] or at the company's own careers domain proxying to Ashby. The application interface has a distinctive look: a single-page form with the role description on one side and the application fields on the other, modern typography, no multi-step wizard.
Does Ashby work for jobs in countries outside the US?
Yes. Ashby supports multi-country hiring with localization for required fields and compliance disclosures. Many Ashby customers are US-headquartered companies hiring globally; the platform handles GDPR consent, country-specific work authorization questions, and currency-aware offer details when the underlying compensation data is captured.
How long does Ashby keep my data after rejection?
Indefinitely by default, scoped to the one employer. Each Ashby-customer instance maintains a long-term candidate record. Recruiters at the company can search the database and surface your record when new roles open up. If you want your data removed, contact the employer's recruiting team and request deletion under the relevant privacy regulation (CCPA, GDPR, etc).