Firms that sell delivery capacity and advisory work to clients, where the interview is partly technical assessment and partly a rehearsal of how you will sound in front of the client paying for you. Use this guide to map the interview rounds, scoring signals, common traps, and high-yield questions for consulting, system integrator, SI roles.
Breadth beats depth here, because a consultant is staffed against whatever the account needs next quarter and the panel is measuring how quickly you become useful on an unfamiliar codebase. The rounds that decide the outcome are usually the case study and the client-facing conversation: estimation, scoping, what you do when the requirement is ambiguous, and how you say no to a client without losing the account. Presales and solutioning questions appear even for delivery roles at senior levels, since anyone leading a workstream eventually writes part of a proposal.
Treat it as a process gap, not a grudge. Find out where and when decisions are made, get your team's constraints in front of the deciders before the meeting through short written proposals with a comment window both time zones can reach, and escalate a specific costly decision, not the people who made it.
Describe your use of AI tools by task, each with its check: reading cited lines, running code, confirming APIs against the docs for your version. Refuse any answer you cannot check cheaply or that is costly to get wrong, keep restricted data out of unapproved tools, and back it with one real catch.
Choose a work sample with real decisions in it that you still understand line by line and are allowed to share. Be ready to admit which parts were other people's or a tool's, what is wrong with it, and what you would change, because the interviewer can open any file and ask why it is there.
Yes, once and briefly, with an assumption attached. In a hypothetical product exercise the scored move is what follows. Separate gaps that change the design from gaps that do not, choose assumptions that keep the problem hard, write them where both of you can see them, and say which parts of the design depend on each.
Treat the backlog as inventory with a carrying cost, delete rather than archive the items nobody will ever order, and derive how deep to refine from the team's measured throughput instead of refining everything. Refinement that clarifies nothing is usually missing a decision, not a better format.
Work out whether there is no project, a project owned by somebody else, or a champion nobody internally listens to, because each has a different next move. Then make one specific ask that requires other people, and treat a refusal as the qualification answer. It also connects multi threading to the point an interviewer is testing.
Do not dispute the claim; ask what it includes. Most unmatchable claims are matchable claims with a different scope or a hidden assumption underneath them, so decompose it against your own basis, concede honestly where the competitor is genuinely better, and make sure the customer knows what question to ask them.
A bare yes is a contractual representation you cannot support and a bare no scores zero, so the answer is a qualified compliance marking with the explanation carried where the evaluators will read it. Use the clarification window before you are forced to choose.