Engineering CVs tend to fail for the opposite reason most CVs fail. It's rarely a lack of substance — it's too much of it, presented in a way that only makes sense to someone who already understands the discipline. The first person to read your CV is often a recruiter or HR screener, not an engineer, and if they can't follow it, a technically brilliant candidate never reaches the technical interview.
Lead with what you built, not what your job title was
"Structural Engineer at XYZ Ltd" tells a screener almost nothing on its own. What moves the needle is specificity: the type of structure, the scale, the standards you worked to, and what you were personally responsible for. Precision reads as competence in engineering more than in almost any other field — vague language does the opposite.
- Name the project type and scale (residential, infrastructure, industrial, budget/size)
- Reference the standards or codes you worked to where relevant (British Standards, Eurocodes, ISO)
- Be explicit about your role versus the wider team's — did you design it, review it, deliver it, sign it off?
Quantify outcomes, even on long projects
Engineering work often spans months or years, which makes it tempting to describe projects rather than your contribution. Pull your specific piece out and quantify it — cost saved, time reduced, defects caught, capacity increased, a compliance issue resolved. A reviewer can't infer your individual impact from a project description alone; you have to state it.
List your software and tools with intent
CAD packages, simulation software, project management tools — list what's genuinely relevant to the roles you want, grouped clearly, rather than everything you've ever opened. If a tool is central to the job description you're applying to and you know it, make sure it's visible near the top of the CV, not the bottom.
Chartered status and professional registration go near the top
CEng, IEng, or membership of the relevant institution (ICE, IMechE, IET, and so on) is often a genuine filter criterion, not just a nice-to-have. If you're chartered, say so clearly under your name or in your profile. If you're working towards it, state that too — many employers value the trajectory almost as much as the credential itself.
Write for two readers at once
Assume your CV will be read first by someone without technical training and later by someone who could interrogate every line. Lead with plain-language outcomes, then back them up with technical detail immediately after — both readers get what they need.
Format still matters
Even the strongest technical content gets lost in a CV that's hard to scan. The structural basics — reverse-chronological order, clean formatting, no tables that break ATS parsing — are covered in our guide to UK CV format, and they apply just as much to engineering CVs as any other.
Once you're through to interview, competency-based questions are common in engineering hiring — our guide to the STAR method is worth preparing with in advance.
Frequently asked questions
Should I mention chartered status or working towards it?
Yes, and prominently. Whether you're already chartered (CEng, IEng) or actively working through it, this belongs near the top of your CV, not buried in a qualifications list at the bottom — it's often one of the first things a hiring manager or panel checks for.
How technical should my CV language be?
Technical enough to be credible to an engineering reviewer, but written so a recruiter or HR screener without a technical background can still follow what you did and why it mattered. Lead each point with the outcome, then support it with the technical detail.
Do I need to list every piece of software or tool I know?
No — list what's relevant to the roles you're targeting and what you can genuinely use with confidence. A tools section stuffed with software you used once on a training course dilutes the ones that actually matter to the job.
How do I show impact on projects that took years to complete?
Break the project into what you specifically owned and delivered, and quantify that piece rather than the whole multi-year programme. "Led structural design for a £12m phase of a 4-year infrastructure project" is more credible and more useful than claiming the whole project as a solo achievement.
Get an engineering CV that reads well both ways
We build CVs that hold up to a technical reviewer and land with a recruiter screening the first pass.
Get My CV Written