Construction candidate backlog claims describe the project, not the person. A resume line reading $200M of healthcare experience is compatible with carrying the estimate, owning the buyout, running the change-order position, or attending the meeting. One question separates them: what number were you accountable for, and what did it do?
Backlog claims on a construction resume in Dallas or Atlanta all say roughly the same thing. Sector, delivery method, and a dollar figure that is meant to convey scale.
The figure is almost always true. It is also the least informative sentence on the page, and hiring managers read it as capability because there is nothing else on the document that looks like a measurement.
What do construction candidate backlog claims actually tell you?
They tell you the scale of the environment the person worked in, and nothing about what they controlled inside it. A $200M project employs a project executive, two project managers, a superintendent team, a chief estimator and a cost engineer. All six can write $200M on a resume truthfully.
This is not resume inflation and treating it as dishonesty leads you badly astray. It is the industry’s standard convention: people describe their work by the projects they were on, because that is how construction talks about itself. Ask any group of project managers what they run and they will name jobs and values, not scopes of control.
The problem is that the convention encodes almost no signal for a hiring decision. Two candidates with identical resume lines can be a person who set the contingency position on a negotiated healthcare job and defended it to an owner, and a person who produced the monthly report describing what someone else decided.
Both were on the job. Only one of them has done the work you are hiring for.
What question turns backlog claims into information?
Ask what number they were personally accountable for, and what that number did while they held it. Someone who owned a position answers with a figure and a direction inside ten seconds. Someone who was adjacent to it describes the team, the process, or the project.
The follow-ups matter as much as the question. A candidate who says they held the contingency on a $60M negotiated job should be able to say what it started at, what it ended at, and what moved it. Not to the dollar, and not from memory of a job four years ago, but in shape: it started around three percent, we gave back a chunk at buyout, we spent most of the rest on an unforeseen condition in the podium.
That answer cannot be produced by someone who was not there. It is not a memory test, it is a structural one, and it is the fastest way to separate the four people hiding behind one resume line.
- What number were you accountable for? A specific figure, or the honest answer that they were not.
- What did it do while you held it? Direction and cause, not just the outcome.
- Who could overrule you on it? Defines the real decision boundary, which the title never does.
- What would you have done differently? Ownership shows up here or it does not show up at all.
The third question is the one that surfaces scope most reliably. A chief estimator whose number went to the owner without the president reviewing it is a different professional from one whose number was always reviewed, and neither is better. They are simply different seats, and your seat is one of the two.
How do you compare backlog claims that are not comparable?
Convert every claim into two figures that line up: the value the person was accountable for, and how many concurrent jobs it was spread across. Total project value is not comparable across candidates. Accountable value and concurrency are.
Consider three candidates who all write $90M on the resume. The first was the project executive on a single $90M hospital, negotiated, with a GMP set at sixty percent design development. The second ran six concurrent $15M tenant improvement jobs. The third was one of two project managers on a $90M job, running the MEP-heavy half. Selah runs confidential searches for a senior project manager.
The chart shows the largest single unit each of them actually carried. The first carried $90M as one thing. The second carried $15M as the largest single unit, six times over, which is a coordination and delegation discipline rather than a depth one. The third carried roughly $45M as their half of a larger job, with a peer to negotiate with and a project executive above.
If your open seat is a single large negotiated job, the first candidate has done it and the second has not, whatever the totals say. If your seat is six concurrent jobs in a busy Southeast market, the second candidate is the only one of the three with the relevant discipline. That is a span of control question as much as a capability one.
| What the resume says | What to ask | What you learn |
|---|---|---|
| Total project value | What were you accountable for? | Scope of control, not environment |
| Sector experience | Which delivery method, and for how long? | Whether hard bid or negotiated fits |
| Years in role | How many concurrent jobs at peak? | Coordination depth against single-job depth |
| Team size managed | Who could overrule you, and on what? | The real decision boundary |
Why does this matter more in a hard market?
Because the temptation to accept a plausible resume rises with the difficulty of finding one. In the 2025 workforce survey published by AGC and NCCER, 91.7 percent of the 1,041 contractors answering the salaried-hiring question reported difficulty filling those positions.
When candidates are scarce, a resume that matches on sector, value and delivery method feels like a find, and the questions above feel like an unnecessary risk to a fragile conversation. That instinct is precisely backwards.
The scarcity does not change what the person controlled. It changes only how much the mistake costs, because a mis-hire in a tight market means a second search that is harder than the first, into a pool that has now had a bad experience of your firm.
The other reason to be rigorous is that these questions do not repel good candidates. They attract them. A strong project executive who genuinely held the position wants to be asked, because the question distinguishes them from the people whose resumes look identical. The candidates who find it uncomfortable are usually the ones the question was designed to find. That is also why reference checks work better when they test the same specific claims rather than asking for a general impression.
Who does this not apply to?
Two cases. Early-career candidates, whose resumes legitimately describe environments rather than owned positions. And specialist seats where the history is not project-shaped: a preconstruction technology lead, a risk manager, a business development director in one metro.
For those, the equivalent question is the same shape with a different object. What were you accountable for, what did it do, who could overrule you. The specific instrument changes and the underlying test does not.
It also does not apply where you already know the answer. On a confidential replacement run as confidential executive search for mandates that cannot be publicly posted, the shortlist is often people your search partner has watched for years. The backlog conversation is then a formality. That is a narrow case. Everywhere else, one question turns a number into a fact.
If you want a shortlist built against what candidates controlled rather than where they worked, that is the difference between a search and a resume feed. We would rather have that conversation with employers before the first interview than after the third.
Sources and further reading
- AGC, Associated General Contractors of America
- NCCER, construction education and research
- BLS wage data, construction managers (11-9021)
- BLS wage data, cost estimators (13-1051)