Generic resume advice does not work for engineers. Your CV is read by an ATS, a non-technical recruiter, and a technical hiring manager — three different filters, three different signals. This page covers what each one actually looks for.
Generic templates push you to add a photo, a hobby section, soft-skill paragraphs, and creative formatting. Each of those actively hurts you. The hiring manager opens GitHub before they finish reading the CV. The ATS chokes on decorative layouts. The recruiter scans for red flags in 6 seconds. None of them care about your favorite books.
Parses to plain text, scores keyword overlap with the JD. Multi-column layouts and decorative headings break parsing. You get filtered before any human sees it.
A non-technical recruiter scans for tenure, gaps, format, and consistency. They cut on visual signal, not technical depth. Clean, scannable beats dense and creative.
A senior engineer opens GitHub, cross-checks LinkedIn, and reads tone for seniority signal. "I worked on" reads junior. "I owned and shipped" reads senior. They decide in under 2 minutes.
Name, role title (matching the JD if honest), email, GitHub, LinkedIn, location/timezone. No photo. Title alignment matters: if the JD is for "Backend Engineer", do not call yourself "Full-Stack Generalist" at the top.
8 to 12 technologies you have used in production. Group them logically (Languages, Frameworks, Infra) only if it helps readability. Mirror the JD vocabulary exactly — Kubernetes, not K8s. Drop "Familiar with…" sections entirely.
Reverse-chronological. Each role: 2-5 bullets, active voice, measurable impact. "I designed and shipped a streaming pipeline that processed 40M events/day" beats "Worked on data ingestion features". Quantify scope, latency, scale, or business outcome.
Critical for juniors and career switchers. 2-3 projects: live, with a README, in a stack relevant to the JD. Each project: one-line description + tech stack + what you built and why. Tutorial clones do not belong here.
Degree, institution, graduation year. For experienced engineers, this section can be 2 lines. For juniors and bootcamp grads, list relevant coursework or capstone. No GPA unless above 3.7 and you graduated under 5 years ago.
The hiring manager reads seniority off your verbs before they reach the bullet’s content. In a shortlist of 10-20 candidates, “almost senior” loses to “clearly senior” every time. If your CV reads a level below the role, you do not get the interview.
Junior signals
Senior signals
Audit yours against a specific role
ATS score, missing keywords with point values, seniority audit, GitHub signal, red-flag detection. Free. No signup.
Run free check →A free engineer CV template fixes your structure. It does not fix your tone, your keyword match, or your seniority signaling. Two CVs with identical templates can read 3 levels apart based purely on phrasing. Optimize the words, not just the layout.
A software engineer CV is read by both an ATS and a technical hiring manager. The ATS scores keyword overlap with the job description; the hiring manager checks GitHub, project quality, and seniority phrasing. Generic resume advice (hobby sections, photo, soft-skill paragraphs) actively hurts you in this context. The bar is technical signal, not personality.
One page until you have 10+ years of relevant experience. Longer reads as inflated. The hiring manager skims — every line should signal. If a bullet does not show ownership, impact, or a relevant technology, cut it.
Yes — and only if your GitHub backs your CV claims. The hiring manager will open it. Tutorial clones, abandoned repos with no README, and zero recent activity hurt you. A link to a clean GitHub with 2-3 real projects beats no link.
Active voice with measurable impact. "I owned and shipped a payment system handling 40k requests/day" beats "Worked on backend payment features". The verb signals ownership level. Numbers signal scope. Both are read in seconds.
8 to 12 you have actually used in production. Listing 40 technologies signals inflation, not range. "Familiar with…" sections are a red flag — drop them. The skills you list should match the JD vocabulary exactly (Kubernetes, not K8s).
For juniors and career switchers — yes, it is often the strongest section on the CV. For seniors with 5+ years of professional experience, projects matter less than impact in past roles. Either way, every project listed should be live, have a README, and show the stack from the JD.
ATS + HR + hiring manager — one pass. Free. No signup.
Check my engineer CV free