The project interview: by the shortlist, capability is assumed and the decision is about people

The team is the product

The owner is buying people, and the interview should reflect that. Three principles:

• Bring the people who will do the work. The project executive, the project manager and the superintendent who are actually assigned. If they cannot be committed, saying so honestly is better than implying otherwise.
• Let them talk. A superintendent describing how they would phase the work while the building stays occupied is more persuasive than any slide. Owners are evaluating judgment and communication, and neither is demonstrated by a project executive answering on someone's behalf.
• Show the continuity. Who is here from preconstruction through closeout, and what happens at each handoff. Owners have been burned by teams that changed after award, and addressing that directly earns credibility.

One commitment carries disproportionate weight: naming the superintendent and stating their availability. It is specific, it is verifiable, and it is the thing most competitors leave vague.

What to actually present

The strongest interviews spend most of their time on the owner's project rather than on the contractor's history. A structure that consistently works:

• Open with what you understand about the project, including the constraints the owner is worried about. Demonstrating that you have read the documents and walked the site is the fastest way to earn attention.
• Name the three biggest risks and how you would manage each. This is the section that wins interviews. Every project has three or four real risks, the owner knows what they are, and most contractors avoid mentioning them for fear of sounding negative. Naming them accurately is the strongest possible signal of competence.
• Present a preliminary approach to phasing and logistics, ideally with a simple graphic. Concrete beats abstract.
• Show the schedule thinking, including long-lead items, the milestones that drive the rest, and where you see float and where you do not.
• Address cost and how it will be controlled, with the estimating approach, the buyout plan and how the owner will see the numbers.
• Use references sparingly and specifically — one comparable project, what went wrong on it, and what was done about it. A story about a problem handled well is worth more than five projects delivered without incident.

The questions that follow

Most interviews are decided in the question period, not the presentation, and preparation for it is the most neglected part of the process.

Prepare honest answers to the four questions that get asked in nearly every interview: what happens if the schedule slips, how change orders will be handled, what happens if the project comes in over budget at the pricing milestone, and who the owner calls when there is a problem. Vague answers to these read as evasion, and specific ones — including admitting what the contractor cannot control — read as experience.

The team should also ask questions, and they should be real ones. Asking what the owner's biggest concern is, what has gone wrong for them previously, and how they prefer to receive information changes the tone of the room from an audition to a working conversation, which is precisely the relationship being purchased.

Rehearsal, timing and the room

Contractors rehearse interviews far less than the stakes justify. A pursuit that consumed two hundred hours of estimating and coordination frequently gets one run-through in a hallway. Four practices change the outcome.

• Rehearse out loud, at least twice, with the actual team. The first rehearsal exposes that the presentation is too long, which it always is. The second fixes it.
• Assign who answers what. The most damaging moment in an interview is three people looking at each other after a question. Decide in advance who owns schedule, who owns cost, who owns field execution and who redirects.
• Time it and cut it. Nearly every interview runs long and gets cut off, which means the material at the end — usually the closing and the commitment — never happens. Build the presentation to finish with time left for questions, because the questions are where the decision is made.
• Prepare for the room you will be in. Whether it is in person or remote changes everything about pacing, visuals and who can be heard. Remote interviews in particular punish long slides and reward one person speaking at a time with clear handoffs.

One further detail matters more than it should: leave something behind that is useful without you. A short, well-organized document containing the team, the risk analysis, the phasing concept and the schedule milestones will circulate among people who were not in the room — and in committee decisions, the person who was not there is frequently the one who has to be convinced by someone else.

Fee, and how not to win by being cheapest

In negotiated work the fee is usually a smaller factor than contractors fear, but it is rarely irrelevant, and how it is presented matters as much as its size.

Three practices help. Present the fee structure with clarity about what is in general conditions, what is in the fee, and what is reimbursable — ambiguity here is where owners have been burned and where they will probe. Explain the value of the preconstruction service concretely, because owners paying for preconstruction want to know what they receive and when. And avoid buying the job on fee, since a fee that is visibly below the market invites the question of where the money will be recovered, which is a question that has damaged more contractors than a slightly higher fee ever did.

Choosing what to pursue

The most profitable improvement available to most contractors in negotiated work is not a better presentation — it is pursuing fewer, better-matched opportunities. A serious interview consumes preconstruction hours, estimating time and the attention of the people who are also running projects, and a company chasing everything arrives at each interview slightly underprepared.

Four filters make the decision honest. Whether the company has directly comparable experience in that project type, since selection committees weight relevance heavily and general capability rarely overcomes its absence. Whether a relationship exists with the owner, the architect or the owner's representative, because in qualifications-based selection an unknown firm is competing against known ones. Whether the team that would be presented is genuinely available on the project's schedule, given that promising an unavailable superintendent is the fastest way to damage a reputation that took years to build. And whether the project is one the company actually wants — the right size, the right delivery method, the right terms — because winning the wrong project is a two-year problem.

Companies that apply these filters typically pursue fewer opportunities, win a higher percentage, and spend the recovered hours on the pursuits they kept. That is a better outcome than any improvement in slide design.

After the interview

Two follow-ups are worth doing consistently. Send a short, substantive note within a day that includes something specific from the discussion — a clarification, an answer to a question that came up, a piece of information promised. Not a thank-you letter, which everyone sends and nobody reads.

And request a debrief regardless of the outcome. Owners and their advisors usually agree, most contractors never ask, and the information is unusually valuable: whether the loss was price, team, approach or presentation. Three debriefs will tell a company more about its win rate than a year of internal discussion.

Five mistakes in the project interview

• Presenting the company instead of the project. The shortlist already established capability; the interview is about this job.
• Bringing executives instead of the project team. Owners are hiring the people who will run the work, and substitution is obvious.
• Avoiding the project's real risks. The owner knows what they are, and naming them is the strongest available credibility.
• Not preparing for the questions. The decision is usually made in that half hour, and generalities lose it.
• Never asking for a debrief. It is free, it is usually granted, and it is the only reliable way to find out why you lost.

The numbers to track

Five numbers turn business development into a managed process. Shortlist rate — submissions that become interviews — which measures the quality of the qualifications package. Interview win rate, which measures the team and the preparation. Win rate by project type and by owner type, because most contractors are far stronger in one segment than they realize. Cost of pursuit per opportunity, including the hours of senior people, which reveals that chasing everything is expensive. And the debrief reasons, tabulated over a year, which is the only feedback loop in this process that is based on evidence rather than assumption.

Frequently asked questions

How is a project interview different from a hard bid?

Hard bidding rewards the lowest responsible number; negotiated and qualifications-based selection rewards the owner's belief that this team will deliver their project with the fewest problems. That is why contractors who are excellent at bidding frequently lose interviews — they walk in and present the company when the owner is trying to evaluate the people who will actually run the job. By the time a shortlist exists, the owner has already accepted that every firm in the room is capable of building the project. What they are deciding is who they want to spend eighteen months with, and how much they believe the schedule and the number. The most common losing move follows directly from missing this: sending the leadership team to present a project that will be run by people who are not in the room, which owners notice immediately and which undermines everything else that is said.

What should a contractor do before the interview?

Three things, and they usually decide the outcome weeks in advance. First, the qualifications submission, which is scored and frequently determines who interviews at all — it should answer the questions asked, in the order asked, with project experience matching this project type rather than a general portfolio, because owners and their advisors read many of these and can tell in thirty seconds whether a response was tailored or recycled. Second, understanding the decision: who is on the selection committee, what each of them cares about, what went wrong on their last project, whether an architect or owner's representative is advising, and whether price is scored and with what weight — most of which can be learned by asking, which is not improper but professional. Third, walking the site and reading the program to form an actual opinion about the project's risks, which separates a team that presents from a team that discusses.

What should be presented in the interview itself?

Mostly the owner's project rather than the contractor's history. Open with what you understand about the project including the constraints the owner worries about, which is the fastest way to earn attention. Then name the three biggest risks and how each would be managed — this is the section that wins interviews, because every project has three or four real risks, the owner knows what they are, and most contractors avoid mentioning them for fear of sounding negative, so naming them accurately is the strongest possible signal of competence. Present a preliminary phasing and logistics approach with a simple graphic, since concrete beats abstract. Show schedule thinking including long-lead items and where float exists and does not. Address cost control, the estimating approach and how the owner will see numbers. And use one comparable reference project specifically — a story about a problem handled well beats five projects delivered without incident.

What questions get asked and how should they be handled?

Most interviews are decided in the question period rather than the presentation, and preparation for it is the most neglected part of the process. Four questions come up in nearly every interview: what happens if the schedule slips, how change orders will be handled, what happens if the project comes in over budget at the pricing milestone, and who the owner calls when there is a problem. Vague answers read as evasion; specific ones, including honest statements about what the contractor cannot control, read as experience. The team should also ask real questions in return — what the owner's biggest concern is, what has gone wrong for them previously, and how they prefer to receive information — which changes the tone from an audition to a working conversation, and that conversation is precisely the relationship being purchased. Assign in advance who answers what, because three people looking at each other is damaging.

Should you ask why you lost?

Always, and almost nobody does. Owners and their advisors usually agree to a debrief, and the information is unusually valuable: whether the loss was price, team, approach or presentation. Three debriefs will tell a company more about its win rate than a year of internal discussion, and tabulating debrief reasons over a year is the only feedback loop in this process based on evidence rather than assumption. The other follow-up worth doing consistently is a short, substantive note within a day of the interview that includes something specific from the discussion — a clarification, an answer to a question that arose, information promised — rather than a thank-you letter, which everyone sends and nobody reads. Alongside those, track shortlist rate, interview win rate, win rate by project and owner type, and cost of pursuit per opportunity, which together turn business development into a managed process.