Back

From Quality Engineering to Product Management: A 10-Year Transition

4 MINS

# From Quality Engineering to Product Management: A 10-Year Transition

After 10 years in quality engineering and automation at firms like Publicis Sapient and Synechron, I made a deliberate choice to transition into product management. Here's what I learned about making this shift successfully.

Why Quality Engineers Make Great Product Managers

The skills that made me effective in quality engineering translate remarkably well to product management.

Systems thinking: Quality engineers see the entire system, not just individual components. We understand how changes in one area ripple through the entire product.

User empathy through edge cases: Years of thinking about what could go wrong gave me deep insight into user journeys. I naturally consider the unhappy paths that many PMs overlook.

Data-driven decision making: QA is inherently quantitative. We measure everything — defect rates, test coverage, regression trends. This analytical mindset is invaluable for product decisions.

Cross-functional collaboration: Quality touches every team — developers, designers, operations, support. Building relationships across functions is second nature.

The Gaps I Had to Fill

Technical expertise alone doesn't make a product manager. Here's what I invested in:

Business acumen: My ISB Product Management certification helped me understand market sizing, competitive analysis, and go-to-market strategy. Quality engineers often focus inward; PMs must look outward.

Strategic thinking: Moving from "how do we build this right?" to "should we build this at all?" required a fundamental mindset shift.

Stakeholder management: QA interactions are often binary — pass or fail. Product discussions involve tradeoffs, negotiations, and alignment across competing priorities.

Vision and storytelling: Quality metrics speak for themselves. Product vision requires narrative — inspiring teams and convincing stakeholders.

How I Made the Transition

The transition wasn't overnight. Here's the approach that worked:

1. Expanded scope in current role

I started taking on product-adjacent responsibilities writing requirements, participating in roadmap discussions, leading feature planning sessions.

2. Invested in formal education

The ISB Product Management certification and IIM Calcutta Fintech programme gave me structured knowledge and credibility.

3. Built a T-shaped profile

I doubled down on fintech domain expertise while broadening my general product skills. Specialization opened doors.

4. Leveraged my technical depth

In fintech, technical credibility matters. My automation background let me speak confidently with engineering teams and make informed technical tradeoffs.

Advice for Engineers Considering PM

If you're a quality engineer or developer considering product management:

Don't wait for permission — start acting like a PM in your current role
Invest in business education to complement your technical skills
Pick a domain and go deep — generalist PM roles are harder to break into
Your technical background is a feature, not a bug — own it The best product managers I know combine technical depth with business breadth and genuine user empathy. Quality engineering builds all three.
Background

Sambit skipped presentations and built real AI products.

Sambit Kumar Das was part of the January 2025 cohort at Curious PM, alongside 13 other talented participants.