A CV lands on a hiring manager’s desk. The candidate has a mechanical engineering degree, three years’ manufacturing experience, SolidWorks, FEA, and hands-on time with production equipment. Looks promising.
Then the experience section says:
Responsible for the design and development of mechanical components, working with cross-functional teams and using CAD and FEA to support projects.
Nothing technically wrong with that sentence. That’s exactly why it survives so often and why it tells the employer almost nothing about the engineer behind it.
What component? What was actually wrong with the original design? What did this person change? Was the FEA used to chase down a failure, compare two options, or just confirm a calculation? Did the final design cut weight, improve reliability, ease manufacturing, or fix something on the line?
That’s where the actual value sits.
Here’s the strange part of engineering CVs: the more technically skilled the candidate becomes, the easier it is to write a CV that sounds impressive while saying almost nothing. The work gets more complex, the language gets more specialised, and somewhere in there the CV starts describing the environment instead of the engineer’s actual contribution.
A good CV reverses that. It takes complicated work and makes the decisions, the contribution, and the result easy to see.
Don’t Open by Listing Everything You Know
Engineers are usually good at collecting evidence degree, software, qualifications, standards, systems, project experience. It’s tempting to keep adding, because every item is technically relevant.
But relevant isn’t the same as important.
An employer hiring a design engineer doesn’t need to know every programme you’ve opened in the last five years. They need to know whether you can do the kind of design work the role actually requires.
So start somewhere else: look at the vacancy, work out what the successful candidate will actually spend their time doing, then pull your strongest matching evidence forward.
If the role involves designing components for manufacture, a line about using CAD to produce a drawing is fine. A line about using CAD to revise a component after manufacturing feedback is far more revealing it shows you understand the relationship between design and production, not just the software.
That’s the level of relevance worth aiming for.
A Software List Doesn’t Prove Ability
“SolidWorks advanced.” “MATLAB intermediate.” These labels are everywhere and mean almost nothing, because people use the same software in wildly different ways. Someone who used MATLAB for one university module and someone who’s built analysis scripts against production data can both write “MATLAB” on the page.
The real evidence sits underneath the label. Compare “Used MATLAB for data analysis” with “Used MATLAB to process test data, identify performance deviations, and compare results against expected operating conditions.” The second version shows what the software was actually doing in your hands.
Same problem shows up with phrases like “experience with commissioning” or “familiar with engineering standards.” If it matters to the vacancy, show how it actually appeared in your work that beats handing yourself a proficiency rating and hoping the reader trusts it.
Your Project Title Isn’t the Achievement Your Engineering Response Is
Graduate CVs have a particularly rough version of this problem. Months on a strong final-year project get reduced to one line: “Final-year project: Design and development of a renewable energy system.” All that work, gone.
The project title was never what made it valuable the decisions inside it were. Maybe you compared several designs against cost and efficiency constraints. Maybe your first prototype exposed a flaw that forced a redesign. Maybe testing contradicted your original assumptions.
Those moments are worth a line. Something like: “Compared three prototype configurations against efficiency and manufacturing constraints before selecting the final design for testing.” Now the employer sees what a project title alone can’t show that you had competing requirements and had to make a real engineering call. That’s evidence of judgement, and judgement is exactly what a CV should be proving.
Be Careful With “Responsible For”
Nothing wrong with the phrase itself sometimes it’s the clearest way to state a real responsibility. The problem is what follows it, or doesn’t.
“Responsible for maintenance of production equipment” tells the reader nothing. If you actually diagnosed recurring faults, prioritised repairs, and helped reshape a preventive maintenance schedule, say that: “Investigated recurring faults on production equipment and used maintenance records to identify patterns, supporting changes to the preventive maintenance schedule.”
Notice it doesn’t pretend you single-handedly transformed the operation it just says what you did. That restraint matters. Engineers work in teams, under supervision, alongside other disciplines, and a CV reads as more credible when it reflects that instead of making every candidate the sole hero of every project.
Be ambitious about your evidence, not your job title.
The Best Numbers Are the Ones You Can Actually Explain
Plenty of advice tells candidates to quantify everything. Taken too far, that backfires a CV gets weaker, not stronger, when every bullet suddenly has a percentage that looks invented purely because someone said achievements need numbers.
If you genuinely cut inspection time by 20%, say so. If you reduced downtime from a known baseline, give the figure. If you worked on a £2m project, that’s useful context. But an achievement doesn’t become meaningless just because it can’t be reduced to a percentage sometimes the strongest result is simply that a design passed testing, a recurring fault got resolved, or a commissioning issue was caught and corrected.
Accuracy beats manufactured precision.
Tailoring Isn’t the Same as Copying the Job Advert
One more mistake worth catching before the CV goes out. A candidate reads “Experience with CAD, FEA, technical documentation, and cross-functional project work” in the advert, and makes sure those exact phrases show up somewhere in their CV. Technically “tailored” except the employer still has to work out whether the candidate has actually done anything meaningful with those skills.
Use the advert as a set of questions instead. Where have I used CAD to solve an actual design problem? Where has analysis helped make or support a real decision? Where have I produced documentation someone else genuinely relied on? Then bring your strongest answers forward.
This matters more in the UK market than people expect, because engineering roles sit inside very different worlds. Experience that makes perfect sense in automotive might need a bit more context for an employer in energy, construction, or aerospace. The skill can transfer. The evidence has to explain how. It’s exactly the kind of gap that experienced engineering CV writers spend most of their time closing not adding more technical language, but making the transfer visible to someone outside your specific sector.
Give the Reader a Reason to Believe You
By the end of an engineering CV, the employer shouldn’t just know what qualifications you hold they should have a real sense of how you actually work. The problems you’ve faced, the tools and judgement you’ve applied, the decisions you contributed to, and what happened afterward.
None of that needs grand claims. The strongest CVs are usually more restrained than the weak ones they don’t tell you the candidate is “exceptionally talented” or “results-driven” every few lines. They just give you enough evidence to reach that conclusion yourself.
That’s the test worth running before you send it. Remove a software name is anything important actually lost? Remove a responsibility does the reader still know what you contributed? Remove a project title is the real engineering problem still clear?
If what’s left still shows what you were trying to solve, what you personally did, why your approach mattered, and what happened next you’re no longer just describing your background. You’re giving an employer a reason to believe you can do the work.
