How to Screen a Frontend Engineer Resume: Must-Haves, Red Flags and a Scoring Rubric
Frontend CVs list frameworks; the job is products. Screen for evidence of shipping interfaces that real people used, of caring about performance and accessibility, and of working with designers without either side losing.
- Read for evidence before matching keywords: a frontend engineer CV should show what the candidate built, ran, closed or decided, with a result. The must-haves below are the four things the job cannot be done without.
- Must-haves: shipped production interfaces in the framework family the role uses, with the product named; evidence of performance work: load time, bundle size, rendering, with a measurement. Nice-to-haves raise a candidate; they do not rescue one missing a must-have.
- Red flags are patterns, not single lines: portfolio links that are dead or show tutorials, and framework list longer than the list of products shipped.
- Use the five-criterion rubric on the page, weighted so that products shipped counts more than job description match. It is written to be pasted into WadeCV as a role and scored automatically.
- Spend three minutes per CV with the rubric and write one line of evidence per criterion. Screening decisions with evidence attached can be explained to the candidate, to the hiring manager, and to anyone who audits them later.
Must-haves
- Shipped production interfaces in the framework family the role uses, with the product named
- Evidence of performance work: load time, bundle size, rendering, with a measurement
- Accessibility mentioned as something done, not a keyword
- Working relationship with design described: handoff, systems, critique
Nice to have
- Design system ownership or contribution
- Testing practice for UI: behaviour tests, end-to-end journeys
- Server rendering, caching or SEO experience for public-facing products
- TypeScript at scale
Red flags
- Portfolio links that are dead or show tutorials
- Framework list longer than the list of products shipped
- 'Pixel-perfect' with no mention of users or outcomes
- No product a person could have used
The rubric
Score each criterion from what the CV shows; weight 3 counts three times weight 1. In WadeCV, create the role with these criteria and every CV is scored this way automatically.
| Criterion | How to measure it | Weight |
|---|---|---|
| Job description match | Match between the candidate's stack, product type and the role as written | 2 |
| Years of relevant experience | Years shipping production frontends, not total years coding | 2 |
| Products shipped | Named, real interfaces with the candidate's contribution and any outcome | 3 |
| Performance and accessibility | Concrete work on either, with measurements or testing described | 2 |
| Collaboration with design | Evidence of working with designers and a design system | 1 |
How to read the CV
Open the portfolio before the CV. A frontend engineer's work is public in a way most engineering is not, and five minutes with a shipped product tells you more than the bullets do. Then read the CV for what they did on it.
Performance and accessibility are where craft shows and where CVs are usually silent. A candidate who mentions either with a number ('cut initial load from 6 s to 1.8 s', 'made the checkout keyboard-operable') has done work most have not. Weight it.
Be careful with framework matching. React, Vue and Svelte engineers move between them; what does not transfer quickly is product sense and the habit of measuring. Screen for those and teach the framework.
Frequently asked questions
Does a bootcamp background matter?
Not after the first shipped product. Screen bootcamp graduates on what they have built since and on the same rubric; many are excellent, and the rubric will show which.
How do we assess design skills from a CV?
You mostly cannot. Look for evidence of working with designers and for a portfolio you can judge; leave the rest to a critique exercise at interview.
What about candidates who are mostly full-stack?
Score the frontend half of their work on this rubric and note the backend half as a bonus. A full-stack engineer with real frontend depth is a strong hire for a small team.
Related guides
- How to Screen a Backend Engineer Resume: Must-Haves, Red Flags and a Scoring Rubric
- How to Screen a UX Designer Resume: Must-Haves, Red Flags and a Scoring Rubric
- How to Screen a Product Manager Resume: Must-Haves, Red Flags and a Scoring Rubric
- How to Screen a DevOps Engineer Resume: Must-Haves, Red Flags and a Scoring Rubric
Screening frontend engineer CVs this week?
Paste the job description into WadeCV, check the rubric it drafts, and upload the CVs. Each one is read against the rubric and scored with an explanation. Ten screenings are free; there is no subscription.
Screen your first CVs free