Can a non-engineer enter IT consulting and shift to product management?
Non-engineers can enter IT consulting and shift to product management, and this path is more walkable than campus rumor suggests.
The catch
the timeline is real (3-5 years post-MBA), and the tech skill gap does not close by accident.
The Core Pathway
The standard route starts with an MBA at a new IIM or equivalent, followed by a campus placement into an IT consulting or strategy role. Entry-point employers from new IIM batches are typically Accenture Strategy, TCS Consulting, and Infosys Management Consulting, with joining packages in the ₹12-16 LPA range.
These roles give you client-facing delivery experience, which is the actual currency you need later.
After 1-3 years of building credibility on live projects, the move to product management becomes viable. Internal transfers exist but are competitive.
Lateral hiring is more common, with Amazon, Flipkart, Swiggy, and growth-stage startups being the most frequent destinations. PM roles at the 3-5 year experienced-hire level typically pay ₹25-40 LPA, and digital strategy roles at product companies (blending analytics, roadmap ownership, and go-to-market) can reach ₹30-45 LPA.
How the Non-Engineering Background Actually Plays Out
| Stage | Where it hurts | Where it helps |
|---|---|---|
| IT consulting entry | None, business skills valued equally | Stakeholder communication, deck quality |
| First 18 months on the job | Tech vocabulary, SQL fluency | Business case framing, client empathy |
| PM interview rounds | System design, tech intuition questions | Product strategy, user research rounds |
| PM role itself | Engineering team credibility early on | Business metrics ownership, prioritization |
The friction is real but front-loaded. Most non-engineers close the visible skill gap within the first two years if they actively work at it rather than waiting for osmosis.
What to Build Before and During the MBA
Start before day one of the MBA, not after
- Excel, Power BI, and Tableau basics before the program begins
- SQL during MBA electives or self-study; basic Python is a bonus, not a requirement
- Work through "Cracking the PM Interview" by Gayle McDowell as structured PM prep
- Take live product or analytics projects at startups during the MBA to build a portfolio you can point to
Non-Engineer-Specific Friction Points
Tech stakeholder conversations require active upskilling, not passive exposure. PM interviews, even for non-technical PM tracks at companies like Google or Razorpay, test product sense, data interpretation, and tech trade-off thinking.
The background does not disappear as a consideration; you just have to overinvest in proof points: a product teardown, a side project, or a published case study that signals technical seriousness.
The students who stall are the ones who treat the MBA as the finish line. This path has a second learning curve after graduation, and that second curve is steeper without an engineering foundation.
That is not a reason to avoid the path. It is a reason to plan for it explicitly.
Digital strategy roles, blending marketing, analytics, and roadmap ownership, are a parallel destination worth considering. They sit naturally for non-engineers with strong business acumen and tend to pay ₹30-45 LPA at the 3-5 year post-MBA mark, often with fewer gatekeeping hurdles than core PM roles.
Pro Tip: Before your PM interview loop, build one public product teardown (a Notion page or LinkedIn post analyzing a product's onboarding flow with metrics) so you have a concrete artifact to reference when interviewers ask for evidence of product thinking.