Why You're Not Winning After the Interview

If you're like most architecture, engineering, or design firms, you probably prepare for interviews believing you're trying to answer one question: Can we prove we're the most qualified team?

It's a reasonable assumption. After all, qualifications are what get you shortlisted in the first place.

But after years of helping A/E firms pursue work and hearing from the people responsible for selecting them, we’ve learned something interesting. By the time a client invites you to interview, they're trying to answer a different question entirely.

Most firm leaders and project managers walk into an interview trying to prove they're qualified. Clients walk into the interview trying to decide whether they can envision working alongside your team throughout the life of the project.

Recognizing that difference changes how firms should prepare for interviews. Instead of focusing solely on what they want to communicate, they need to consider what the client is still trying to understand.

Reading the room

During interviews, decision-makers aren’t searching for another project example or another list of credentials. They’re trying to understand what it feels like to work with your team. That includes something that's difficult to quantify but easy to recognize: chemistry.

•       Will you communicate clearly when priorities change?
•       Do you genuinely understand the project's goals, challenges, and stakeholders’ needs?
•       Will you collaborate well with the different project teams?
•       Will you respond thoughtfully when faced with difficult questions?
•       Can you be trusted when the project becomes more complicated than expected?
•       Will this be the team I can have difficult conversations with when challenges arise?
•       Am I going to look forward to working with this team?

These aren't questions about your past projects. They're questions about your future working relationship. The interview becomes one of the first opportunities for clients to experience how your team thinks, communicates, collaborates, and responds under pressure.

That's because the interview is less about validating your capabilities and more about beginning to build trust. And the interesting thing about trust is that clients rarely evaluate it directly; instead, they look for signs of it during conversations.

•       Does your team communicate well?
•       Do you understand their priorities and concerns?
•       Do the people in the room work well together?
•       Does your team know how to pivot when the conversation goes off script?

The interviews that end in selection are the ones where the conversation was engaging and moved beyond the presentation itself. In those moments, clients begin to answer the question that matters most: not whether you're qualified, but whether you're the team they trust to have beside them as the work unfolds.

HOw storytelling builds trust

So how do you help a client begin to trust you?

You help them understand how your team thinks, how you approach challenges, and how you'll show up when the path forward isn't straightforward.

That's why storytelling plays such an important role in business development today.

A well-told story reveals far more than the outcome of a project. It shows how your team helped a client navigate a difficult decision, align competing priorities, adapt when conditions changed, or move forward when there wasn't an obvious path ahead.

Imagine two firms responding to the same interview question: "How would your team approach a project like ours?"

One answers by sharing their technical approach, listing relevant projects, and years of similar experience.

The other passionately shares a story about a project where stakeholder priorities threatened to derail progress. Instead of focusing solely on the credentials, they tell a client-centric story that explains how the team navigated competing perspectives, adapted their approach, and helped the client move forward with confidence.

The first proves they have experience. The second gives the client confidence in how that experience will be applied.

That's why storytelling is much more than a presentation technique. It's a way to transform qualifications into confidence.

While technical information earns credibility, storytelling earns confidence.

A different way to think about interviews

Qualifications remain essential. They always will. Without them, you probably won't make the shortlist. But once you've earned the interview, the conversation needs to shift.

The goal is no longer to convince the client that you're capable of doing the work. It's to help them feel confident that you're the right team to navigate everything that comes with it.

Instead of asking, "How do we prove we're qualified?" ask, "How do we help the client envision working with us?"

Instead of repeating what you've done, show them how you think. Instead of treating the interview as a presentation, treat it as the beginning of a relationship.

Remember, qualifications may earn you the opportunity, but trust earns you the work.