Drag to rotate · Each skill you switch on adds a plank to the bridge — five planks and you're across
Which skills do you have?
Spreadsheet modelingFinancial models, scenario analysis
Stakeholder managementWorkshops, exec communication
Process mappingAs-is/to-be, SOPs, swimlanes
Basic SQL / PythonEven coursework counts
Domain depthFinance, ops, healthcare...
Where ex-consultants actually land
| Role | Why it fits | Gap to close |
|---|---|---|
| Product manager | Stakeholders, prioritization, decks that decide things | Shipping instinct; work with real eng teams |
| Solutions / sales engineer | Client fluency + demo skills | One product's tech stack, deeply |
| Data / analytics | Modeling rigor transfers directly | SQL fluency, one BI tool, stats refresher |
| Workflow automation | Process mapping is the core skill | APIs, an automation platform, light scripting |
| Founder / early ops | Generalist stamina, client instincts | Tolerance for building without a playbook |
Note what's not on the list: junior software engineer. It's possible, but it burns your seniority. The winning pivots monetize consulting skills instead of discarding them.
The 6-month plan
Months 1–2: Build proof
- Automate one real workflow end-to-end (e.g. a reporting pipeline: form → sheet → scheduled summary email).
- Learn SQL to the level of confident JOINs and window functions — 30 focused hours gets you there.
Months 3–4: Build in public
- Publish 2–3 case studies: "How I cut a 6-hour weekly process to 20 minutes." Concrete numbers beat certificates.
- Ship one small tool for your old industry — enterprise workflow pain you personally felt.
Months 5–6: Convert
- Target companies selling to consultants' clients — your domain knowledge is their moat.
- Frame every interview answer as: business problem → system you built → measured outcome.
The honest math of the pivot
Expect a possible 0–20% initial compensation dip moving from senior consulting to a first tech role — recovered typically within 1–2 promotion cycles because tech ladders compress faster. The asset you're buying: skills that compound (code, product judgment) instead of hours that reset every engagement. The biggest predictor of a successful pivot isn't credentials — it's having one shipped artifact you can demo in an interview.