Consulting Delivery interview prep.
A delivery / engagement manager owns a client-facing engagement end-to-end: take it from sales handoff through scope + plan + team + execute + monitor + escalate + go-live + close + follow-on sales.
What interviewers look for
- Can the candidate run a full delivery lifecycle: scope → plan → execute → monitor → close with discipline?
- Do they manage scope + change rigorously: change control process at kickoff + documented impact + client-decision-with-tradeoffs - not silent absorbing?
- Can they handle a client escalation with composure: own + investigate + propose corrective plan + rebuild trust + protect the follow-on?
- Are they risk-disciplined: identify + log + mitigate risk + escalate at the right time - not surprised when it materialises?
- Do they lead the team well: multi-discipline coordination (functional + technical + change + testing + business), partner orchestration, motivation under pressure?
- Are they business-aware: margin, utilization, follow-on revenue - the project IS a business, not just delivery?
Behavioural questions to expect
Walk me through your CV.
What it tests: Story coherence + genuine fit for the delivery seat. Teams want evidence of progressively-scoped delivery work (analyst → consultant → manager), client-facing experience, and business + technical breadth.
Tell me about your most impactful engagement.
What it tests: Depth + ownership + client outcome. Tests whether the candidate frames engagement work as client problem → scope + approach → team + execution → measurable outcome.
Tell me about a weakness, a failure, or feedback you've received and worked on.
What it tests: Self-awareness + delivery discipline. Cross-role canonical. Delivery mistakes (silent scope absorption that killed margin, missed risk that became a crisis, escalation handled poorly that lost the follow-on) carry real $ + relationship cost.
Why consulting delivery - and why this firm vs strategy consulting, internal eng, or hyperscaler SA?
What it tests: Authentic fit for the client-facing + scope-managed + team-led + business-aware seat. Tests whether the candidate WANTS the delivery work (scope + execution + escalation + close) vs the advisory-only (strategy) or build-only (internal eng) alternatives.
Which delivery sub-specialty or vertical would you want to focus on, and why?
What it tests: Genuine fit + grasp of how delivery areas differ (cloud + data implementation / SaaS / custom dev / package; vertical: FS / HC / retail / mfg / public sector).
Why this firm?
What it tests: Whether the candidate has done the homework. Bar: firm-specific evidence from the offerings, engagements, verticals, delivery methodology, people - not generic 'great firm'.
How would you describe this firm's delivery practice + client approach in your own words?
What it tests: Whether the candidate has internalized HOW the firm wins + delivers - service offerings, vertical strength, partner ecosystem, delivery methodology.
How does an IT services firm actually create + capture value?
What it tests: Whether the candidate understands services-firm economics: scope + margin + utilization + follow-on revenue; T&M vs fixed-price vs managed-service trade-offs; client retention + expansion.
Technical concepts to master
Client engagement + delivery lifecycle
- Sales-to-delivery handoff
- Critical transition: sales promises + SOW + budget become delivery's plan + commitment; misalignment here cascades through the engagement.
- Discover + design + sign-off gates
- Requirements + design documented + signed off as a gate before build; protects scope + sets quality bar.
- Build + test + change control
- Execution phase; agile sprints or waterfall phases; change control process protects scope from creep through this phase.
- Hypercare + close + follow-on
- Hypercare = post-go-live stabilization period; close = formal engagement end with KT + handoff; follow-on = expansion engagement signed.
Scope + change + risk management
- Change control process
- Established at kickoff: any scope change requires formal request + impact analysis (timeline + budget + risk) + client decision + sign-off + plan update.
- Risk register + RAID
- Risks + Assumptions + Issues + Dependencies logged continuously; risks assessed (likelihood × impact); mitigations assigned + tracked.
- Status + escalation cadence
- Weekly status with RAG + key risks + asks; steering committee monthly for executive alignment; escalation criteria explicit (e.g. amber > 2 weeks → escalate).
- Margin + utilization discipline
- Engagement margin = revenue - cost / revenue; utilization = consultant billable hours / available hours; both are P&L levers.
Client relationship + escalation handling
- Stakeholder map + engagement
- Map of executive sponsor + steering committee + working-level stakeholders + influence + interest; engagement cadence + communication channel per stakeholder.
- Transparency + early surfacing
- Surface risks + issues + scope changes early - before they become crises. Honest, frequent communication builds trust.
- Escalation handling
- When senior client escalates: own within 24h, investigate root cause, propose corrective plan, re-commit personally, follow through.
- Follow-on protection + growth
- Quality delivery earns the next engagement; relationship + reference investments compound; account growth is a long-term outcome of multi-engagement quality.
Team + technical leadership + multi-discipline orchestration
- Multi-discipline team coordination
- Functional consultants + technical engineers + change management + testers + partner SMEs; each has its own work stream + leadership.
- Partner + vendor orchestration
- Hyperscaler + SaaS + tech-platform partners contribute SMEs + licenses + escalation paths; orchestration includes their joint accountability.
- Onshore / nearshore / offshore model
- Distributed delivery model: onshore client-facing + nearshore + offshore execution; time zones + handoffs + quality protocols matter.
- Team motivation + protection
- Pressure + deadlines + client demands wear on the team; the delivery lead protects + motivates + manages expectations both up + down.
Practical drills
- Walk me through an engagement you've delivered end-to-end - scope, plan, execution, key moments, outcome.
- Mid-engagement (10 weeks into a 16-week build), the client requests adding a new module that wasn't in scope. The client estimates it's small. Walk me through how you'd handle.
- A senior client executive is unhappy with deliverable quality and has escalated to your delivery lead, threatening to cancel the engagement. Walk me through your response.
Smart-question anchors
- Delivery practice + scope - the role's first engagement, expected scope at 6-12 months
- Methodology + standards - waterfall / agile / hybrid; the firm's signature delivery framework
- Vertical + offering - the verticals + offerings the role focuses on, growth bets
- Partner ecosystem - hyperscaler + SaaS partnerships + certifications + joint go-to-market
- Onshore / offshore + global delivery - the firm's global delivery model + how it integrates
Related roles
Sourced from
- MockQuestions, 33 IT Delivery Manager Interview Questions
- Teal. Technical Delivery Manager Interview Questions
- The Interview Guys. Accenture Interview Questions 2026
- Invensis. Delivery Manager Interview Questions 2026
- PMI + PMBOK delivery + risk management methodology
- Tech Interview Handbook + senior behavioral references
Ready to Generate Your Own Prep?
Drop your CV and a job description on the home page. A couple of minutes later you get a report with everything you need to land the job.