You have spent three or four years solving engineering problems, writing lab reports, building models and wrestling with one final-year project until it finally behaved. Then you open a blank CV, stare at the cursor and think: “What have I actually got to show for all that?”
If that sounds familiar, you are in good company. Most engineering graduates feel the same way. The issue is rarely a lack of experience. It is that university work does not come with tidy job titles, so its value stays hidden unless you spell it out clearly.
This guide shows you how to do that honestly and in plain English. By the end, you will know what to include, what to leave out and how to explain it.
Start With What You Have Already Done
Picture a mechanical engineering student designing a small gearbox for a module project. They read the brief, build a CAD model, calculate the loads, choose a material and then spot an interference problem that forces a redesign.
That student has not worked as a design engineer, and the CV should never suggest otherwise. But they did design something, hit a technical problem and fixed it. That is real evidence, and employers know how to read it.
The same applies across disciplines: site measurements in civil engineering, circuit testing in electrical, process modelling in chemical, simulations in aerospace. Ask yourself one question: what evidence do I already have of how I think and work?
Why Graduates Struggle With This
Confidence is usually the first hurdle. You see a friend’s CV packed with placements, assume yours looks thin, and pad it with module names and a long list of software. Unfortunately, a long list tends to bury the useful parts.
Take a heat transfer lab. “Completed a heat transfer laboratory” tells the reader almost nothing. “Collected experimental measurements, compared them with theoretical predictions and investigated the differences” tells them plenty.
Some graduates reach this point and start wondering whether Engineering CV writers could help them present technical coursework more clearly. It is a fair thing to wonder, because the real challenge is translating project work into plain, credible language. Whoever does the editing, the principle stays the same: the wording should make genuine evidence easier to see, never invent experience that was not there.
Exposure is another trap. Using MATLAB twice in one module is not the same as using it across several projects. A credible CV draws that line instead of making every skill sound advanced.
Group work needs honesty too. If four of you built a system and you handled the control calculations, say so. A smaller, accurate contribution is far easier to defend in an interview than a grand claim.
A Simple Framework: Claim, Evidence, Relevance
Begin with a claim, such as “I can analyse data”. Then find the evidence: which project actually made you do it? Finally, ask why that matters for the role in front of you.
Compare “Strong analytical skills” with “Processed experimental results in MATLAB, plotted measured against predicted values and investigated possible causes of variation.” The second version shows what analytical skills look like in practice.
Your final-year project is often your richest source. Depending on your discipline, it may show that you can:
- define an engineering problem and research it properly;
- choose a suitable calculation, modelling or testing method;
- work within limits of time, cost, materials or equipment;
- interpret results and explain your decisions in a report.
Tailor It to the Vacancy
A graduate design role and a testing role will not value the same things. Read the job advert closely and note what keeps repeating. If CAD and technical drawings appear three times, dig through your projects for proof of that. If testing dominates, look at your lab work and fault-finding.
Be specific. “Worked on engineering projects” is vague. “Designed and tested a small pumping system in a four-person team, contributing the hydraulic calculations and comparing performance with the predicted flow rate” is something a reader can picture.
Remember that everything on your CV is fair game in an interview. If you list Python, know what you used it for. If you mention your project, know why you chose that method and what limited your results.
Practical Steps You Can Take Today
Do not open a template yet. Go back through your reports, lab write-ups and presentations first, and look for moments where you applied knowledge rather than just received it. Jot down anything that fits:
- final-year or dissertation projects;
- laboratory and testing work;
- CAD, modelling or simulation;
- coding and data analysis;
- placements, society projects and competitions;
- relevant part-time jobs.
Now pick one and ask yourself what you were trying to solve, what you personally did, what went wrong and how you responded. Those answers usually produce better material than any impressive adjective.
Here is how it works for an electrical engineering graduate who built a small embedded system. “Worked on an embedded project” becomes “Developed part of the system, tested the circuit, investigated faults and modified the design after unexpected behaviour.” Same project, far clearer picture.
Keep your education section selective too. List modules that match the vacancy, not every line of your transcript. And do not delete non-engineering jobs. Retail or hospitality will not show finite element analysis, but they do show reliability, communication and teamwork.
Mistakes That Quietly Cost Interviews
Turning coursework into professional experience is the big one. A university project is valuable as a university project. Keeping that distinction clear protects your credibility.
Next comes listing software with no context. “MATLAB, Python, SolidWorks, ANSYS” leaves a recruiter guessing. A short note on what you built or analysed does far more.
Do not write your CV like a transcript, and do not make every project sound flawless. Failed tests and unexpected results are normal. Explaining how you investigated one shows exactly the thinking employers want.
Finally, avoid empty personality claims. “Highly motivated problem solver” is easy to write and hard to prove. A technical fault you tracked down proves it far better.
Bringing It All Together
Experience does not need to come from a payslip to count. Your degree gave you chances to design, test, calculate, programme and explain your reasoning.
The strongest descriptions follow a quiet logic: problem, action, reasoning, result. You faced something that needed solving, chose an approach, made decisions based on evidence and produced an outcome. That is engineering thinking.
Your CV does not need to pretend university was a workplace. It needs to show you already behave like an engineer. Start with one project today, and you will probably find more evidence than you expected.
