What a Client Expects in an Interview
Understanding what a client actually assesses in a presales or engagement-qualification interview — beyond technical skills.
Anticipating the 3 dimensions a client assesses
A client doesn't just assess your technical skills. They assess 3 dimensions at once: trust, competence and fit.
- ✓Anticipate the 3 dimensions a client assesses
- ✓Structure your answers to address what they're really looking for
- ✓Avoid mistake #1: talking about your skills in general rather than their specific problem
Trust, Competence, Fit
- ✓Listen before answering (don't interrupt)
- ✓Ask about their context before proposing solutions
- ✓Adapt your technical level to your audience (a CIO ≠ a developer)
- ✓Show that you understand their organisational constraints, not just the technical ones
Examples by seniority level
Client question: "Have you worked on projects with demanding performance constraints before?"
Answer: "Yes, in 2023 at an HR software vendor. Our REST API served 40 enterprise clients with peaks of 50,000 requests a minute. We had a 99.9% SLA. I personally designed the Redis caching system that cut response time from 800ms to 120ms. What interests me about your context is that you mention similar constraints on your payment API — are your load peaks predictable or random?"
What works: precise figures, a clear personal role, a pivot to the client's problem, a discovery question at the end.
Client question: "What are the main difficulties of a cloud migration in our sector?"
Answer: "In banking, the three constraints that consistently complicate a cloud migration are regulatory requirements (PCI-DSS, DORA since January 2025, NIS2), data-sovereignty management, and resistance from teams used to on-premise patterns. On the GCP migration I led for an institution with 1.2M customer accounts, I planned for all three from the scoping stage. What was underestimated, honestly, was training the internal teams — I dedicated 20% of the budget to it. How are you organised internally at the moment?"
What works: demonstrated regulatory expertise, honesty about what was underestimated, concrete figures, a question that invites them to share their context.
Common mistakes
- ✕Talking about your skills in general rather than showing how they apply to the client's specific problem
- ✕Using the collective "we" without specifying your personal contribution
- ✕Not researching the client before the interview — not knowing their sector, their news, their challenges
- ✕Answering the technical question without restating the business stakes behind it
- ✕Not asking questions — a consultant who asks no questions isn't trying to understand
- ✕Overstating your skills without grounding them in concrete achievements
- ✕Ignoring non-verbal signals — if the client checks their watch, wrap up and move to the next question
Quick checklist before a client interview
- ✓I've researched the company, its sector, its recent news
- ✓I know the regulatory issues in their sector
- ✓I've prepared 3 concrete, quantified examples suited to their context
- ✓I can frame my value in terms of problems solved (not generic skills)
- ✓I've prepared 3 relevant questions to ask
- ✓I can describe a limit of my experience without it hurting my credibility
Expert advice
What a client is really looking for
A client interview isn't a skills exam. It's a conversation where the client is trying to answer one question: "Can I trust this person to deliver in MY context?" Tailor every example. Show that you've understood THEIR problem. Ask questions that demonstrate genuine professional curiosity.
Want one-to-one support to prepare for your interviews?
An outside perspective to build your bank of examples and rehearse under real conditions.