Civil engineer CV example and writing guide
Updated 29 July 2026
A convincing civil engineer CV connects sound technical work with clear project outcomes. This guide shows how to structure that evidence, write a focused personal statement and turn routine responsibilities into specific, credible achievements.
Civil Engineer CV examples
Graduate Civil Engineer
JuniorGraduate Civil Engineer with experience supporting drainage and highways projects through design checks, site inspections, engineering calculations and progress reporting. Brings a sound grounding in civil engineering principles, building information modelling and safe, sustainable design, with a careful approach to quality and project constraints.
Why it works: This graduate civil engineer CV pairs a relevant degree and placement experience with measured evidence from design checks, site inspections, reporting and project coordination.
Civil Engineer
Mid-levelCivil Engineer with six years of experience supporting transport, drainage and public-realm projects through design, construction and handover. Combines engineering modelling, site inspection and risk management with clear communication across multidisciplinary teams, and has delivered packages valued at up to £8.4 million.
Why it works: This civil engineer CV sample connects design, site inspection and project coordination to credible measures of cost, programme, quality and environmental performance.
Senior Civil Engineer
SeniorSenior civil engineer with 13 years of experience leading infrastructure design and construction work across transport, drainage and public-realm programmes. Combines independent engineering judgement with project, commercial and risk management, translating technical constraints into safe, buildable solutions. Experienced in directing multidisciplinary teams, reviewing designs and site activity, managing client relationships and delivering portfolios with a combined value of up to £48 million.
Why it works: Shows clear progression into technical and project leadership, with defensible examples of project scale, risk control, design assurance and measurable delivery outcomes.
How to write a civil engineer CV
Use a clean, reverse-chronological layout with familiar headings and straightforward formatting. Avoid logos, decorative boxes and complicated columns, which can make a CV harder to read and may not work well with applicant tracking systems. Two pages is a sensible target for most applicants, although a graduate civil engineer CV may fit on one page when experience is limited.
Build the right order
Put your name and contact details first, followed by your personal statement, skills, employment history and education. Add relevant projects or other information only when they strengthen your application. Experienced engineers should give employment more space; graduates can bring education and project work forward.
| Section | What to include | What to leave out |
|---|---|---|
| Personal statement | Engineering experience, project contributions, selected successes and direction | Generic claims that could describe any applicant |
| Employment | Job title, employer, dates, scope and measured results | A list copied from the job description |
| Skills | Hard skills, software competence and useful working behaviours reflected in the vacancy | Every tool or technique you have encountered |
| Education | Relevant qualifications, institution and dates | Unrelated modules or school detail once you have substantial experience |
| Extras | Relevant placements, languages, volunteering or technical projects | Hobbies that add no useful evidence |
Keep the personal statement to a compact paragraph. Set out your level, the kind of work you have contributed to and one or two outcomes that matter to the target employer. A civil engineer personal statement works best when it sounds like a precise introduction rather than a collection of adjectives.
List employment from the newest role backwards. Tailor each entry to the vacancy by selecting relevant engineering contributions and achievements. Give enough context to make the result meaningful: the project stage, your responsibility, the scale involved and what changed because of your work.
Use a dedicated skills section, but treat it as a signpost rather than proof. Match relevant hard skills, software competence and soft skills to the job description, then support the important ones in your employment or project bullets. Project management can be particularly useful evidence where the role covers resources, programme, quality or risk; see this project engineer CV guide if that is your focus.
Present education in reverse-chronological order, beginning with the most recent suitable qualification. Include its title, institution and dates. Graduates can add selected modules, projects or an optional industry placement; experienced applicants can keep this section shorter.
Extras earn their place when they answer a likely employer question. A relevant project can show technical judgement, while a placement can demonstrate exposure to engineering work. Keep each addition brief and factual.
Personal statement examples
Civil engineer with five years of experience contributing to infrastructure design, site inspections and construction-stage coordination. Managed technical inputs across projects valued at up to £4.2 million, resolved 18 design queries before they affected the programme and helped reduce material waste by 9%. Now seeking a role that combines design judgement, project delivery and close work with multidisciplinary teams.
Hard-working civil engineer looking for a new opportunity with a good company. I have excellent communication and problem-solving skills, work well alone or in a team and can handle many different engineering duties. I am keen to learn, grow and take the next step in my career.
Writing your experience
Strong experience bullets explain what you did, the setting in which you did it and the result. Start with an action verb, add enough scope to make the work understandable, then finish with a defensible measure. Useful measures may include project value, quantities reviewed, time recovered, defects closed, costs avoided, waste reduced or progress against programme. Never invent a figure or estimate one for effect.
A practical pattern is: action + engineering task or scope + method + result. For example, "Reviewed drainage design packages for a £3.8 million development, resolving 14 coordination issues before construction and avoiding six programme delays." The value comes from the connection between the review and the outcome, not from the number alone.
| Before | After |
|---|---|
| Responsible for site inspections | Completed 32 site inspections across two active work fronts, closing 91% of recorded issues within the agreed seven-day period |
| Helped with structural designs | Checked 24 structural design drawings against project specifications, identifying eight discrepancies before issue for construction |
| Worked with contractors and consultants | Coordinated weekly technical reviews with five contractor and consultancy disciplines, cutting unresolved design queries from 21 to 7 in six weeks |
These rewritten bullets are illustrative. Replace their figures with your own records and be ready to explain how each result was calculated.
Choose verbs that describe your actual authority. "Designed", "evaluated", "inspected", "modelled", "checked", "coordinated", "planned", "managed", "resolved" and "reported" are direct and specific. A graduate who supported a task should say "assisted", "prepared" or "contributed" rather than implying sole ownership. A senior engineer can use "led", "approved" or "directed" only where those words accurately describe the role.
Civil engineering work often sits inside several constraints, so show how you balanced them. A useful bullet might connect a design revision with cost, time, resources, quality or risk. Where relevant to your employment, include communication with engineers, technicians, specialist contractors, clients, suppliers or other project stakeholders. Name the purpose and outcome of that contact rather than writing "excellent stakeholder management".
Site and design evidence also needs precision. State whether you commissioned, carried out or reviewed an inspection; whether you produced, checked or evaluated a design; and which performance criterion or specification guided the work. This wording reveals your contribution and avoids overstating responsibility.
Key skills & ATS keywords
Hard skills
Soft skills
ATS keywords
Education & certifications
List education from the most recent suitable qualification backwards. For each entry, give the qualification name and level, institution or awarding body, location where it helps identify the institution, and attendance or graduation dates. Keep the format consistent so a reader can scan it quickly.
A Bachelor of Engineering in Civil Engineering is a relevant degree example for this section. Civil engineering study may cover structures, materials, geotechnics, hydraulics and transportation, alongside scientific, technical, environmental, economic and managerial aspects of project work. If these areas support the vacancy, graduates can name a small selection of relevant modules rather than reproducing the full course list.
You can also mention academic experience with CAD, BIM or FEM software when it is relevant and you can describe what you produced. A final project involving environmental impact, responsible construction or climate resilience may provide useful evidence, particularly when professional experience is still limited. State the question, your method and the result in one or two lines.
An industry placement is an optional route to experience during civil engineering study. Put it under employment or a clearly labelled placement section when it involved substantial workplace responsibilities; otherwise, include a short note beneath the degree. Describe your contribution without presenting supervised work as independent authority.
Do not add an unsupported string of credentials. Include specialist certifications or licences only when they are relevant to the role and genuinely held. Where applicable, record an expiry or renewal date so the entry is unambiguous. If no named credential is supported, concise education and well-evidenced project experience are better than a padded certification section.
Common mistakes to avoid
Using a dense civil engineer CV layout packed with boxes, logos and complicated tables.
Choose a clear, readable structure with standard headings and straightforward formatting. This makes the document easier to scan and avoids features that may not work well with applicant tracking systems.
Listing duties such as "helped with site inspections" without showing what changed because of the work.
Turn duties into evidence. State what you inspected or checked, the scale involved and a defensible result, such as fewer outstanding defects, faster approval or delivery against a deadline.
Sending the same skills list for every civil engineering vacancy.
Read the job description and select the hard skills, software competencies and soft skills that match the advertised work. Keep only terms that reflect your genuine experience.
Writing a personal statement that says only that you are hardworking and passionate about engineering.
Connect your engineering experience, project contributions, strongest result and next career step to the employer's needs. A graduate can use a placement, design project or other relevant academic evidence.
Allowing software names to replace engineering evidence.
Pair each relevant digital skill with its use. For example, explain whether you applied modelling, BIM, CAD, FEM or GIS to design, evaluate, test or manage infrastructure.
Describing project work without its constraints or stakeholders.
Show how you worked within time, cost, resource, quality or technical limits. Where relevant to the employer, identify collaboration with engineers, technicians, contractors, clients or suppliers.
Junior vs senior: what changes
| Aspect | Junior | Senior |
|---|---|---|
| Personal statement | Lead with civil engineering study, a placement or a substantial project, then name the type of technical contribution you can already make. | Lead with project scale, leadership scope, engineering judgement and a small number of defensible delivery outcomes. |
| Technical evidence | Use coursework, design projects, placements and supervised site work to show modelling, design, inspection or analysis skills. | Show responsibility for evaluating technical solutions, checking design or construction activity and resolving complex delivery issues. |
| Project management | Describe ownership of a defined task, package or deadline and explain how you tracked accuracy and progress. | Describe planning and management of projects, teams, technical input, resources, quality systems and risk. |
| Stakeholder work | Give an example of clear technical communication within a project team or during a placement. | Show coordination across multidisciplinary teams and, where the role involves them, clients, contractors, suppliers and other external parties. |
| Results and metrics | Use modest, defensible measures such as drawing quantities, survey coverage, deadlines met, defects recorded or calculation accuracy. | Use broader measures such as project value, programme performance, cost control, team size, risk reduction or quality improvement, provided every figure can be verified. |
| Skills section | Prioritise relevant engineering principles, modelling methods and software used in study, projects or placements. | Prioritise technical leadership, independent judgement, project management, commercial awareness, risk management and the specialist tools used in recent work. |
Frequently asked questions
Aim for a concise CV that gives enough space to prove relevant engineering work without repeating duties. A graduate civil engineer CV may fit comfortably on one or two pages, while an experienced candidate will often need two.
Use relevant university projects, an optional industry placement, site exposure, volunteering and transferable work. Describe the engineering problem, your contribution, the methods or software used and a result you can defend.
No. Under British CV conventions, leave out your photo and date of birth; use the space for contact details, technical evidence and achievements.
Match your personal statement, experience and dedicated skills section to the job description. Repeat relevant terminology naturally, but include only tools, methods and responsibilities that you can discuss confidently at interview.
No. Select software relevant to the vacancy and show how you used it, whether for modelling, design, analysis, evaluation or infrastructure management. A long unqualified list is weaker than a shorter list backed by project evidence.
Put the most relevant transferable evidence first, particularly project planning, resource control, risk assessment, technical communication and work within time or cost limits. Support it with engineering study or project evidence rather than relying on a previous job title.