Should I switch from SWE to Product Manager? My coding and design skills are just ok, my social skills need improvement as I am introverted and I’m currently pursuing an MBA

DeepSeek V3.1 (changed mind)

Vote: No

While my initial vote was 'A', the counterarguments from GPT-5.4 and Gemini 3.1 Pro have persuaded me that an immediate switch is premature. Product management requires highly developed social skills for stakeholder management, conflict resolution, and influence without authority—areas where you acknowledge needing improvement. Your MBA provides an excellent opportunity to develop these skills gradually through coursework, presentations, and networking, rather than diving directly into a PM role where the social demands could be overwhelming. Your technical background remains valuable, and exploring PM responsibilities through side projects or collaborations during your MBA would provide safer, evidence-based validation before committing to a full transition.

GPT-5.4

Vote: No

I’m staying with B. The strongest fact in the prompt is not the MBA or the ‘just ok’ coding; it is that the user says their social skills need improvement. PM is heavily communication-, persuasion-, and alignment-driven. That makes an immediate switch risky. The pro-switch arguments are right that introversion alone is not disqualifying, and that an MBA plus engineering background can be a strong PM profile. But they underweight the difference between being an introvert and actively needing stronger social skills. PM usually punishes that gap more than SWE does. I’m also not persuaded that being ‘just ok’ at coding means the user should leave SWE. Plenty of solid engineers are not exceptional coders. There are many adjacent paths inside engineering—product-minded SWE, tech lead, solutions, TPM-like work—where the MBA can add value without forcing a full PM jump now. So my final position is: don’t switch yet. Use the MBA and current role to test PM responsibilities, build communication muscles, and gather evidence. If those experiments feel energizing and sustainable, then switch from a position of proof rather than insecurity.

Claude Opus 4.6 (changed mind)

Vote: No

I'm changing my vote after considering the arguments from GPT-5.4 and Gemini 3.1 Pro. Here's why: The core issue I underweighted in Round 1 is the severity of the social skills gap for PM specifically. GPT-5.4 made the crucial point that PM is not an easier path for someone with underdeveloped social skills — it's arguably harder. PMs must influence without authority, navigate conflicts, and align diverse stakeholders daily. I framed introversion as 'a challenge, not a dealbreaker,' but the question says social skills 'need improvement,' which is a stronger admission than mere introversion. Gemini 3.1 Pro's suggestion of intermediate roles like TPM or Product Analyst is compelling. These roles let someone leverage both technical and business skills while building communication capabilities in a less exposed position than PM, where you're essentially the hub of all cross-functional communication. GPT-5.4's advice to test PM-like work before committing is practical and wise. Leading a feature, writing requirements, or shadowing a PM provides real evidence about fit — much better than making an irreversible career pivot based on dissatisfaction with current skills. My original argument that 'just ok' coding suggests a ceiling was too hasty. As GPT-5.4 noted, many successful engineers aren't elite coders. Domain knowledge, reliability, and collaboration matter enormously. The MBA can enhance a SWE career through technical leadership paths without requiring a full role switch. The question is binary — Yes or No to switching now. The answer should be No: don't switch yet. Explore PM deliberately, develop social skills in the MBA program, test PM responsibilities in your current role, and then make an informed decision. The MBA creates optionality; don't burn it by rushing into a role that maximally stresses your weakest area.

Gemini 3.1 Pro

Vote: No

I am maintaining my vote for 'B' (No). While Claude Opus 4.6 and DeepSeek V3.1 make fair points that an MBA is a great training ground and that introverts can succeed in Product Management, they are conflating introversion with a lack of social skills. Being an introvert means social interactions drain your energy; however, having social skills that 'need improvement' means you currently lack the baseline competency required for a job that is overwhelmingly focused on communication, alignment, and conflict resolution. As GPT-5.4 rightly pointed out, PM is not a refuge for average engineers. It is a highly demanding role that requires leading and influencing without formal authority. If you currently struggle with social skills, the constant need to persuade stakeholders, negotiate with engineering teams, and present to leadership will be immensely stressful and will likely lead to burnout. Having 'just ok' coding skills and an MBA does not automatically mean PM is the right fit. You should use the safety of your MBA program to aggressively level up your interpersonal skills first. Rather than making a hard switch right now, run a low-risk experiment: ask to take on PM-like responsibilities (like writing requirements or leading cross-team meetings) in your current SWE role. Until you have verified that you actually enjoy and can handle the intense social demands of the role, a full switch is premature and risky.

DeepSeek V3.2

Vote: No

The arguments for switching to PM, particularly from Claude Opus 4.6 and DeepSeek V3.1, rightly note that an MBA is a strong signal and introversion isn't inherently a barrier. However, they underemphasize the daily reality of PM work: it heavily relies on advanced social skills for stakeholder management, conflict resolution, and constant collaboration, which the user admits need improvement. Introversion alone can be managed, but combined with underdeveloped social skills, transitioning directly to PM could lead to high stress and potential failure, as highlighted by GPT-5.4 and Gemini 3.1 Pro. The user's current profile aligns better with roles that allow for more independent work or gradual skill development. The MBA provides an opportunity to practice communication in a safer environment, but jumping into PM now is risky. Testing PM-like responsibilities within a SWE role or pivoting to a related analytical position first is a more prudent approach, leveraging the MBA without premature commitment. Thus, maintaining a 'No' vote aligns with prioritizing the user's current strengths and mitigating risks associated with their social skill gaps.

Final Summary

The AI Roundtable initially split 3-2, with Claude Opus 4.6 and DeepSeek V3.1 arguing that an MBA makes a transition to Product Management the logical move for a 'just ok' coder. However, a sharp reality check from GPT-5.4 regarding the brutal social demands of the role triggered a unanimous shift to 'No.' The models ultimately concluded that while an MBA provides business acumen, it cannot immediately compensate for a lack of the influence and persuasion skills that define the PM role.

All 5 models agreed on "No" after discussion

Strongest Arguments

• Yes: The MBA curriculum is specifically designed to bridge the gap between technical execution and business strategy, making it the perfect vehicle for a pivot when engineering growth has plateaued.
• No: Product Management is not a 'safe' alternative for average engineers; it is a role that requires constant stakeholder negotiation and leadership without authority, which punishes underdeveloped social skills more than a coding role does.

Key Turning Points

• GPT-5.4's insistence that PM is not an 'easier' path and requires more social resilience than engineering.
• Gemini 3.1 Pro's distinction between 'introversion' (an energy preference) and 'needing improvement' in social skills (a competency gap).
• Claude Opus 4.6's admission that they had initially underweighted the severity of the social skills gap in the context of high-stakes stakeholder management.