How to prepare for a QBS interview

Opening: prepare to be evaluated as a team

QBS usually refers to qualifications-based selection for professional services. For federal architecture and engineering procurements, the Brooks Act sets out a qualifications-based process. State and local procedures vary, so read the solicitation and applicable procurement rules. Interview format, scoring criteria, and allowed materials can differ by client and project.

Treat the interview as part of the project, not a separate sales performance. Attendees should understand the likely work, know their responsibilities, and be ready to discuss real decisions. A technically strong team can lose confidence if it gives vague answers, lets one person dominate, or presents a plan that does not fit the client’s needs.

This guide is for owners and principals preparing a civil engineering firm for a QBS interview. It covers evaluation criteria, team roles, project approach, qualifications, answers, accessible materials, rehearsal, and follow-up. Licensed PE judgment and local codes govern engineering decisions.

Start with the evaluation criteria

Before building a presentation, identify what the client says it will evaluate. Read the request for qualifications and interview notice, plus addenda and any stated agenda. Anchor preparation in the written selection criteria. Do not assume the client values the same things your firm does or that a previous interview format will repeat.

Make a one-page criteria map. For each criterion, record the requirement, the person who will address it, and the evidence you can provide. Criteria may include relevant project experience, key personnel, understanding of the project, schedule, quality management, communication, risk management, or coordination with other disciplines. Use the client’s terms when they are clear.

Separate explicit criteria from reasonable inferences. If the solicitation calls for municipal roadway design experience, that is explicit. If it describes an active downtown corridor but does not name traffic management as a criterion, it may still be sensible to prepare for questions about maintaining access and coordinating with stakeholders. Keep the distinction clear so the team does not present an assumption as a client requirement.

Check practical instructions as carefully as the technical scope. Confirm interview length, presentation limit, attendee limit, submission format, technology, question period, and whether the client expects a formal presentation. Follow rules about materials and contact. Ask the procurement contact for clarification through the permitted channel when a requirement is ambiguous.

Turn the criteria into a preparation matrix:

Criterion: What is the client evaluating?
Evidence: Which project, person, method, or record supports the point?
Speaker: Who is best placed to explain it?
Proof: What concise example or visual makes it credible?
Likely question: What might the panel ask to test the claim?

This exercise exposes gaps early. If the team has a strong claim but no specific evidence, find a supportable example or revise the claim. General phrases such as “responsive team” and “high quality” do little on their own. Explain what the team does to respond promptly or produce quality results.

The map also helps the firm allocate preparation time. A criterion with substantial weight or a direct connection to project risk deserves a clear answer and capable speaker. An incidental point may need only a brief response. Never invent scoring weights the client has not provided.

Assign team roles before the interview

The proposed project manager or principal should usually lead, connecting the client’s need to the firm’s team and approach. The lead should not answer every technical question. The panel needs to hear from the people who will do the work and make decisions.

Choose attendees based on their delivery roles. Depending on the project, the team may include:

Principal or client lead: accountable for the client relationship and resource commitments.
Project manager: coordinates scope, schedule, communication, and decisions.
Technical lead: explains engineering methods, design issues, and technical review.
Discipline lead: addresses a significant specialty such as drainage, structures, traffic, geotechnical coordination, or utilities.
Construction or field representative: speaks to constructability, site conditions, phasing, or construction support when relevant.

Avoid adding attendees just to display firm size. Each person should have a defined reason to attend and a clear contribution. If the panel asks who will do the work, the proposed team should answer without hedging.

Agree on handoffs. The project manager might frame a schedule question, then invite the technical lead to explain design dependencies. The principal can clarify a staffing commitment. Transitions should feel natural, not scripted.

Discuss sensitive commitments before interview day. Who can authorize a scope adjustment? Who will tell the client that a requested date is not feasible? Who will escalate a safety or permitting conflict, or handle a utility conflict? The team should not promise every request can be accommodated. It should explain how it will assess requests, describe consequences, and involve the right decision-maker.

Present a consistent picture of accountability. If the principal says the project manager will have authority, the manager should be ready to explain what that means. If a specialist will be available only at key milestones, say so accurately. Clear availability is more credible than implying every senior person will be involved daily.

Explain a project approach the client can picture

A strong project approach connects the client’s needs to a sequence of work and decisions, supported by clear communication. Make it specific enough to show that the team has thought through the project, while leaving room to confirm unknowns after selection.

Begin with the client’s desired outcome. It may be a safe design, a permit-ready package, improved access, a reliable construction schedule, or a coordinated improvement within funding and property constraints. State the outcome in the client’s terms, then identify conditions that could affect it.

Describe phases that fit the scope. A roadway project might begin by confirming base data, utilities, survey needs, and stakeholder constraints, then move through alternatives and preliminary design. It may advance through final design, permitting, bidding support, and construction services if included. A water or drainage project may have different technical steps. Use the actual scope rather than a generic lifecycle diagram.

For each phase, explain:

What the team will do.
What information or decision it needs.
Who will lead the work.
How the client will review progress.
What could change schedule, cost, or the recommended option.

This makes the approach useful to the panel. Instead of saying “we communicate proactively,” say what the client can expect: a named project manager, agreed meeting cadence, concise decision records, and prompt notice when an issue could affect cost or schedule. Do not promise response times or deliverables the firm cannot meet.

Discuss project-specific risks without pretending to know what has not been investigated. Common issues may include incomplete utility information, right-of-way constraints, permitting dependencies, environmental review, railroad coordination, traffic staging, public access, or conflicts with other projects. Identify what warrants early confirmation and explain how the team will address it.

Show how alternatives will be compared. The client may consider performance, maintainability, construction impacts, property needs, permitting, and life-cycle implications. Explain which factors matter and how the team will present tradeoffs. If criteria or data are not yet known, say what must be confirmed before recommending an option.

Connect quality management to the proposed work. Name who is responsible for technical review, when reviews will occur, and how comments will be tracked and resolved. Describe discipline coordination and how the team will check that drawings and calculations agree. Confirm separately that specifications match. Avoid guarantees that imply no issue can occur. A credible process identifies how the team finds and addresses issues.

If the panel raises a constraint that changes your approach, respond to it. A project plan is not fixed. Show that the team can listen, assess new information, and explain what must be checked before committing to a change.

Select qualifications that match the assignment

Relevant qualifications are evidence, not a catalog. Choose projects that resemble the assignment in important ways: technical conditions, client type, delivery method, public involvement, schedule pressure, permitting context, or coordination demands. A project need not be identical if you can explain the connection honestly.

For each example, prepare a concise account:

The client’s need and project context.
Your firm’s actual role and scope.
The team members or methods relevant to this selection.
The constraint or challenge addressed.
The result, stated with supportable facts.
What experience transfers to the current assignment.

Be precise about who did the work. If a project was completed by a subconsultant, predecessor firm, or individual before joining your firm, explain the relationship. Do not imply your current team delivered work it did not perform. The panel may ask for references, project records, or details to test the claim.

Bring examples from people as well as firms. A principal may have deep experience, but the client also needs confidence in the proposed project manager and technical leads. Identify their responsibilities on example projects and how they will apply that experience here.

Choose a manageable set of examples. Too many summaries blur the connection. One closely matched project and a second demonstrating a different need can make a clearer case than a long list. If the firm lacks direct experience in one area, explain adjacent experience and how the team will close the gap, such as through a qualified specialist already identified for the project.

Prepare a candid answer about lessons learned. Do not claim every project went perfectly. Explain a relevant challenge, the action taken, and how the team applies that learning. Keep the discussion factual and appropriate to confidentiality obligations.

Listen and answer with discipline

Interview panels often combine several issues in one question. Listen through the full question, note its parts, and answer in a sensible order. If a term is unclear, ask a brief clarifying question. A short pause is better than answering a question the panel did not ask.

Lead with the direct answer, then give the reason, a specific example, and the implication for this project. Keep the first response focused and let the panel ask for more detail. A useful pattern is answer, evidence, application. For example, state who will manage utility coordination, describe a relevant process, and explain how it would begin on the proposed project.

Answer as a team. The technical lead may be right for a design review question. The project manager or principal may be better placed to discuss contract administration or staffing authority. The lead can direct a question to a colleague, then connect the response to the client’s stated need.

Avoid common answer problems:

Overclaiming: State what you know, what you will verify, and who will make the technical decision.
Defensiveness: Acknowledge a concern before explaining the response.
Jargon: Use plain language, then define a technical term if it matters.
Long monologues: Answer the point and stop.
Unclear ownership: Name the role responsible for the action.
Speculation: Do not guess about conditions, approvals, or unconfirmed commitments.

If you do not know, say so plainly. Explain how you would find the answer, what information is needed, and who would follow up. This demonstrates judgment and protects credibility. Licensed PE judgment and local codes govern engineering decisions.

Do not interrupt a panelist to finish a question or contradict a colleague in front of the panel. If a teammate needs clarification, add context respectfully and accurately. Agree on key facts and commitments before arriving, while still speaking naturally.

Watch the panel’s cues without overinterpreting them. A follow-up may signal interest or a need for clarification. Ask whether the answer addressed the concern if the discussion permits. Give the panel room to speak; do not fill every pause with another claim.

Make materials accessible and easy to use

Follow the client’s instructions first. If slides are permitted, prepare a small, readable deck that supports the conversation. It should help the panel understand the team, relevant experience, project approach, and communication plan, not reproduce the entire proposal.

Use plain headings, descriptive labels, and legible text. Avoid dense paragraphs, small type, weak color contrast, and diagrams that need lengthy explanation. Do not rely on color alone to distinguish items. Label lines and categories directly where practical.

Make digital files accessible. Use meaningful slide titles, logical reading order, alternative text for informative images, and descriptive link text. Check that the file opens on the client’s likely platform and that fonts and tables remain readable. Check diagrams separately. If providing a PDF, confirm text is selectable and pages display correctly.

Use visuals only when they clarify the work. A simple project map, team responsibility chart, decision flow, or phase diagram may help. Decorative stock images usually add little. Identify the source and date of project imagery or data when that context matters.

Prepare a print version only if allowed and useful. Bring enough copies for the panel, with a clear cover and page numbers. Do not hand out unapproved material, leave confidential information visible, or introduce new qualifications absent from the submission if the solicitation prohibits additions.

Have a technology backup plan. Bring the approved file in the requested format and follow the venue’s connection instructions. If the display fails, continue without blaming the client or losing the substance of the discussion. Assign one person to manage slides so speakers can focus on the panel.

Rehearse the actual interview

Rehearsal should test clarity, timing, coordination, and judgment. It is not a contest to memorize a script. Use the actual attendees, planned room or video setup, and allotted time. If the client has a question period, leave room for it.

Run through the presentation once for structure, then again with interruptions and questions. Ask a colleague who was not involved in preparing the proposal to act as a panelist. Have them probe the approach, staffing, relevant experience, schedule assumptions, and risks. They can also ask how your firm differs from competitors. The purpose is to find unclear answers before the client does.

Record the rehearsal if the team is comfortable. Review whether speakers answer directly, use understandable language, and give one another room. Check posture, pace, audibility, screen sharing, and transitions. Remove material that repeats another speaker or uses time without adding evidence.

Practice difficult questions, including:

What is the main project risk, and what would you do first?
Which proposed team member will be available during critical phases?
How will you manage a scope or schedule change?
What information do you need from the client?
What experience is closest to this assignment?
What would you do if initial data conflict with field conditions?
How will the client know when a decision is needed?

Agree on facts that must remain consistent: names and roles, project examples, availability, and assumptions. Also agree on commitments. Give speakers room to phrase answers in their own words. If an answer depends on a technical determination, practice explaining the decision process without pretending the result is already known.

End rehearsal with a practical check. Confirm arrival or connection time, attendee names, room access, equipment, file version, contact person, and procedure for submitting required materials. Assign a lead for logistics and a backup for the presentation file.

Follow up and keep a clean record

After the interview, follow the client’s communication rules. If a thank-you or clarification is permitted, send a concise note through the approved channel. Thank the panel, reinforce one specific point tied to the project, and provide only information the client invited or allowed. Do not use follow-up to add an unsolicited second presentation or pressure the selection team.

If you promised an answer, deliver it promptly and accurately. Identify the question, provide the verified response, and name any limitation. When a technical answer needs confirmation, say what has been checked and what remains subject to project data, client direction, or licensed PE judgment.

Record the interview while details are fresh. Keep notes factual and internal. Capture questions asked, themes emphasized by the panel, commitments made, follow-up items, and lessons for future selections. Distinguish direct statements from interpretation. Store the record with proposal and interview materials according to firm document practices and procurement requirements.

Review the effort with the team. Which answers connected client needs to real evidence? Where did the team talk too long or leave ownership unclear? Did the examples match the evaluation criteria? What should change in the criteria map, project sheets, or rehearsal plan next time? A short, candid review can improve the next pursuit without turning the interview into a blame exercise.

For supporting material, visit the CivilEngineers.com resources, guides, and checklists. Use the glossary for engineering and procurement terms.

General education only, not engineering, legal, tax or investment advice. Licensed PE judgment and local codes govern.