Design Interface Civil Engineer

A design interface civil engineer works on large infrastructure projects (rail, highways, water, energy, major buildings) making sure the different parts of a design actually fit together. Rather than designing one element in isolation, they sit between design teams, contractors and clients - checking that, say, the track design, the drainage, the overhead power equipment and the structures all occupy the right space, follow the same assumptions and don't clash. The job exists because big projects are split between many organisations and disciplines, and most expensive mistakes happen at the joins.

Starting salary: £27k–£34k
Live graduate jobs: 1 open now
Main way in: The most common route by far
They usually ask for: An accredited civil or structural engineering degree is the norm

Approximate graduate salary

Graduate civil engineering roles typically start somewhere around £27,000–£34,000, with London and major-programme roles at the higher end and smaller regional consultancies lower. This is approximate and varies widely by employer, sector and location; pay usually steps up noticeably on achieving chartered status.

What you'd actually do

Reviewing drawings and 3D models from different design disciplines side by side, looking for clashes - a cable route passing through a structural beam, a drainage run that conflicts with foundations, a maintenance access route blocked by equipment.
Running or attending interface meetings where engineers from different teams or companies talk through unresolved issues, and writing up the decisions so they don't get lost.
Maintaining an interface register - a tracked list of every point where one party's design depends on another's - chasing owners for responses and escalating items that are stuck.
Checking that assumptions match across packages: loadings, levels, datum points, design life, clearances, who is providing which bit of hardware at a boundary.

Show 3 more

Doing some actual design work yourself - calculations, sketches, markups, specification clauses - particularly in your first couple of years, since you need credibility with the discipline teams.
Preparing and issuing technical queries and change notices, and assessing what a change in one package means for everyone else's programme and cost.
Site or model walkthroughs and constructability reviews, checking that what has been drawn can physically be built in the sequence planned.

How graduates get in

The most common route by far: a civil engineering graduate scheme at a consultancy or contractor, joining a general design team and being pulled into interface work on a large project after a year or two. Very few employers advertise 'design interface engineer' at graduate level - it's usually a role you move into.
Direct entry as a graduate or assistant engineer on a specific major programme (rail upgrades, nuclear, water AMP frameworks, large highways schemes), where interface and coordination work starts early because the project is split across many packages.
A year in industry placement or summer internship with a consultancy or contractor, converting to a graduate offer - this is a strong route and often the easiest way in.
Degree apprenticeship in civil engineering, working while studying, then moving into project design teams. Increasingly common and treated equivalently by most employers.

Show 2 more

Conversion from a related degree (structural, mechanical, geotechnical, building services, or an MSc in civil/structural engineering) - realistic, though you'll usually need the MSc or strong relevant experience to be taken seriously for an accredited route.
Occasionally sideways from a BIM or digital engineering coordinator role, where you already do clash detection and model federation and then pick up the engineering side. Less common but it does happen.

What employers ask for

An accredited civil or structural engineering degree is the norm - accredited meaning approved by the Joint Board of Moderators on behalf of the Institution of Civil Engineers (ICE) and similar bodies, which matters for later chartership. Related engineering degrees are often accepted; non-engineering degrees generally are not without a conversion MSc.
Most graduate schemes ask for a 2:1, though a fair number accept a 2:2 with relevant placement experience, and some employers (especially smaller consultancies and contractors with hiring pressure) are flexible. Requirements genuinely vary - do not assume a 2:2 rules you out.
A BEng alone satisfies part of the academic requirement for Chartered Engineer status; an MEng or BEng plus an accredited MSc satisfies it fully. Many employers will fund a 'technical report route' or further study if you only have a BEng.
Working knowledge of standard design and modelling software - typically AutoCAD, Revit or Civil 3D, model federation and clash detection tools, and discipline-specific analysis packages. Employers expect familiarity, not expertise, at entry.

Show 2 more

Right to work in the UK, and for defence, nuclear and some rail work, eligibility for security clearance or sponsor-specific vetting. This can be a hard gate on certain projects.
A driving licence is often asked for on infrastructure projects where site visits are frequent, though it's not universal.

Skills that matter

Reading other disciplines' drawings and models

You cannot spot a clash between a structural frame and a cable containment route if you can only read civil drawings - the job is fundamentally about understanding enough of everyone's language.

Spatial and 3D reasoning

Much of the work is holding a complex arrangement in your head and noticing that two things want to occupy the same volume, or that a crane cannot reach where the drawing assumes it can.

Written precision in technical correspondence

Interface agreements, technical queries and meeting records become contractual evidence later, so an ambiguous sentence about who provides a bracket can cost real money.

Chasing people without annoying them

You usually have no authority over the engineers you depend on, so progress comes from being persistent, well-prepared and easy to say yes to.

Tracking lots of open items at once

A typical package has dozens of live interfaces at different stages, and the failure mode of this role is quietly losing one until it surfaces on site.

Understanding programme and change

Knowing when a design decision is needed, and what it blocks if it slips, is what makes your escalations credible to project managers.

Putting these on a CV? We counted which skills 12,914 live graduate adverts ask for, and what to do with the answer — part of our application advice.

Where it leads

Graduate or assistant engineer (roughly the first two to three years): doing supported design work, taking minutes, maintaining registers, learning how packages fit together. You'll be working towards the ICE Initial Professional Development requirements with an assigned mentor and supervising civil engineer.
Engineer, owning interface issues yourself and leading smaller coordination meetings. Chartership (CEng via the ICE, or IStructE/CIHT depending on your discipline) is typically achieved around four to six years after graduating under a structured training agreement, though people on less structured routes often take longer - timelines vary a lot.
Senior engineer or interface manager, responsible for the interface strategy across a whole package or a set of packages, managing junior engineers and fronting discussions with the client and other contractors.
From here the path forks. Some go deeper technically towards principal engineer and technical authority roles; others move into project management, package management or systems integration, which is a strong fit because the skills overlap heavily. A move into client-side roles (infrastructure owners and major programme clients) is also common and often well paid.
Longer term: programme-level integration lead, design manager, or project director on major schemes. Timelines here vary enormously and depend far more on which projects you happen to be on than on years served.

What people get wrong

“It's a coordination or admin job rather than real engineering.”

You need genuine technical judgement to know which clashes matter and which are noise - deciding whether a 50mm overlap is a real problem or a modelling artefact requires understanding both disciplines' tolerances. Many interface engineers continue doing design work alongside it, and you'll struggle to be taken seriously by discipline leads if you can't.

“Clash detection software finds the problems for you.”

Software finds geometric overlaps in models. It does not find the problems that actually bite: two teams using different assumed loadings, a boundary where both parties assumed the other was supplying a component, or a maintenance access route nobody modelled. Those come from reading documents and asking awkward questions in meetings.

“You work alone at a desk on technical problems.”

It's one of the more people-heavy engineering roles. A large share of the week is meetings, calls and negotiation with people in other companies who have competing commercial interests and no obligation to prioritise your query.

“Taking this role takes you off the chartership track because it isn't 'proper' design.”

Interface work maps well onto several of the ICE competences, particularly around managing engineering activity, communication and commercial awareness. The real risk is under-evidencing technical design competence, which is why most people keep some hands-on design going and plan their experience record with their mentor.

Where this varies

The role looks quite different depending on who employs you. At a design consultancy you're mostly coordinating between in-house discipline teams and managing the client relationship. At a main contractor you're coordinating between subcontractors and the construction programme, with more site exposure and more commercial pressure. On the client side (infrastructure owners and major programme organisations) you're policing interfaces between separate contractors and the focus shifts heavily towards assurance and contract boundaries. Sector matters too: rail and nuclear are the most interface-heavy and the most process-driven, with formal registers, gated design reviews and sometimes security clearance; highways and water are typically lighter-touch; building-led projects often call the same work BIM coordination or design management. Job titles are inconsistent across the industry - 'interface engineer', 'design coordinator', 'integration engineer' and 'design manager' can describe very similar work, so read the advert rather than the title.

See all 1 live Design Interface Civil Engineer jobsFrom employers' own careers sites, updated daily Tailor your CV for this roleFree with an account, 3 a month

General guidance about the role across the UK market, not about any specific employer. Entry routes and requirements vary — always check the individual job advert.