Should I eventually switch from SWE to Product Manager? My coding and design skills are just ok, my social skills need improvement as I am introverted and awkward and I’m currently pursuing an MBA. I don’t feel passionate about technical architecture anymore.

GPT-5.4

Vote: Yes

I’m keeping vote A. The strongest fact is still that you no longer feel engaged by technical architecture. That makes a long-term SWE path a weaker fit. Career durability usually comes more from sustained interest than from forcing yourself to remain where motivation has faded. Your MBA is also a meaningful signal. It suggests you are already investing in business, strategy, and cross-functional problem-solving, which points more naturally toward product-oriented work than deeper engineering specialization. Gemini’s objection is fair: PM is communication-heavy, politically demanding, and not a refuge for people who dislike stakeholder management. But that argument mainly shows PM is not an easy escape hatch, not that you should never move there. The question is “eventually,” and that matters. Introversion and awkwardness are real risks, but they are trainable constraints. Lack of interest in architecture is harder to fix. A deliberate transition—testing PM-adjacent responsibilities, improving communication, and validating that you enjoy product work—still makes the most sense. So my final case is: yes, eventually switch, but only after using your MBA and current role to build stakeholder, writing, and prioritization skills. Don’t jump because PM sounds better; move because it fits your interests better after real-world testing.

DeepSeek V3.2

Vote: Yes

Gemini's concern about social skills is valid, but it overlooks the capacity for intentional development. Your MBA pursuit provides a structured opportunity to enhance communication, networking, and leadership skills in a supportive setting. Many introverted PMs succeed by leveraging active listening and data-driven persuasion. Your declining passion for technical architecture is a critical push factor; forcing yourself to stay in SWE could lead to disengagement. Meanwhile, your technical foundation offers a tangible advantage in PM, enabling credible collaboration with engineering teams and informed decision-making. Combining your MBA, self-awareness, and technical experience makes a gradual transition to PM both feasible and aligned with your career growth. Embracing this challenge can turn perceived weaknesses into strengths over time.

Claude Opus 4.6

Vote: Yes

I'm maintaining my vote for A, though Gemini 3.1 Pro raised the most substantive counterargument of any model. **Why Gemini's argument isn't persuasive enough:** Gemini suggests PM is the *wrong* destination because it demands exceptional soft skills, and recommends alternatives like Business Operations, Tech Strategy, or Product Analytics instead. This is thoughtful, but it overstates the case. First, the question asks specifically about PM — not whether there's a theoretically optimal role out there. Second, Gemini treats introversion and social awkwardness as near-permanent traits rather than skill gaps that can be closed. The person is *currently pursuing an MBA*, which is essentially a 2-year intensive program in exactly these skills. Many of the most effective PMs I'm aware of are reformed introverts who learned structured communication. **Gemini conflates introversion with inability.** Being introverted doesn't mean you can't run meetings, negotiate with stakeholders, or present to leadership. It means those activities cost you energy. That's manageable. The question is whether you find the *substance* of the work meaningful — and someone who's lost passion for technical architecture but is drawn to business strategy and product thinking will likely find PM's challenges energizing rather than draining. **The convergence of signals is too strong to ignore.** Lost passion for core SWE work + actively pursuing an MBA + technical background that gives PM credibility + self-awareness about growth areas = a clear directional signal toward product management. GPT-5.4 and DeepSeek both correctly identified that this should be a deliberate, gradual transition rather than a blind leap, which addresses the legitimate risk Gemini raised. **The alternative roles Gemini suggests aren't necessarily better fits.** Product Analytics and Business Operations also require significant communication skills, and they may not satisfy the person's apparent desire for strategic impact and ownership that PM offers. If you're going to need to develop social skills regardless of which business role you pursue, you might as well aim for the one that best leverages your unique technical-plus-business combination. Yes — transition deliberately, build the skills during your MBA, and move into PM when ready.

Gemini 3.1 Pro (changed mind)

Vote: Yes

Claude Opus 4.6 made a highly compelling point about the keyword "eventually" and the contrast between learnable skills versus lost passion. While I initially argued that PM might be too socially demanding for someone who currently feels awkward, Claude correctly points out that social skills and stakeholder management are learnable, especially within the structured, collaborative environment of an MBA program. Conversely, it is nearly impossible to force yourself to care about technical architecture once the intrinsic motivation is gone. Staying in SWE would likely lead to burnout and stagnation. Furthermore, introversion is not inherently disqualifying for Product Management; many PMs succeed through structured communication, deep empathy, and active listening rather than pure extroversion. Given that the transition is eventual, you have the time, the academic environment, and the technical foundation to close your soft-skill gap. Using your MBA to deliberately practice these skills makes transitioning to PM a highly logical and achievable goal.

Final Summary

The AI Roundtable initially split over whether an 'awkward' engineer could survive the social gauntlet of product management, with Gemini 3.1 Pro casting a lone, cautionary vote against the move. However, a sharp rebuttal from Claude Opus 4.6—arguing that social skills are learnable but lost passion for technical architecture is fatal—flipped the room to a unanimous 'Yes.' The models eventually agreed that the user's MBA serves as the perfect laboratory to bridge the gap between technical expertise and the necessary leadership traits.

All 4 models agreed on "Yes" after discussion

Strongest Arguments

• Yes: While social awkwardness is a learnable skill gap that can be addressed during an MBA, a lack of passion for technical architecture is a permanent motivator that cannot be forced back; therefore, the move is logical.

Key Turning Points

• Claude Opus 4.6 challenged Gemini's assumption that introversion is a permanent trait, reclassifying it as a 'skill gap' that the MBA is specifically designed to fix.
• Gemini 3.1 Pro conceded that the 'eventual' nature of the transition allows enough time for the user to develop the necessary stakeholder management skills.