How to Write an Engineering Student CV That Gets Interviews (Even With No Work Experience)

Engineering graduate applications have surged 44% in the past two years. More students, more competition, same number of internships and graduate roles. If your CV reads like a list of modules and a part-time job at Tesco, it's going to get seven seconds of attention — and then nothing.

Here's the good news: you have more to show than you think. Your final year project, your group design challenge, your dissertation, that hackathon you entered in second year — all of it is evidence of real engineering capability. You just need to know how to present it.

This guide walks you through every section of an engineering student CV, with particular focus on the projects section — the most underused asset on a student CV. By the end, you'll have a clear formula for turning your degree work into compelling bullet points that make recruiters want to keep reading.

What should an engineering student CV include?

Before getting into the detail, here's the structure that works best for engineering students — especially those without formal work experience:

Personal statement — 3-5 sentences at the top summarising who you are and what you're looking for
Education — your degree, A-levels, and relevant academic achievements
Projects — your most important section if you have limited work experience
Technical skills — languages, tools, software, and frameworks
Work experience — any relevant or transferable roles (more on this below)
Extracurriculars and societies — engineering societies, sports teams, volunteering
References — "Available on request" is fine

Order matters. For engineering students, education and projects should sit near the top. That's where your strongest evidence lives — make it easy for a recruiter to find it.

How to write your engineering student personal statement

Think of your personal statement as a 3-5 sentence pitch. It answers three questions: who are you, what can you offer, and what are you looking for?

For engineering students with limited work experience, lean on your degree discipline, a standout technical skill or project, and your career direction. Keep it specific — vague personal statements are one of the most common CV mistakes.

Weak example:

I am a hardworking and motivated engineering student looking for an opportunity to develop my skills in a professional environment.

This could describe anyone. It tells a recruiter nothing.

Stronger example:

Final year Mechanical Engineering student at the University of Leeds with hands-on experience in CAD design and finite element analysis. My dissertation project involved optimising a heat exchanger design using ANSYS, reducing simulated thermal losses by 18%. I am looking to join a graduate engineering team where I can apply my technical skills to real-world product development.

Same person. Completely different impression. Specific, technical, and direction-focused.

If you're struggling to phrase your experience in recruiter-friendly language, AlignCV's AI suggestions help you turn your notes into polished CV copy — especially useful when you're not sure how to describe technical work.

Education section: make your degree work harder

Most engineering students list their degree title and university, then stop. That's a missed opportunity.

Your education section should include:

Degree title and university (e.g., BEng Civil Engineering, University of Manchester)
Expected graduation date or year of graduation
Degree classification — if it's strong, include it; if you're still studying, include predicted classification
Relevant modules — list 4-6 modules that are directly relevant to the roles you're targeting (e.g., Structural Analysis, Fluid Mechanics, Digital Signal Processing)
Dissertation or final year project — title and a one-line description
Academic awards — prizes, bursaries, high distinction grades

Example:

BEng Mechanical Engineering | University of Sheffield | 2023-2026 (Predicted: 2:1) Relevant modules: Thermodynamics, Finite Element Analysis, Materials Science, Design for Manufacture Final Year Project: Designing a passive cooling system for small-scale electronics — targeting a 15% reduction in thermal runaway events

This gives a recruiter much more to work with than just the degree title.

The projects section: your most powerful asset

This is where engineering students consistently undersell themselves. The projects section is your equivalent of work experience — and for technical roles, it's often more relevant.

How to choose which projects to include

Include projects that show:

Technical skill relevant to the roles you're applying for
Problem-solving and analytical thinking
Teamwork or independent initiative (ideally both)
A tangible outcome — something was built, tested, improved, or achieved

You don't need to include every project you've done. Aim for three to five, prioritising final year project, dissertation, and any personal or extracurricular engineering work.

How to describe a project in three bullet points

This is the formula that separates strong CVs from weak ones:

Action verb + task/technology used + result or impact

Each bullet point should follow this structure. Lead with what you did, include the technology or method involved, and close with what it achieved.

Before (weak):

Took part in a group project to design a bridge structure.

After (strong):

Designed a steel truss bridge spanning 12m using AutoCAD, contributing the load analysis component; structure met all Eurocodes BS EN 1993 requirements within the £10,000 budget constraint.

Same project. The second version tells a recruiter what you did, what tools you used, and that you worked within real engineering standards. That's what gets CVs noticed.

More before/after examples:

Weak	Strong
"Worked on a software project using Python."	"Built a Python script to automate data cleaning for a 50,000-row environmental dataset, reducing processing time from 4 hours to 12 minutes."
"Did a group project on renewable energy."	"Collaborated in a team of four to model a wind farm layout using MATLAB; our design achieved 94% capacity factor in simulated testing, ranked 2nd out of 12 competing teams."
"Completed a CAD design project."	"Produced detailed SolidWorks assembly drawings for a robotic arm prototype; iterated across three design reviews in response to feedback from lab supervisors."

How to quantify academic projects

Students often assume quantification is only possible in commercial settings. It isn't. Here's how to add numbers to academic work:

Percentage improvement: simulated efficiency gains, error reduction, weight savings, time reduction
Scale: dataset size, number of users in a test, project budget, number of components
Rankings: position in a class competition, grade achieved, peer review scores
Team size: "Led a team of five" or "Collaborated across four engineering disciplines"
Deadlines and constraints: "Delivered under a six-week sprint timeline"

If you genuinely can't quantify, describe the scope or the stakes. "Designed for a 150kN load" tells a recruiter more than a vague verb alone.

Solo vs. group projects: how to credit your contribution

Group projects are fine on a CV — but be specific about your role. Recruiters know engineering is collaborative; they want to understand what you contributed.

Use phrases like:

"Led the structural analysis component of a four-person team project..."
"Responsible for PCB circuit design within a larger embedded systems build..."
"Managed integration testing while two teammates handled hardware assembly..."

Avoid "we" language. Even in group work, your CV is about what you did.

Should you include a GitHub link or portfolio?

For software and computer science engineers: yes, absolutely. A GitHub profile with well-documented repositories is a strong credibility signal for technical roles. Include it in your contact details header.

For mechanical, civil, and electrical engineers: a portfolio PDF showing CAD drawings, simulation outputs, or design reports can be useful — especially for design-heavy roles. Link to it if you have one.

If you're unsure whether your CV is linking the right things in the right way, browse AlignCV's free CV templates — the layouts are designed to give the right sections the right prominence.

Technical skills section: specific beats generic

Your technical skills section should be a scannable, credible list of the tools and technologies you actually know how to use.

Organise by category for easy reading:

Example for a software/computer science engineering student:

Programming languages: Python, Java, C++, MATLAB Frameworks and libraries: NumPy, Pandas, TensorFlow (basic) Tools: Git, Linux, Docker (basic), VS Code Concepts: Data structures, object-oriented programming, machine learning fundamentals

Example for a mechanical engineering student:

CAD and design: SolidWorks, AutoCAD, CATIA (basic) Analysis and simulation: ANSYS, MATLAB, Simulink Manufacturing: GD&T, injection moulding principles, CNC machining (supervised) Standards: Eurocodes, BS EN standards, ISO 9001 awareness

A few important rules for this section:

Only include skills you could discuss confidently in an interview
Add "(basic)" or "(familiar)" next to skills you've only touched
Don't pad with tools everyone uses (Word, PowerPoint) unless the role specifically asks
Tie skills to evidence in your projects section — "Python (3 years, used in final year data analysis project)"

Work experience for engineering students with none

If you have an internship or placement year, great — that goes first in your experience section with the same action-verb bullet point formula.

If you don't, here's what counts:

Lab technician roles or demonstrator positions at university
Part-time jobs, even in retail or hospitality — they show reliability, communication, and working under pressure
Volunteering, particularly any technical volunteering (building/fixing things, teaching coding, STEM outreach)
Engineering society roles — committee member, event organiser, competition participant (Formula Student, IMechE design challenges, IET events)
Open-source contributions or personal side projects
Hackathons — even if you didn't win, participation shows initiative

Take Priya, a final year Computer Science student who hadn't done a placement year. She almost left her experience section blank. Instead, she listed her university's coding society committee role ("Organised and ran six Python workshops for 120+ undergraduates"), her part-time barista job with a bullet point about managing stock orders, and a GitHub repo she'd built for a university module. Her section looked full, relevant, and real — because it was.

For more strategies on filling your CV when your work history is thin, our guide on writing a CV with no work experience covers this in more detail.

ATS tips for engineering CVs

Many larger engineering firms and graduate schemes use an Applicant Tracking System (ATS) to screen CVs before a human reads them. ATS software scans for keywords, formatting, and structure — and automatically filters out CVs that don't match.

For engineering students, the key ATS principles are:

Use keywords from the job description. If the job description says "SolidWorks" and your CV says "3D modelling software", an ATS may not match them. Use the same terminology the employer uses.

Avoid tables and columns. ATS parsers often mangle text inside tables or two-column layouts. Use a clean, single-column CV structure.

Spell out acronyms on first use. Write "Finite Element Analysis (FEA)" rather than just "FEA", in case the ATS searches for the full term.

Use standard section headings. "Technical Skills", "Work Experience", "Education" — not creative alternatives like 'My Toolkit' that an ATS won't recognise.

If you want to know how your CV actually scores before you apply, AlignCV's ATS score checker (Pro plan) analyses your CV against ATS criteria and flags any issues — useful if you're applying to large companies with volume application processes.

FAQ

What should an engineering student put on their CV if they have no work experience?

Lead with your education and projects. Your final year project, group design assignments, dissertation, and any extracurricular engineering work (hackathons, societies, competitions) are all relevant. Use the action verb formula to describe what you built, analysed, or achieved. Fill any remaining gaps with non-engineering experience — part-time jobs, volunteering, and society roles all demonstrate transferable skills.

How long should an engineering student CV be?

One page for most students; two pages if you have a placement year or substantial project portfolio. If in doubt, one tight page beats two padded ones. Recruiters prefer concise CVs that are easy to scan quickly.

Should I include all my university projects?

No. Select three to five projects that are most relevant to the roles you're targeting. Prioritise your final year project and dissertation, then choose projects that showcase the specific skills (tools, techniques, discipline knowledge) the employer is looking for.

How do I describe a group project on my CV?

Be specific about your individual contribution. Use phrases like "Led the structural analysis component", "Designed the PCB layout", or "Wrote and tested the simulation model". Avoid "we" language — your CV is about what you did, even within a team.

Is GitHub important on an engineering CV?

For software engineering, computer science, and data-focused roles, yes. A well-documented GitHub profile with clear README files can be as compelling as a traditional project section. For mechanical, civil, and electrical engineering, a linked portfolio PDF showing design work or simulation outputs can serve a similar purpose.

Conclusion

The biggest mistake engineering students make is treating their degree work as background — something that happened before their career started. It isn't. It's evidence. Your projects, your dissertation, your technical skills, and your academic achievements are proof that you can think like an engineer. You just need to present that evidence in a way recruiters can act on.

Here's a quick recap:

Lead with your projects — they're your most powerful section if you lack formal experience
Use the formula: action verb + technology used + result or impact
Quantify wherever you can — percentages, team sizes, rankings, simulated outcomes
Be specific about your contribution in group projects
Tailor your keywords to each job description to pass ATS screening

Your CV doesn't need years of work experience behind it. It needs clarity, specificity, and the right structure.

Ready to build it? Build your CV free with AlignCV — all templates included, no card required.

Engineering Student CV: How to Use Projects to Get Hired