Inside Ashby ATS: How Hypergrowth Startups Tag and Score 'Velocity' & 'Scope'

Traditional Applicant Tracking Systems like Lever or Greenhouse parse a resume into flat entities: job titles, companies, skills. They match keywords against a static job description. Ashby ATS recruiting software, built for companies scaling from 100 to 2000 employees, introduces a relational data model. Recruiters don't just score a candidate; they tag discrete achievements with attributes like 'Scope: Team,' 'Scope: Org,' 'Velocity: High,' or 'Complexity: High.' These tags feed a composite scorecard that weighs 'strategic impact' separately from 'technical execution.'

This architecture solves a core hypergrowth hiring problem: distinguishing between an engineer who shipped features quickly and one who defined the patterns an entire product vertical uses. In systems like Workday or iCIMS, both profiles might trigger the same keyword match for 'microservices' and 'AWS.' Ashby’s tagging forces a committee to answer: did this person operate at the level of a task, a project, a team’s mandate, or a business unit's strategy? The tags become searchable, reportable dimensions for talent analytics, far beyond a simple thumbs-up/thumbs-down.

When a recruiter reviews your resume in Ashby, they are guided by a custom scorecard. For a Staff Engineer role, the ‘Scope Impact’ section might be weighted at 40% of the total score. The recruiter’s task is to find evidence in your bullet points to apply a predefined tag. A bullet like ‘Reduced API latency by 30%’ might earn a ‘Velocity: High’ tag but leave the ‘Scope’ field empty, triggering a prompt for the recruiter to seek clarification.

Contrast this with older systems. In Greenhouse, a recruiter might simply rate ‘Technical Skills’ on a 1-5 scale. In Lever, NLP might highlight keywords but provide no framework to assess their organizational context. Taleo often uses rigid knockout rules (e.g., “MUST have 5+ years Java”) but cannot evaluate the strategic weight of those years. Ashby’s model is a hybrid: it requires human judgment, but structures that judgment into quantified, comparable data points. This is why a candidate can ‘look good’ on paper but receive a mysteriously low Ashby score—the recruiter couldn't map your experience to the required scope tags for the level.

**Weak Bullet (Fails Scope Tagging):** 'Built a new caching layer using Redis to improve performance.' This is an activity. It might earn a 'Technical Execution' tag but provides zero data for 'Scope' or 'Velocity.' The recruiter has no idea if this was a solo weekend script or a platform-wide migration.

**Strong Bullet (Triggers 'Scope: Org' & 'Velocity: High'):** 'Designed and led org-wide rollout of Redis caching layer, adopted by 12 product teams, reducing p95 API latency by 40% and cutting monthly cloud spend by $18K.' This specifies organizational reach (12 teams), quantifies speed/performance impact (40% latency reduction), and ties to a business metric (cost). The Ashby recruiter can confidently tag for high scope and velocity.

**Weak Bullet (Fails Velocity Tagging):** 'Responsible for CI/CD pipeline maintenance.' This is a job description, not a measurable result.

**Strong Bullet (Triggers 'Velocity: High' & 'Complexity: High'):** 'Automated deployment pipeline for monolith-to-microservices transition, reducing average deployment time from 90 minutes to 7 minutes and enabling team to ship 3x more frequently.' This defines the problem complexity ('monolith-to-microservices'), provides a before/after velocity metric (90min to 7min), and states the operational outcome (3x ship frequency).

The most common mistake I see in Amazon Bar Raiser debriefs and Google hiring packets is the conflation of seniority with sheer volume of work. A Principal Engineer resume packed with 15 bullet points of tactical achievements will lose to one with 5 bullets demonstrating clear organizational scope shifts. Committees aren't counting tasks; they're evaluating the radius of your influence.

This is where Ashby’s tagging formalizes an intuitive hiring committee truth. A Staff Engineer role might require at least two instances of the 'Scope: Cross-Team' tag. A candidate with ten 'Scope: Individual' tags, no matter how impressive the individual metrics, will be leveled down. The counter-intuitive rule: For roles above Senior, prune your resume of lower-scope achievements, even if they contain big numbers. One bullet proving you changed the trajectory of multiple teams is worth more than five bullets proving you were an exceptional individual contributor.

1. **Audit Each Bullet for an Action > Metric > Scope Chain.** For every bullet, ask: What did I DO? By how much did it IMPROVE? Who ELSE was impacted (my team, 3 teams, the entire org)? If you can't answer the third question, the bullet is likely tagged as low scope.

2. **Force the 'So What?' Test.** After stating a metric like 'improved QPS by 50%,' immediately append the strategic consequence: '...enabling the launch of Product X which captured $2M in new ARR' or '...allowing the data science team to reduce model training time by 6 hours.' This directly feeds the 'Business Impact' tag in Ashby scorecards.

3. **Replace Vague Verbs with Scope-Signaling Language.** Swap 'worked on' with 'architected for,' 'assisted with' with 'led the cross-functional initiative between [Team A] and [Team B].' This language explicitly guides the recruiter to higher-level tags.

4. **Create a 'Scope & Impact' Summary.** Before your Experience section, add a 2-line summary stating your highest-altitude impact: e.g., 'Engineer whose system designs have been adopted by 4 product teams, consistently reducing operational load and enabling faster iteration cycles.' This primes the recruiter to look for and tag high-scope evidence.