What Tier One Contractors Look For When Hiring Engineering Professionals

Tier One is not a formal classification. There is no register or accreditation that makes a contractor Tier One rather than Tier Two. It is a convention, built on the scale of work a company can deliver, the frameworks it sits on, and the size of client it can be trusted with. But for candidates, what that convention translates into is a hiring bar that is genuinely higher, and often stricter, than the rest of the market. Understanding what these organisations are actually looking for, and how to show it on a CV, makes a real difference to whether an application gets read past the first ten seconds.

The CV Mistake That Costs the Most Interviews

The single biggest issue we see on engineering CVs applying for Tier One roles is a list of duties instead of a record of delivery. A CV that reads “responsible for site supervision, quality control and liaison with subcontractors” tells a hiring manager almost nothing they cannot assume from the job title. It does not tell them what was actually built, how complex it was, or what the candidate's specific contribution was within a much larger team.

Compare that with something closer to: “Site engineer on a £40 million water treatment upgrade for a municipal client, responsible for setting out and quality control across two treatment streams, tracking a twelve-month lead time on switchgear that carried real schedule risk.” The second version does the same job of describing the role, but it also answers the questions a Tier One hiring manager is actually asking: how big was the project, how complex was it, what was genuinely your responsibility within it, and what would you bring to our next scheme.

This matters more in infrastructure than almost anywhere else in construction, because the scope gap between projects that look similar on paper can be enormous. A project manager who delivered a £40 million commercial fit-out and a project manager who delivered a £40 million water treatment upgrade for a public body have very different experience, even with an identical job title and budget. Funding compliance, public accountability, long lead times on specialist plant and a client with zero tolerance for surprises are a different discipline entirely from private commercial delivery. Tier One contractors know this, and a CV that fails to draw out that distinction risks being read as less experienced than it actually is.

Project Experience, Not Just Project Names

It is common to see a CV list a string of well-known schemes with little detail beyond the project name and dates. Naming a major programme signals scale, but it does not, on its own, tell a hiring manager what the candidate actually did. Tier One contractors are looking for the detail underneath: what was your specific scope, what problems did you solve, what would have gone wrong without your input, and what was the measurable outcome.

A useful structure for each role on a CV is to briefly set out the project (value, sector, client type), then the candidate's specific responsibility within it, then a genuine outcome or achievement, ideally quantified. Delivered ahead of schedule. Reduced a specific cost line. Resolved a particular technical or contractual issue. Numbers do not need to be dramatic to be useful. A specific, honest figure is far more convincing than a vague claim of success.

Technical Credibility, Clearly Signposted

Tier One contractors work across complex contractual frameworks, NEC in particular for most UK infrastructure, and increasingly digital delivery tools such as BIM and integrated cost and programme management software. A CV that name-checks the relevant contract forms, software and compliance standards a candidate has actually worked with, rather than a generic skills list copied from a job description, gives a hiring manager confidence that the candidate can be productive quickly, without a long induction into tools and terminology they should already know.

The same applies to safety and quality credentials. CSCS, relevant CITB or sector-specific cards, and any professional body membership or progress towards chartership should be stated clearly and kept current on the CV. These are not decorative. On regulated infrastructure work, they are often the first thing a hiring manager checks before reading anything else.

Progression That Tells a Story

Tier One hiring managers read a CV's career history for a pattern, not just a list of jobs. A candidate who has taken on genuinely larger scope, more responsibility or greater technical complexity with each move reads very differently to one whose roles have simply repeated the same level of work under different job titles. If your career has involved a genuine step up in responsibility, make that visible rather than assuming it will be obvious from the sequence of employers and dates.

Equally, if there is a gap or a lateral move in your history, a single honest line explaining it, a fixed-term contract ending, a deliberate move to gain experience in a new sector, does more good than leaving it unexplained and inviting a hiring manager to guess.

What This Means in Practice

Before submitting a CV for a Tier One infrastructure role, it is worth reading back through each project entry and asking three questions. Does this tell the reader the actual scale and complexity of the work, not just the project name? Does it show what I specifically did, rather than what the team or company achieved? And does it include at least one concrete, honest outcome rather than a general statement of success?

A CV that can answer yes to all three, even for a handful of key roles, will consistently outperform a longer, more comprehensive document that lists every duty from every job without ever showing what any of it actually delivered.

If you are working on your CV for an infrastructure role and want a second opinion, or you are trying to work out how your experience translates to a Tier One environment, we would be glad to talk it through.