Frontend Engineer ATS Keywords for Tech Companies (2026)

Frontend Engineer ATS Keywords for Tech Companies (2026)

Frontend Engineer (FE) hiring at tech companies — Stripe, Vercel, Meta, Shopify, Linear, Notion, Airbnb, Figma — is a different keyword target than full-stack or generalist software-engineer hiring. Recruiters configure ATS searches around six signal classes specific to the modern frontend stack: framework keywords (React, Next.js, Vue, Svelte, Solid), language keywords (TypeScript, JavaScript, ES2024), styling keywords (Tailwind, CSS Modules, styled-components, vanilla-extract), build/tooling keywords (Vite, Turbopack, esbuild, Webpack), testing keywords (Vitest, Jest, Playwright, Cypress, Testing Library), and performance + accessibility keywords (Core Web Vitals, LCP, INP, ARIA, WCAG). A resume that names HTML/CSS/JavaScript without naming a current framework, no TypeScript, and no testing tool gets filtered out for senior FE roles because the keyword density across those six classes is too low [1][2]. This page lists the FE keywords that pass screens at tech companies in 2026, grouped by signal class, with the counter-list of keywords that backfire when a candidate leans on outdated stack choices.

Key Takeaways

• FE Engineer ATS searches at tech companies in 2026 weight six keyword classes — framework, language, styling, build/tooling, testing, performance + accessibility — and a resume missing any one of them reads as off-stack for the role [1][2].
• React + TypeScript is the dominant tech-company FE stack as of the 2024 Stack Overflow Developer Survey, where TypeScript ranked among the most-loved languages and React remained the leading web framework among professional developers [3].
• Next.js, the React meta-framework maintained by Vercel, ships React Server Components and the App Router as the default since version 13 and is the dominant production framework for new tech-company FE roles per the official documentation [4].
• Core Web Vitals — LCP, CLS, and INP (which replaced FID as a Core Web Vital in March 2024 per web.dev) — are the canonical performance metrics ATS searches scan for on senior FE resumes [5].
• Accessibility evidence (ARIA, WCAG 2.2, semantic HTML, keyboard navigation) is now table-stakes on senior FE resumes at companies that publish accessibility commitments — its absence reads as a 2018-era resume [6].
• Counter-signal keywords — jQuery as primary stack, Bootstrap-only, no TypeScript, no testing — actively hurt FE resumes at modern tech companies because they signal a stack mismatch with what the team ships [3][4].
• levels.fyi tracks Software Engineer compensation at Vercel, Stripe, Meta, and most major tech companies; the salary surface for FE-specialist roles tracks the broader SWE ladder, with FE specialists at the same level earning within the same band as backend or full-stack peers [7].

How Frontend Engineer ATS Screens Work

FE Engineer hiring runs through the same ATS engines as broader software-engineering hiring — Greenhouse, Lever, Workday, Ashby, SmartRecruiters, iCIMS — but recruiters configure the keyword filters around the FE stack rather than backend or systems-engineering signal. The screening mental model: an FE candidate must show a framework, a language (almost always TypeScript at tech companies in 2026), a styling approach, a build/test toolchain, and performance + accessibility evidence. Resumes that name only the languages (HTML/CSS/JavaScript) without a framework, or a framework without TypeScript, or a framework + TypeScript without any testing or performance signal, get downranked because the recruiter's filter is set on combinations, not individual terms [1][2].

Engine-specific behavior for FE hiring:

Greenhouse (Stripe, Notion, Linear, Robinhood, and most Series-B+ tech companies) supports semantic matching, so "React + TypeScript" registers as related to "Next.js + TypeScript" or "TSX components." Greenhouse FE recruiters typically run two-stage filters: a coarse "React or Vue or Svelte within last 2 years" pass, then a refinement on the remaining stack signal (TypeScript, testing tool, perf metric) [1].

Lever (Eventbrite, Shopify, parts of Lyft) emphasizes recency. For FE roles, "React within last 2 years" or "Next.js within last 18 months" filters are common because the framework ecosystem moves fast — a candidate whose most recent React experience is 4 years old reads as out-of-date even if the older work was strong.

Workday (Disney, Salesforce, Adobe, large-enterprise FE hires) is the strictest exact-match parser. For FE, Workday filters often require literal framework names — "React.js," "Vue.js," "Angular" — and creative naming ("a UI framework," "modern JavaScript framework") fails the screen [8]. Always name the canonical framework string.

Ashby (Notion, Linear, Ramp, Anthropic, and most modern AI-era startups) is the most forgiving FE ATS because its LLM-based scoring reads bullets in context. A bullet that describes "shipped a Next.js App Router migration with React Server Components, hit a sub-2.5s LCP on the new homepage, and added Playwright coverage on the checkout flow" registers cleanly as senior FE signal even if the candidate's title is ambiguous [9].

SmartRecruiters and iCIMS are stricter and more exact-match — both score the title block heavily and penalize creative titles. Taleo (legacy enterprise) is the oldest and the strictest; for FE Taleo searches, write defensively with the canonical framework names and the literal "frontend engineer" or "front-end developer" string in the title block [8].

Tier 1 — Framework Keywords

Framework choice is the single most-scanned FE keyword class at tech companies. The framework determines the rest of the stack expectations (language, styling, testing) and the ATS filter is almost always set on at least one canonical framework name [1][3].

React — The dominant tech-company FE framework as of the 2024 Stack Overflow Developer Survey [3]. Pattern: "Built consumer-product surfaces in React 18 + TypeScript," or "shipped a React 19 migration including the new use hook and Server Components." Naming the React major version (18, 19) signals recency.

Next.js — The Vercel-maintained React meta-framework that ships the App Router and React Server Components as the default since v13 [4]. Pattern: "shipped a Next.js 14 App Router migration with React Server Components and Server Actions," or "owned the Next.js performance budget — sub-2.5s LCP across the marketing surfaces." Tier-1 keyword for any tech-company role using React.

Vue — Strong second-tier framework signal, especially at GitLab, Zoom, and parts of Alibaba's product surface. Pattern: "Built the dashboard in Vue 3 + TypeScript with the Composition API."

Svelte / SvelteKit — Growing presence at smaller tech companies (Cloudflare, parts of Apple's docs surface, multiple AI startups). Pattern: "Shipped the marketing surface in SvelteKit with sub-1.5s LCP."

Solid / SolidStart, Qwik, Astro — Tier-2 framework keywords. Worth listing if the candidate has shipped production work in them; Astro in particular has growing adoption for content-heavy surfaces.

Angular — Still common at Google, parts of Microsoft, and large enterprise (financial-services FE). Pattern: "Built the trader-tools dashboard in Angular 17 + RxJS with strict TypeScript."

Remix / React Router 7 — Now merged with React Router under the Remix → React Router 7 transition. Worth mentioning where shipped.

Tier 1 — Language Keywords

TypeScript is now table-stakes at tech companies. Resumes that don't list TypeScript get downranked even when the underlying React experience is strong [3].

TypeScript — Mandatory mention. Pattern: "5+ years TypeScript across consumer-product and design-system surfaces." Bonus: name strict-mode usage ("strict TypeScript with noUncheckedIndexedAccess"), generics fluency, or type-driven API contracts.

JavaScript / ES2024 — Pair with TypeScript, not as a substitute. Pattern: "TypeScript + modern JavaScript (ES2024 features including pipeline operator and Object.groupBy)."

JSX / TSX — Light Tier-1 mention; pairs naturally with React. The literal "TSX" string sometimes catches stricter ATS filters that "TypeScript" alone misses.

HTML5 / Semantic HTML — List once, not as a primary skill. Recruiters at senior FE roles assume HTML fluency; the signal lives in semantic HTML and accessibility rather than the language itself.

CSS / CSS3 — List once. The depth signal lives in the styling approach (CSS Modules, styled-components, Tailwind), not in CSS itself.

WebAssembly / Wasm — Tier-2 specialist signal. List only if shipped; relevant for performance-critical FE work, audio/video apps, and design-tool FE (Figma's Wasm work, Adobe's web apps).

Tier 1 — Styling Keywords

Styling approach is heavily filtered at tech companies because it correlates with the company's design-system maturity. Modern tech companies use one of three patterns: utility-first (Tailwind), CSS Modules, or styled-components / emotion / vanilla-extract.

Tailwind CSS — Dominant utility-first framework at Vercel, Cal.com, multiple AI startups, and Stripe's docs surface. Pattern: "Tailwind CSS with custom design tokens and a preset shared across 4 surfaces."

CSS Modules — Common at Next.js shops where Tailwind isn't the primary choice. Pattern: "CSS Modules with postcss plugins and design-token integration."

styled-components / Emotion / vanilla-extract — CSS-in-JS keywords. List the specific library shipped. vanilla-extract is a senior-level signal because it's zero-runtime and harder to migrate to.

Sass / SCSS — Still present at Shopify and large-enterprise FE. List if shipped recently; if the candidate's most recent role used Tailwind, mentioning Sass adds limited additional signal.

Radix UI / Headless UI / shadcn/ui — Component-primitive signals. shadcn/ui in particular has become a Tier-1 keyword for new-tech-company FE roles because it sits at the intersection of Tailwind + Radix + design system.

Design tokens / design system — Process keyword. Pattern: "Owned design-token rollout across 11 surfaces; partnered with Design on the unified component library."

Tier 1 — Build / Tooling Keywords

Build-tool fluency signals depth at the bundler-and-config level — the FE work that hiring managers care about beyond shipping components.

Vite — Dominant modern bundler for non-Next.js React, Vue, and Svelte projects. Pattern: "Vite 5 with custom plugins for the design-system build pipeline."

Turbopack — The Vercel-built Rust bundler now stable for Next.js dev mode. Worth naming if shipped on Next.js 14+ projects [4].

esbuild — Fast bundler, often used as the underlying engine for higher-level tools. List if used for custom build pipelines.

Webpack — Still common at large companies. List if shipped, but a modern FE resume that lists only Webpack with no Vite or Turbopack reads as out-of-date.

pnpm / npm / yarn — Package manager signal. pnpm in particular has become a tech-company-de-facto signal because of its monorepo handling.

Turborepo / Nx — Monorepo tooling. Tier-1 senior-FE signal at companies running design systems across multiple product surfaces.

ESLint / Prettier / Biome — Code-quality tooling. Biome (the Rust-based combined linter/formatter) is the modernization signal here.

Storybook — Component-library tooling. Tier-1 keyword for FE roles touching the design system.

Tier 1 — Testing Keywords

Testing fluency is the keyword class most often missing from junior FE resumes — and most heavily scanned at senior FE roles. A senior FE resume with no testing tool listed reads as red-flag because senior FE work at tech companies includes test ownership [1][2].

Vitest — Modern Vite-native unit-test runner. Pattern: "Vitest unit + integration coverage on the design-system primitives."

Jest — Older but still-common React unit-testing framework. List if shipped, often paired with React Testing Library.

React Testing Library / Testing Library — User-centric component testing. Pattern: "RTL coverage on the checkout flow with custom renderers."

Playwright — Modern E2E framework, dominant at Microsoft, Anthropic, Vercel-aligned shops. Pattern: "Playwright suite covering 14 critical paths with cross-browser parallelization."

Cypress — Older E2E framework, still common. List if shipped; many shops have migrated from Cypress to Playwright since 2023.

MSW (Mock Service Worker) — API-mocking library. Tier-2 senior-FE signal because it shows depth at the test/API boundary.

Visual regression / Chromatic / Percy — Visual-testing keywords for design-system FE roles.

Tier 1 — Performance and Accessibility Keywords

Performance and accessibility are the two keyword classes that distinguish senior FE engineers from mid-level [5][6]. Resumes that name Core Web Vitals and accessibility evidence move through senior screens; resumes that don't, even with strong framework experience, get filtered to mid-level.

Core Web Vitals — The umbrella term. Pattern: "Owned Core Web Vitals across the consumer-product surface; held LCP under 2.5s and INP under 200ms across 6 quarters."

LCP (Largest Contentful Paint) — Loading metric, target under 2.5s [5]. Pattern: "Cut LCP from 4.1s to 1.8s on the marketing homepage by inlining critical CSS and switching to next/image with priority hints."

INP (Interaction to Next Paint) — Replaced FID as a Core Web Vital in March 2024 [5]. Pattern: "Held INP under 200ms across the dashboard by deferring non-critical JS and breaking long tasks." INP is the recency signal — naming it shows post-2024 perf awareness.

CLS (Cumulative Layout Shift) — Visual stability metric. Pattern: "Cut CLS from 0.18 to 0.04 by reserving image dimensions and stabilizing font loading."

Lighthouse / PageSpeed Insights / WebPageTest — Performance tooling. List the tools used for measurement.

Bundle size / code splitting / tree shaking — Bundle-discipline keywords. Pattern: "Cut homepage JS bundle from 280kB to 110kB through route-level code splitting and dependency audits."

ARIA / WCAG 2.2 — Accessibility keywords [6]. Pattern: "Shipped a WCAG 2.2 AA pass across 14 surfaces — keyboard navigation, focus management, ARIA labels, and color-contrast remediation." WCAG 2.2 (released October 2023 per W3C) is the recency signal; older resumes still cite WCAG 2.1.

Semantic HTML / keyboard navigation / focus management — Accessibility-craft keywords.

axe / Pa11y / Lighthouse a11y audit — Accessibility tooling. List if shipped.

Screen reader testing (VoiceOver, NVDA, JAWS) — Senior accessibility signal. List only if you've actually tested with these.

Counter-List — Keywords That Backfire on FE Resumes

The other side of FE keyword optimization: stack choices that read as out-of-date or off-stack at modern tech companies [3][4].

jQuery as primary stack — Listing jQuery as a top-line skill on a 2026 FE resume reads as 2014-era stack. If jQuery experience is real and recent (legacy maintenance work), bury it deep in a "Legacy / Maintenance" line, not in the top skills.

Bootstrap-only — Bootstrap as the only styling system listed reads as bootcamp-tutorial output. Modern tech-company FE work uses Tailwind, CSS Modules, or design-token-driven systems. List Bootstrap only if shipping recent production work that genuinely uses it.

No TypeScript — A senior FE resume in 2026 that lists React but not TypeScript reads as off-stack [3]. If the candidate has only used JavaScript, the resume should signal active TypeScript learning or migration ownership.

No testing tool listed — Senior FE resumes without any testing tool (Vitest, Jest, Playwright, Cypress) read as red-flag because senior FE work includes test ownership [1].

"Familiar with React" / "Worked with React" — Hedging language. Replace with shipped-work framing: "shipped 4 production React applications" or "owned the React 18 → 19 migration on the consumer-product surface."

Long flat skill list (30+ items) — Triggers spam-detection on Greenhouse and Ashby [1][9]. Pick 18–22 items grouped into 4–5 categories.

"Frontend / Backend / Mobile / DevOps" all-of-the-above — On a frontend-engineer-targeted resume, claiming full-stack-plus reads as either junior generalist or unfocused. Lead with FE depth; list backend/mobile experience as supporting context if relevant.

No accessibility mention — In 2026, accessibility silence on a senior FE resume reads as an oversight at companies with public accessibility commitments [6].

Only personal projects, no production URLs — Tutorial-replica clones (Twitter clone, Netflix clone) without a shipped public URL or company context read as bootcamp-stage. Senior FE resumes need production work with measurable outcomes, not portfolio clones.

Worked Examples — FE Keywords in Experience Bullets

Example 1 — Framework + language + perf

Before (C-grade): Built React components for the dashboard.

After (A-grade): Shipped the dashboard refactor in React 18 + TypeScript on Next.js 14 App Router with React Server Components — cut LCP from 3.6s to 1.9s and held INP under 180ms across the most-used flows.

Keywords hit: React 18, TypeScript, Next.js 14, App Router, React Server Components, LCP, INP.

Example 2 — Design system + styling + tooling

Before: Worked on the design system.

After: Owned the design-system primitives layer — built 24 components in React + TypeScript with Radix UI primitives, Tailwind CSS tokens, and Storybook 8 documentation; published as a private package across 5 product surfaces with Turborepo.

Keywords hit: React, TypeScript, Radix UI, Tailwind, Storybook, Turborepo, design system, primitives.

Example 3 — Testing + a11y

Before: Added tests and made the site accessible.

After: Built Playwright E2E coverage on 14 critical paths with cross-browser parallelization and Vitest unit coverage on the design-system primitives; led the WCAG 2.2 AA audit pass — keyboard navigation, focus management, and screen-reader (VoiceOver, NVDA) verification across 11 surfaces.

Keywords hit: Playwright, Vitest, WCAG 2.2, keyboard navigation, focus management, VoiceOver, NVDA.

Example 4 — Build + perf

Before: Improved page load.

After: Cut the marketing-homepage JS bundle from 280kB to 110kB through route-level code splitting, dependency audits, and a Webpack-to-Vite migration; held Lighthouse performance at 95+ across the surface.

Keywords hit: Bundle size, code splitting, Webpack, Vite, Lighthouse.

Example 5 — Migration ownership

Before: Helped with the framework upgrade.

After: Owned the Pages Router → App Router migration on Next.js 13 → 14, including incremental adoption of React Server Components and Server Actions across 3 product surfaces; partnered with the platform team on the shared component-library compatibility layer.

Keywords hit: Next.js 13, Next.js 14, Pages Router, App Router, React Server Components, Server Actions.

Density and Placement Rules for FE

1. Professional Summary: Pack 6–8 Tier-1 FE keywords. Example: "Senior Frontend Engineer with 7 years building consumer-product surfaces in React + TypeScript on Next.js — shipped App Router migration with React Server Components, owned Core Web Vitals (LCP under 2.5s, INP under 200ms), and led the WCAG 2.2 AA audit across 11 surfaces."
2. Skills section: 4–5 categories, 18–22 items total. Recommended grouping: Languages (TypeScript, JavaScript, HTML5, CSS), Frameworks (React, Next.js, plus any second framework shipped), Styling (Tailwind, CSS Modules, Radix, design tokens), Tooling (Vite, Turbopack, Storybook, Turborepo, pnpm, Biome), Testing + Quality (Vitest, Playwright, axe, Lighthouse).
3. Experience bullets: Each recent bullet should pair a framework or stack mention with a quantified outcome (perf number, surface count, test coverage, accessibility result). Aim for 1–2 Tier-1 FE keywords per bullet, embedded naturally.
4. Public shipped URL. The header should link to a portfolio or, ideally, named production surfaces shipped at named companies. Tutorial-clone projects without a real-user URL read junior.

Density rule of thumb for FE: Tier-1 framework keywords (React, Next.js) appear 4–6 times across the resume. Tier-1 language keywords (TypeScript) appear 4–6 times. Performance keywords (Core Web Vitals, LCP, INP) appear 2–4 times with at least one quantified perf bullet. Testing keywords (Vitest, Playwright) appear 2–3 times. Accessibility keywords (WCAG 2.2, ARIA) appear 1–2 times — but at least once on senior+ resumes.

Anti-Patterns That Fail FE Screens

• The "framework agnostic" resume: Lists "JavaScript frameworks" without naming React, Vue, or Svelte. Fails the screen because Workday and Taleo filter on canonical framework strings [8].
• The "HTML/CSS/JavaScript" senior resume: A senior FE resume that lists only the three core languages with no framework, no TypeScript, and no testing tool reads as 2015-era. Add the modern-stack signal or expect the screen to drop the resume.
• The "buzzword-as-implementation" resume: Lists Server Components, Suspense, Concurrent Mode without describing actual shipped work. Senior FE interviewers probe these claims hard, and the disconnect between resume and depth shows fast.
• Tutorial-replica portfolio: Top-three projects are a Twitter clone, a Netflix clone, and a Spotify clone — without shipped URLs or original product context. Reads as bootcamp output; senior FE roles want production work.
• No perf or a11y evidence: Even a strong shipped-work resume that doesn't cite a single Core Web Vital number or accessibility outcome reads as mid-level. Senior FE work includes ownership of both [5][6].
• Stack monoculture: "React, React, React, React" across 6 years with no second framework, no build-tool depth, no testing fluency. Reads as narrow. Add the adjacent-stack signal (Vite, Storybook, Playwright, design tokens) even if React is the primary.

FAQ

Do I need TypeScript on my FE resume in 2026?

For tech-company senior FE roles, effectively yes. Per the 2024 Stack Overflow Developer Survey, TypeScript is among the most-loved languages and dominant in the tech-company FE stack [3]. A senior FE resume that lists React without TypeScript reads as off-stack at Stripe, Vercel, Notion, Linear, Anthropic, and most modern tech companies. The exception: legacy enterprise FE roles that maintain pre-TypeScript codebases, or contractor work where the candidate is still actively learning. In both cases, the resume should signal active TypeScript adoption (a recent migration owned, a side-project shipped in TypeScript, a course completed) so the gap doesn't read as resistance.

How do I handle React Server Components on my resume if I haven't shipped them yet?

Don't claim them. The honest framing is to name the React version and Next.js version you've actually shipped — "React 18 + Next.js 13 Pages Router" is a true claim and reads honest. Claiming Server Components when you haven't shipped them gets caught in the senior FE technical interview because Server Components have specific behaviors (no client hooks, async components, the 'use client' boundary) that show fluency only with real exposure. If the role requires Server Components and you haven't shipped them, signal active learning instead — a side project, a course, a documented migration plan from your current Pages Router work [4].

How many frameworks should I list on a FE resume?

One primary, one or two secondary, and only what you've shipped. Pattern: "React (5+ years primary), Vue (2 years on a previous team), Svelte (one production marketing site)." Listing 6+ frameworks reads as breadth-without-depth and triggers skepticism — senior FE interviews probe framework choices hard, and the candidate who can't articulate trade-offs between their listed frameworks gets caught fast. Pick the ones you can defend in a 30-minute interview.

Should I list CSS frameworks individually or grouped?

Individually, with the specific approach named. "Tailwind CSS, CSS Modules, styled-components, vanilla-extract" reads stronger than "modern CSS approaches." ATS filters at Workday and Taleo are exact-match on the literal framework string [8]. If you've shipped Tailwind, name Tailwind. If you've shipped CSS Modules, name CSS Modules. The cluster of named approaches signals depth at the styling-architecture level.

How do I handle the junior-to-mid FE transition on my resume?

Lead with shipped production work — features that real users used at named companies. Add the depth signal that distinguishes mid from junior: a TypeScript migration owned, a Core Web Vitals improvement quantified, a testing suite added, a design-system primitive shipped, an accessibility audit completed. Mid-level FE recruiters specifically scan for evidence of work beyond "implemented designs" — ownership of part of the stack (perf, a11y, testing, design system, build tooling) is the differentiator [1][2].

Do Frontend Engineers still need a portfolio in 2026?

Yes for most non-FAANG roles, optional at the very top. The portfolio for a FE engineer should show shipped production work — not tutorial clones. Ideal portfolio surface: 3–5 case studies of real shipped features at named companies, with the FE-specific outcomes (perf numbers, accessibility results, test coverage) in the writeup. A portfolio with "shipped Next.js 14 marketing surface, cut LCP from 4.1s to 1.8s" beats a portfolio with 12 generic React projects every time.

Should I list Turborepo or Nx on my resume?

Yes if you've shipped them. Monorepo tooling is a senior-FE signal at companies running design systems across multiple product surfaces. Pattern: "Turborepo monorepo with 4 apps and 6 shared packages; Vite + Vitest + Playwright in the toolchain." If the role description mentions monorepo work and you have shipped it, the literal "Turborepo" or "Nx" keyword is worth its line in the skills section — it's a distinguishing senior signal that mid-level resumes don't carry.

How do I show frontend perf work if I don't have real numbers?

Get the numbers before submitting the resume. Open the production surface in Chrome DevTools, run a Lighthouse audit, run a WebPageTest run, capture LCP / INP / CLS. If the work was a measured improvement you led, document the before-and-after. If you don't have access to the production data and can't get it, lean the resume on the technical work itself ("led the route-level code-splitting refactor on the consumer-product surface") rather than fabricating perf numbers. The editorial bar: cite numbers you can defend in a hiring-manager interview, and skip the metric if the underlying data is shaky [5].

---

References

[1] Greenhouse Software. "Sourcing and Filtering Best Practices — Greenhouse Help Center." https://support.greenhouse.io/hc/en-us/articles/360051506331-Sourcing-best-practices

[2] Ashby HQ. "How Ashby's AI-Powered Sourcing Works." https://www.ashbyhq.com/resources/guides/ai-powered-sourcing

[3] Stack Overflow. "2024 Developer Survey." https://stackoverflow.blog/2024/05/13/2024-developer-survey/

[4] Vercel. "Next.js Documentation — App Router." https://nextjs.org/docs/app

[5] Google / web.dev. "INP: Interaction to Next Paint becomes a Core Web Vital." https://web.dev/blog/inp-cwv-march-12

[6] W3C. "Web Content Accessibility Guidelines (WCAG) 2.2." https://www.w3.org/TR/WCAG22/

[7] levels.fyi. "Software Engineer Salary Data — Vercel, Stripe, Meta." https://www.levels.fyi/companies/vercel/salaries/software-engineer

[8] Workday. "Workday Recruiting — Candidate Search Documentation." https://doc.workday.com/admin-guide/en-us/staffing/recruiting/candidate-experience.html

[9] Ashby HQ. "Recruiting Workflow and Candidate Scoring." https://www.ashbyhq.com/

[10] React. "React 19 Release Notes." https://react.dev/blog/2024/12/05/react-19

[11] MDN Web Docs. "ARIA — Accessibility." https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA

[12] web.dev. "Largest Contentful Paint (LCP)." https://web.dev/articles/lcp