A civil engineering CV gets read by someone who wants one answer quickly: what have you built, and what was your part in it? Most engineers bury that answer under a profile paragraph and a list of duties lifted from their contract. Put the projects first, make your role on each one obvious, and the rest of the document gets much easier to write.
Make the project list the spine of the CV
Hiring managers in this sector think in projects, not job titles. "Graduate Engineer, 2021 to 2024" says very little. "Highway drainage upgrade, 4 km of carriageway, detailed design of attenuation tanks" says a lot. So under each employer, list the projects you worked on and give each one the same four pieces of information:
- Project type. Bridge, retaining wall, foundations for a residential block, water treatment works, station refurbishment. Be specific: "infrastructure" is not a project type.
- Scale or value. Describe it in words, or with figures that only indicate the order of magnitude: "a mid-sized school extension", "a road scheme of roughly 10 million", "three storeys of post-tensioned slab". If the value is confidential, describe the scale physically instead, with spans, lengths, storeys or volumes.
- Your role. This is the line most CVs get wrong. "Involved in the design of" hides you. "Designed the pile caps and checked the temporary works for the basement dig" shows you.
- Stage of work. Feasibility, concept, detailed design, tender, construction, handover. Someone hiring for detailed design wants to see detailed design, and a contractor wants to see you on site during construction.
Keep each project to two or three lines. If you have worked on twenty schemes, pick the six or eight that best match the job in front of you and fold the rest into one line ("plus several minor highway and drainage schemes for local authority clients").
A short example, with an invented firm:
- Northbank Footbridge, Harlow Consulting. Steel truss footbridge, 45 m span over a river. Detailed design of the deck and bearings, Eurocode checks, drawings for tender. Stage: detailed design to tender.
Three lines, and the reader already knows what you can do.
Design office or site: two different CVs
Civil engineering splits roughly into two worlds, and the CV changes with the one you are aiming at.
The design-office CV
Consultancies and in-house design teams care about technical depth. They want the elements you sized, the analyses you ran, the checks you carried out, and the drawings and reports you produced. Put the weight on:
- the structural, geotechnical or hydraulic work you did yourself, element by element
- the software you did it in and the codes you designed to
- calculation packages, reports and design reviews you wrote or checked
The real question for this reader is whether a senior engineer can sign off your calculation without rework.
The site CV
Contractors and site-based client roles care about delivery: programme, quality, coordination and safety. Here the weight goes on:
- the works you supervised and the subcontractors you coordinated
- setting out, temporary works, inspections and test plans
- how you handled technical queries between site and the design team
- programme and cost outcomes, stated plainly
The site reader wants evidence you can keep a job moving. "Ran the pour sequence for a six-level car park, coordinating three subcontractors" does that.
If you have done both, lead with the side that matches the role and mention the other in one sentence near the top.
Site qualifications and your safety record get one line on this CV: name the relevant safety card or supervisor certificate for your country and mention a clean record only if you can stand behind it. The full treatment of site tickets and medicals belongs in a field-based job CV, which is a separate subject.
Software, codes and standards
Software deserves a short dedicated section, but it also belongs inside the project lines, because "AutoCAD" on its own says nothing about what you did with it. Name tools as examples of what you actually use: AutoCAD and Civil 3D for drafting and highway geometry, Revit for BIM coordination, structural analysis packages for frame and finite element work. If you have worked in a BIM environment, say which part you played.
Group the list by purpose instead of pasting twenty product names in a row:
- Drafting and modelling: AutoCAD, Civil 3D, Revit
- Analysis: the structural or geotechnical packages you use regularly
- Project tools: whatever your employer uses for document control or scheduling
Codes and standards get their own line. In Europe the Eurocodes are the obvious reference, and naming the parts you design to (concrete, steel, geotechnics) tells a reader far more than "familiar with relevant standards". If you have worked to a different national code, or to a client's own specifications such as a highway authority's standards, list those too.
Chartership and professional titles
Professional status works differently from one country to the next, so describe yours in the terms of the country you are applying in, and hedge anything you are not certain transfers.
In the UK, chartership through a professional institution is a common goal, and many employers list it as desirable for senior roles. If you are chartered, put the post-nominal letters next to your name and the institution in a short professional section. If you are working towards it, say so and give the stage you have reached. "Working towards chartership" with no detail is easy to write and hard to believe.
Other countries handle this through a protected degree title, membership of a professional body, or a licence tied to signing off drawings. The rules vary and they change, so check the current position for the country you are targeting rather than assuming your title carries over. Registration as a hiring gate is its own topic. Here the point is placement: credentials sit near the top, stated accurately.
The graduate version and the experienced version
A graduate civil engineer has fewer projects and more education, and the CV should be honest about that balance.
For a graduate, education goes high: the degree, the relevant modules, and the final-year or master's project written up like a real project, with the same four elements. Placements and summer internships count as projects. A graduate who writes "designed a 20 m reinforced concrete footbridge to Eurocode 2 as a group project, responsible for the deck and the load combinations" already speaks the language of the job.
For an experienced engineer the order flips. A three-line profile with your discipline, your strongest project type and your professional status. Then experience, project by project. Then education in two lines, with the module list gone. If you have more than fifteen years behind you, compress the early roles to a line each and keep the detail for the last decade. If you now lead teams or run whole schemes, your project lines should start to show it, though a CV aimed squarely at project management roles is a different document with different priorities.
The quickest test of a civil engineering CV: cover the job titles and read only the project lines. If a stranger can tell what you design or build, and at what scale, the CV works.
Putting it together
Start by listing every project you have touched in the last ten years, even roughly. Then, for the role in front of you, keep the ones that match its type of work and its stage, and write each one with the four elements. Postulit can turn your LinkedIn experience into a first draft, but the project lines are the part you should rewrite by hand, because no profile export knows which pile caps you designed.
Before you send it, check that every project shows your own role with an active verb, and that your codes and software appear inside the projects and not only in a list at the bottom. Then read the top third as a stranger would: if your discipline and your best project are visible there, a chief engineer will keep reading.