After 4 years as a software engineer at a FAANG company, I decided to make the jump to management consulting. Here’s how I navigated the transition to BCG.
Why I Left Tech for Consulting
- Wanted broader business exposure beyond engineering problems
- Interested in strategy, not just execution
- Craved variety — different industries, different challenges every few months
- Long-term career goal: operating role at a tech company, consulting as a bridge
The Application
Timing
Applied during BCG’s experienced hire cycle. Most MBB firms have dedicated tracks for non-MBA experienced hires with 3-5 years of work experience.
Positioning My Engineering Background
- Reframed technical projects as business impact stories
- Highlighted cross-functional leadership (worked with product, sales, marketing)
- Emphasized analytical rigor and problem-solving methodology
- Showed client-facing experience from internal stakeholder management
Interview Preparation
The Biggest Adjustment
Engineers think bottom-up (data → analysis → conclusion). Consultants think top-down (hypothesis → analysis → validation). I had to rewire my approach.
What Helped Most
- 40 practice cases with a structured partner
- 3 mock interviews with ex-BCG coaches
- Reading BCG publications to understand their frameworks
- Practicing verbal communication — engineers write code, consultants tell stories
The Outcome
Received a BCG offer as an Associate (post-MBA level). The engineering background was seen as a differentiator, especially for tech-focused cases.
Advice for Engineers Considering Consulting
- Start networking 6+ months before you want to apply
- Frame your experience in business terms, not technical jargon
- Practice top-down communication relentlessly
- Your analytical skills are your superpower — leverage them
- Be prepared to explain “why consulting?” convincingly