Civil Engineer CV Example
A civil engineering CV is usually read in two passes: a keyword scan — sometimes by software, sometimes by a busy technical lead — followed by a closer read from a senior engineer who wants proof you can actually deliver. Both want different things from the same page. The scan looks for the right discipline, the right software, and the standards you've worked to; the engineer looks for the scale of the projects you've delivered, how much you owned, and outcomes measured in time, cost, or risk reduced. This example shows how to structure a civil engineering CV, how to present your design software and technical standards, how to write project-focused experience bullets that quantify impact, and how to signal your chartership or professional-registration status. Everything is editable in the Cvida builder — use it as a starting point and tailor it to your discipline, whether that's structural, geotechnical, transport, water, or site and construction management.
Why a civil engineering CV is different
Civil engineering hiring has its own conventions, and they explain every choice below. A technical reviewer is screening for signals a generic CV never shows:
- Discipline specificity matters: 'civil engineer' is broad — structural, geotechnical, transport, water, and construction each have different software, standards, and expectations the reviewer is matching against
- Software is a hard filter: AutoCAD, Civil 3D, Revit, SAP2000, ETABS, or STAAD aren't optional keywords — a reviewer scans for the exact tools the role uses
- Standards and codes are evidence: naming the Eurocodes, British Standards, ACI, or local design codes you've worked to proves real project exposure, not just theory
- Projects carry the weight: the scale, value, and type of projects you've delivered tell a senior engineer more than your job title ever will
- Chartership signals trajectory: progress toward professional registration (such as CEng, PE, or your country's equivalent) is a major differentiator, even while still in progress
Treat your CV as a technical document. The same precision you'd put into a design calculation or a method statement applies here: name the right discipline, the right tools, and the right standards, and prove the work with measurable project outcomes.
The fundamentals of CV structure and length this example builds onThe structure that works for an engineering CV
Put the technical signal where a reviewer looks first. Most civil engineering CVs work best in this order:
- Header: name, your discipline title (for example 'Structural Engineer'), location, phone, email, LinkedIn, and your chartership status if relevant
- Summary (3-4 lines): years of experience, discipline, the type and scale of projects, core software, and registration status
- Technical skills: design software, analysis tools, standards and codes, and methods — grouped and scannable
- Experience: roles in reverse-chronological order, each focused on the projects you delivered and your specific role on them
- Key projects: a short highlighted section for 2-4 flagship projects with value, scope, and your contribution
- Education: degree(s), university, and year — plus any accreditation, since an accredited MEng or BEng matters for chartership
- Professional: memberships (such as ICE, ASCE, or your local engineering body), chartership progress, and relevant certifications
Keep it to two pages — engineering is one of the fields where a second page is genuinely expected once you have project history, because the project detail is the substance reviewers want. Recent graduates should still aim for a tight single page.
How long a CV should be, and when a second page is justifiedThe summary: discipline, scale, and chartership status
Three or four lines at the top — the most-read part after your name. For a civil engineer it should answer: what discipline, what scale of projects, what tools, and where you are on chartership:
- Line 1 — experience and discipline: 'Chartered structural engineer with 8 years' experience in commercial and residential building design.'
- Line 2 — project scale and type: 'Delivered structural designs for projects up to £40M, from concept through to construction support.'
- Line 3 — software and standards: 'Proficient in Revit, ETABS, and Tekla; design to Eurocodes and British Standards.'
- Line 4 (optional) — chartership and target: 'Chartered engineer (CEng MICE) seeking a senior design role with a path to technical leadership.'
- Cut the empty adjectives: 'hardworking, detail-oriented team player' adds nothing — the discipline, the scale, and the standards do the persuading
A summary that names a real discipline, a real project scale, and real standards beats an adjective-heavy one every time. If you can't yet name a chartership status, lead with the project scale and software instead — those are the next strongest signals.
How to write a CV summary that works, with examplesThe skills section: software, standards, and technical depth
Group your technical skills by type so a reviewer scans in seconds, and order each group by genuine depth — most fluent first:
- Design and modelling software: AutoCAD, Civil 3D, Revit, Tekla Structures, MicroStation — name the ones you actually use
- Analysis software: SAP2000, ETABS, STAAD.Pro, PLAXIS, HEC-RAS — match these to your discipline (structural, geotechnical, water)
- Standards and codes: Eurocodes, British Standards, ACI, AASHTO, or your local design codes — proof of real project work
- Technical methods: structural analysis, foundation design, drainage design, BIM coordination, temporary works, site supervision
- What to leave off: software you touched once in a university module, and generic office tools — they only dilute the real signals
Be honest about depth: if you list ETABS, expect a technical question about it. A short, accurate, discipline-matched skills section beats a long generic one, because a reviewer can immediately picture you doing the actual work.
How to choose and present the best skills for your CVExperience bullets: projects, budgets, and measurable outcomes
The strongest civil engineering bullets are project-centred and quantified: what you designed or built, at what scale, and the outcome. Compare these:
- Weak: 'Responsible for structural design work on various projects' — no project, no scale, no software, no outcome
- Strong: 'Led the structural design of a 12-storey reinforced-concrete office building (£28M), from concept to construction, using ETABS and Revit to Eurocode 2'
- Strong: 'Optimised a bridge foundation design that cut concrete volume by 18%, saving an estimated £120k while meeting all geotechnical requirements'
- Strong: 'Coordinated BIM models across 4 disciplines, resolving 60+ clashes before construction and avoiding costly site rework'
- Pattern to apply: action verb + project + scale or value + software/standard + outcome (time saved, cost reduced, risk mitigated, clashes resolved)
The numbers don't have to be enormous — they have to be real and specific. 'Designed drainage for a 2-hectare residential site to meet local sustainable-drainage requirements' is a strong bullet, because it names the scope, the scale, and the standard a reviewer recognises.
How to quantify your achievements on a CV, with examplesThe key projects section: the heart of a civil engineering CV
A dedicated projects section is where civil engineering CVs win or lose. It lets a reviewer see your range and the scale you operate at without digging through job descriptions:
- Pick 2-4 flagship projects, each with: name or type, value, your role, the software and standards used, and a one-line outcome
- Show the full lifecycle if you have it: concept, detailed design, tender, and construction support — reviewers want to know which stages you've actually worked
- Name your specific contribution: 'designed the lateral stability system' is far stronger than 'worked on the project as part of a team'
- Cover a range of types if you can: showing both building and infrastructure, or both design and site work, signals versatility
- For graduates: a university capstone, a final-year design project, or an industrial-placement project fills this section credibly
Make the projects concrete and varied. A reviewer who can see three real, well-described projects with your specific role and the standards you applied is already halfway to inviting you in — the project detail is the evidence your job titles can't provide.
Strong action verbs to start your CV bullet pointsATS and formatting: getting past the first filter
Large consultancies and contractors often run CVs through software before an engineer sees them, and engineering parsing is unusually literal about technical terms:
- Mirror the job advert's exact terms: if it says 'Civil 3D' and 'Eurocodes', use those exact words where they're true for you
- Spell out abbreviations once: 'Building Information Modelling (BIM)', 'Sustainable Drainage Systems (SuDS)' — that covers both keyword variants
- Keep the format simple: standard fonts, a single or clean two-column layout, and no text inside images — parsers mangle anything visually clever
- Name software and standards in plain text, not only inside a graphic skills chart that a parser cannot read
- Save as PDF unless the advert asks for Word — the layout and your project tables survive the round-trip more reliably
The simple test: can your CV be read top to bottom in a plain text editor and still make sense? If yes, the parser can read it too. Clean formatting plus the advert's own technical keywords gets you past the filter and in front of the engineer.
The full ATS playbook for parsing-safe CV formattingCommon mistakes on a civil engineering CV
Even strong engineers lose interviews to fixable CV mistakes. Avoid these and you immediately stand out:
- Listing duties instead of projects: 'responsible for designs' tells a reviewer nothing — lead with the projects you delivered and your role on them
- Hiding the software and standards: if a reviewer has to hunt for whether you know Revit or the Eurocodes, the CV has already failed its main job
- No quantification: engineering is a numbers discipline — a CV with no project values, scales, or measurable outcomes reads as junior
- Vague discipline: a CV that doesn't make clear whether you're structural, geotechnical, or transport forces the reviewer to guess, and they usually won't
- One generic CV for every role: tailor the summary, skills, and highlighted projects to each advert's discipline and software — it sharply lifts your response rate
Run the reviewer's test: in 30 seconds, can a senior engineer see your discipline, your software, the standards you work to, and the scale of projects you've delivered? If yes, this CV will earn the interview. If not, the fixes are almost always the same — lead with projects, surface the software and standards, and quantify everything.
The most common CV mistakes and how to avoid them