Transportation Engineer Resume Examples (United Kingdom, 2026)

So here are three complete, UK-style CV samples you can copy in minutes. They’re written the way hiring managers and consultancies actually read: quick proof of scope, tools, standards, and measurable outcomes.

Pick the one closest to your level (mid, junior, senior), steal the bullets, swap the project context and numbers, and send it.

Breakdown: why this CV works (and how to steal it)

You’ll notice this isn’t trying to “sound impressive.” It’s trying to be easy to trust. In UK transport hiring, trust comes from three things: (1) you speak the standards (DMRB, Manual for Streets, TSRGD), (2) you name the modelling/design tools, and (3) you show outcomes that matter (delay, RFC, approvals, RSA closures).

Professional Summary breakdown

The summary hits the recruiter’s skim-test in under 10 seconds: years, specialism, tools, and a measurable win. It also signals the UK context (local authorities, planning approvals, DMRB stages) without turning into a paragraph of buzzwords.

Weak version:

Transportation engineer with experience in transport projects. Good communication skills and able to work in a team. Looking for a new opportunity.

Strong version:

Transportation Engineer with 6+ years’ experience delivering highway and junction design, traffic modelling, and active travel schemes for UK local authorities and developers. Reduced peak-hour delay by 18% on a signalised corridor by optimising MOVA settings and rebalancing junction geometry using LinSig and AutoCAD Civil 3D. Targeting a Transport Engineer role focused on scheme design through DMRB stages and stakeholder approvals.

The strong version works because it replaces vague claims (“experience,” “team”) with verifiable signals: tools (LinSig, Civil 3D), outcomes (18% delay reduction), and the type of work a Traffic Engineer / Highway Engineer is hired to do in the UK.

Experience section breakdown

The bullets are built like mini case studies: action + tool/context + measurable result. That’s exactly what a hiring manager needs to compare you against other candidates who only list duties.

Also: the numbers aren’t random. They’re the numbers transport teams actually care about—delay, queueing, RFC, approvals, RSA closures, rework.

Weak version:

Worked on junction modelling and produced drawings for highways schemes.

Strong version:

Built and calibrated LinSig models for 6 signalised junctions and recommended staging/green splits that reduced average delay by 18% and improved queue storage compliance on the A57 approach.

The strong bullet proves you can do the work end-to-end: model, calibrate, recommend, and improve performance—exactly what a Transport Engineer is expected to deliver.

Skills section breakdown

These keywords are not “nice to have.” They’re ATS filters and hiring-manager shorthand in the UK market. Consultancies and local authorities often search for:

• Standards: DMRB, Manual for Streets, TSRGD
• Development planning: Transport Assessments, Travel Plans, TRICS, TEMPro
• Modelling: LinSig, TRANSYT, Junctions 9, ARCADY/PICADY
• Design platforms: AutoCAD Civil 3D, sometimes MicroStation

That mix helps you match roles titled Transportation Engineer, Traffic Engineer, Highway Engineer, or Transportation Planner—without you needing four separate CVs.

How this junior CV differs from Sample #1 (and why it matters)

At junior level, nobody expects you to “own” a corridor scheme. What they do expect is that you can produce reliable outputs: clean data, consistent modelling inputs, tidy drawings, and documentation that survives review.

That’s why this CV leans on:

• Data quality (QA checks, Power Query, survey imports)
• Volume + repeatability (12 applications, standard checklist)
• Delivery support (consultation packs, RSA evidence)

If you’re early-career, this is your cheat code: show that your work reduces rework for the team. That’s value.

What makes a senior CV different (so you don’t undersell yourself)

Senior hiring is less about “can you run ARCADY?” and more about scope, decisions, and leadership. This sample still includes tools (because credibility matters), but the bullets focus on:

• Budget and programme scale (£45m)
• Governance (design assurance, risk reviews)
• People leadership (team of 6)
• Stakeholder outcomes (high-risk comments resolved)

If your CV reads like a task list at senior level, you’ll get screened out as “solid engineer, not a lead.”

How to Write Each Section (Step-by-Step)

You don’t need a “perfect” CV. You need one that matches how UK transport roles are hired: fast skim, quick credibility checks, then deeper reading if you pass.

a) Professional Summary

Use this simple formula and keep it tight:

[Years] + [specialism] + [achievement with a number] + [target role].

For a Transportation Engineer, “specialism” isn’t “transport.” It’s the slice you actually do: junction modelling, highway design, development planning (TA/TP), active travel, public realm, bus priority, RSA coordination.

Weak version:

I am a hardworking transportation professional looking for a challenging role where I can grow and contribute to projects.

Strong version:

Transportation Engineer with 5+ years delivering junction modelling (LinSig/Junctions 9) and highway design to DMRB and Manual for Streets for UK local authorities. Improved PM peak junction performance by reducing average delay 14% through staging changes validated in LinSig. Targeting a Traffic Engineer role focused on signal optimisation and scheme design.

The strong version is specific enough that a hiring manager can immediately place you: “This person can model, design, and speak UK standards.”

b) Experience Section

Write experience in reverse chronological order, but don’t treat it like a diary. Each bullet should answer: what did you change, using what, and what improved?

Transport hiring managers are allergic to “responsible for.” They want proof you can deliver outputs that survive review—DMRB compliance, modelling assumptions, RSA close-out, planning submissions.

Weak version:

Responsible for producing Transport Assessments and using TRICS.

Strong version:

Prepared 7 Transport Assessments (TRICS + TEMPro) for residential schemes and secured planning approval on 6/7 by strengthening sensitivity testing and aligning mitigation to the highway authority’s junction capacity thresholds.

If you’re stuck for metrics, use the ones your projects already track: number of junctions modelled, approval rate, delay/RFC changes, RSA issues closed, consultation response rates, rework reduction, milestone hit rate.

Action verbs that fit this profession (and don’t sound fluffy):

• Modelled, calibrated, validated, forecasted
• Designed, detailed, checked, assured
• Optimised, re-timed, re-staged, rebalanced
• Assessed, audited, mitigated, prioritised
• Coordinated, negotiated, secured, closed out

c) Skills Section

Your skills list is an ATS map. Build it from the job description, then back it up in your bullets. In the UK, transport CVs often get filtered by software and standards first—especially in consultancies.

Keep it tight and technical. Split your thinking into three buckets:

Hard Skills / Technical Skills

• DMRB, Manual for Streets, TSRGD
• Junction capacity assessment, signal optimisation, queue analysis
• Transport Assessments, Travel Plans, development planning support
• Road Safety Audit (Stages 1–4) coordination/response
• Active travel design, bus priority, public realm layouts

Tools / Software

• LinSig, TRANSYT, Junctions 9 (ARCADY/PICADY/OSCADY)
• TRICS, TEMPro
• AutoCAD Civil 3D, AutoCAD, MicroStation
• QGIS, Excel (Power Query)
• AutoTURN (swept path analysis)

Certifications / Standards

• DMRB compliance (scheme design stages)
• Road Safety Audit process (UK practice)
• CDM awareness (Construction Design and Management)

Don’t add generic soft skills here. If you want to show communication, prove it in experience: “secured approvals,” “resolved comments,” “led consultation materials.”

d) Education and Certifications

In the UK, education matters most early-career. After ~5 years, it becomes a credibility line—not the headline. Include your degree, university, and dates. Add relevant modules only if you’re a graduate and they match the role (transport planning, highway engineering, traffic modelling).

For certifications, focus on what employers actually recognize in transport teams: Road Safety Audit exposure, DMRB familiarity, and CDM awareness. If you’re working toward a professional qualification (e.g., chartership pathway), you can list it as “In progress” with a date—just don’t oversell it.

If you did short courses (LinSig, TRICS, Civil 3D), include them only if you can also show you used the tool on a real project. Otherwise it reads like a shopping list.

Common Mistakes (Transportation Engineer CVs)

One classic mistake is writing like a Transportation Planner when the role is clearly a Traffic Engineer or Highway Engineer. If the job ad screams “LinSig, DMRB, junctions,” and your CV talks only about “sustainable transport strategy,” you’ll look misaligned. Fix it by mirroring the role’s deliverables: modelling outputs, design packages, approvals.

Another is hiding the standards. UK reviewers want to see DMRB, Manual for Streets, TSRGD, RSA stages—because those reduce risk. If your CV says “designed highways schemes” without naming the standards, you force the reader to guess.

A third is listing software without proof. “LinSig” in skills is meaningless if your experience bullets never mention a model, a calibration step, or a performance result. Add one bullet that shows what you did with it and what changed.

Finally, many candidates avoid numbers because they feel “too specific.” In transport, numbers are the language: delay, RFC, queue length, approvals, issues closed. Use them.

Conclusion

A strong Transportation Engineer CV in the United Kingdom is simple: prove your standards, name your tools, and quantify the outcome. Copy one of the samples above, tailor the summary to the job title (Transport Engineer / Traffic Engineer / Highway Engineer), and keep every bullet evidence-based.

When you’re ready to format it cleanly and make it ATS-friendly, build it in cv-maker.pro with the keywords and structure from this page.

CTA: Create my CV