Engineering CVs tend to fail in a specific way: they list duties and a long column of software, but hide the projects the engineer actually delivered. A hiring manager or technical lead is scanning for scope, standards and outcomes. If your CV tells them what tools you can open but not what you built, to what code, at what budget, it reads as junior even when you are not. This guide covers mechanical, civil and electrical CVs together, because the underlying fix is the same: put delivered projects first, and prove technical competence with evidence.
What employers want
Engineering employers are hiring for a few things at once: technical competence in the discipline, delivery to the relevant standards and codes, a genuine grasp of safety, and a track record of projects at real scope and budget. They want to see that you can take a brief and deliver something that works, is compliant, and is safe. A CV that answers 'what have they delivered, and to what standard?' is far stronger than one that describes a role in the abstract.
Lead with delivered projects
Structure your experience around the projects you delivered, not just the job titles you held. For each significant project, make five things clear: the discipline and type of work, the scope, the value or budget, your specific role, and the outcome. 'Contributed to a design team' tells a reader almost nothing. 'Led the structural design for a £6m school building, from concept to construction issue' tells them your level, your responsibility and the scale you operate at. Real projects are the strongest evidence an engineering CV can carry.
Chartership and professional status
Professional registration matters in engineering, so make yours easy to find. If you are registered as IEng or CEng through an institution such as IMechE, ICE or the IET, state it clearly near the top, usually in the profile or a short credentials line, and again in your qualifications section. If you are working towards it, say so honestly: 'working towards CEng (IMechE)' or 'IEng, progressing to CEng'. This is a claim that is easy to verify, so never imply a status you do not hold. Being straight about the stage you are at costs you nothing and protects your credibility.
Standards, codes and compliance
Referencing the standards and regulatory context you have worked to signals real competence rather than generic experience. A civil or structural engineer might cite the Eurocodes and CDM regulations; a mechanical engineer might reference relevant BS or ISO standards and Building Regulations such as Part L; an electrical engineer might point to BS 7671, IEC standards or CDM duties on a project. Name the standards that are genuinely relevant to the roles you are targeting and that you have actually applied. This tells a technical reader you understand the framework the work has to sit within.
Technical skills and software
Software matters, but it belongs in a clear, grouped skills section, not scattered through every bullet or padded out to look impressive. Group tools sensibly, for example CAD and modelling (SolidWorks, AutoCAD, Revit), analysis (MATLAB, finite element tools), and any discipline-specific packages. Then match the list to the advert: if a role asks for Revit, make sure your genuine Revit experience is visible and, ideally, evidenced by a project where you used it. A skills list on its own proves familiarity; a skill tied to a delivered project proves capability.
Quantify what you delivered
Numbers turn engineering claims into evidence. Quantify efficiency gains, cost savings, tolerances held, throughput improved, or programme met. Where exact figures are commercially confidential, use percentages or ranges rather than dropping the point altogether. 'Reduced material cost' is weaker than 'reduced material cost by around 12% through a design change'. The scale and result are what let a reader judge your level, so include them wherever you honestly can.
Discipline-specific tailoring
Mechanical, civil and electrical CVs emphasise different evidence. A mechanical CV might foreground design, thermal or fluid performance and manufacturing tolerances; a civil CV might lead with structures, infrastructure scope and construction-phase delivery; an electrical CV might stress power, controls, compliance to wiring regulations and system integration. There is no single template that fits all three. Read the advert, work out which evidence it values most, and bring that forward. Tailoring to the specific discipline and role always beats a generic 'engineer' CV.
A worked example
The figures below are illustrative, to show the shape of a strong bullet rather than any real project. Before: 'Worked on HVAC design.' After: 'Led HVAC design for a £4m commercial fit-out to Part L, cutting projected energy use by 18%.' The rewrite names the discipline, the scope and value, the standard worked to, your role, and the outcome. That is the difference between a duty and a delivered result.
Common mistakes to avoid
- Listing duties and software while hiding the projects actually delivered
- Leaving out scope, budget or your specific role on each project
- Never naming the standards or codes the work was delivered to
- Overstating chartership or professional status
- A generic 'engineer' CV that ignores the discipline in the advert
- No numbers at all, even where percentages or ranges could be shared safely
If you want a second opinion on how your engineering experience reads, we offer a free, human review and a range of CV writing packages for mid-career professionals.
Common questions
What should an engineering CV focus on?
Delivered projects at real scope and budget, worked to the relevant standards and codes, with your specific role and the outcome made clear. Employers read for technical competence and safe delivery, not a list of duties or a wall of software names.
Should I list chartership if I'm still working towards it?
Yes, but be honest about the stage. Write 'working towards CEng (IMechE)' or 'IEng, progressing to CEng' rather than implying you already hold it. Overstating professional status is easy to check and undermines the whole CV.
How long should an engineering CV be?
Two pages is standard for most mid-career engineers, occasionally three where a long project list adds real evidence. Lead with your strongest recent projects and keep older or less relevant roles brief.