WHAT TO CHOOSE ?
Hi everyone,
I recently received an offer from Infosys for a Technical Support role. While I'm happy to have the opportunity, I'm feeling confused about my long-term career path.
Many people have told me that if I start my career in a non-development or non-technical role like Technical Support, it will be difficult to switch to software development or other technical IT roles later.
I have a few questions:
Is Technical Support at Infosys a good role to start my career?
If I work in this role for 1–2 years, will I still be able to switch to a software development or other technical role, either within Infosys or in another company?
If switching to a technical role is difficult, would pursuing an MBA after 1–2 years of work experience be a better option?
From a long-term career perspective, what would you recommend? Should I accept this role, prepare for a technical switch, or plan for an MBA?
I would really appreciate advice from people who have worked at Infosys or have gone through a similar career path.
Thank you in advance for your guidance!
10 answers
Michelle’s Answer
Michelle recommends the following next steps:
Diego’s Answer
Here's the honest part: Technical Support won't lock you out of development, but it also won't hand it to you. What determines your path isn't the title on your offer letter, it's what you choose to do with your evenings and weekends while you're in it. I've seen people go from support into engineering in under two years, because they kept building, kept learning, and made noise about wanting to move. I've also seen people stay in support for a decade because they got comfortable and stopped pushing.
So don't overthink "support vs. dev vs. MBA" as three separate lanes you have to pick right now. Take the job, and treat it as data. You'll learn how the company actually works, what the technical teams value, where the internal transfer doors are, none of which you can see from outside. That's not a detour, that's information you don't have yet and can't get any other way.
The MBA question can wait. It's a much better decision after you've actually worked and know what you're solving for, not before.
My honest recommendation: accept the role, keep building your technical skills on the side, and revisit the "should I switch" question in 6–12 months with real experience instead of secondhand opinions. You'll be a very different, much more informed person by then.
Every decision you make in life opens new paths you probably haven't even imagined yet.
Going out there, connecting with people, will build a network for you, connections are probably our most valuable asset professionally.
Omowunmi’s Answer
On the contrary, it will give you the needed breadth within the filed, as your support function will broadly serve different areas in the IT. It will also enable you test various areas in IT vis a vis your key interests, giving you a clear lead and answers to the ultimate space where you perfectly fit into in IT. I will not recommend an MBA immediately, rather, i will recommend a masters programme or certification in the area of specialty you have developed a passion /interest especially while working as a technical support at Infosys. Your MBA programme can be achieved when you are at mid management level to develop your leadership and strategic skills. All the best!
Matias’s Answer
As a UX Principal, I want to share a perspective that isn't often discussed: Starting in Technical Support can be a great foundation for your career if you use it wisely.
Here's how you can make the most of this role:
1. Is Technical Support a good place to start your career?
Yes, definitely. It gives you a close look at how real users interact with software, where systems might fail, and what frustrates them. This experience builds strong user empathy, a valuable skill for software engineers, product managers, and UX designers. You'll also learn about IT infrastructure, troubleshooting, and corporate environments. Plus, it gets you into a major tech company where you can grow your network and learn how businesses work.
2. Can you move to Software Development after 1–2 years?
Yes, you can, but it takes effort. It won't happen automatically, but it's possible both at Infosys and elsewhere:
Internal Mobility: Companies like Infosys often have internal job postings or upskilling programs. If you do well and connect with development teams, moving internally is common.
Stay Hands-On: Keep coding on the side while in support. Work on small projects, automate tasks, and maintain a GitHub portfolio.
My Recommendation for Your Next Steps:
Accept the role: Work experience is always better than a gap, especially now.
Use it as a learning lab: Learn about user issues, system architecture, and teamwork.
Build your network: Connect with developers and leaders. Share your goal of moving into development—people love to help!
Keep learning: Spend time each week improving your software engineering skills to be ready for new opportunities.
Don't see this role as a limit—see it as your stepping stone. You've got this!
Caroline’s Answer
Omowunmi’s Answer
On the contrary, it will give you the needed breadth within the filed, as your support function will broadly serve different areas in the IT. It will also enable you test various areas in IT vis a vis your key interests, giving you a clear lead and answers to the ultimate space where you perfectly fit into in IT. I will not recommend an MBA immediately, rather, i will recommend a masters programme or certification in the area of specialty you have developed a passion /interest especially while working as a technical support at Infosys. Your MBA programme can be achieved when you are at mid management level to develop your leadership and strategic skills. All the best.
sarvestha’s Answer
You're absolutely right! The world is changing so quickly, and one of the biggest advantages we have today is that our skills are often transferable across industries. You're no longer limited to following just one career path.
If, at any point, you feel like going back to something you enjoyed or exploring a completely different direction, don't hesitate to do it. Every experience you gain adds to your skill set and helps you grow, even if it doesn't seem directly related at first.
At the end of the day, your career is your journey. Choose the path that excites you, keeps you curious, and brings you fulfillment. It's perfectly okay to change your mind, pivot, and try something new. The most important thing is to do what genuinely makes you happy.
Wishing you all the best—you've got this! 😊
TRAVIS’s Answer
Giorgia’s Answer
That said, I would not automatically consider Technical Support a non-technical role. The value of the experience will depend on the specific responsibilities, the technologies you will work with, and how much opportunity you have to troubleshoot complex problems, understand systems, and interact with customers.
In the past, I hired a UX designer who had previously worked in Technical Support at Apple. Her experience supporting real customers, understanding their problems, and helping them navigate technology contributed significantly to her success as a designer. Technical Support can help you develop strong problem-solving, communication, product knowledge, and customer empathy—skills that are valuable in many technical roles.
If the Infosys role gives you exposure to relevant technologies, I would seriously consider accepting it, especially if you do not currently have a stronger offer. At the same time, be intentional about your next step: continue developing your programming skills, work on technical projects, pursue relevant certifications if useful, and look for opportunities to move internally or externally after gaining experience.
I would not assume that you need an MBA after one or two years. An MBA is usually more helpful if you want to move toward business, management, consulting, product strategy, or leadership. It is not the most direct path into software development. Whether it makes sense depends heavily on your background and long-term goals.
My recommendation would be to evaluate the actual responsibilities of the Technical Support role rather than focusing only on the title. It can be a good starting point, but you should continue building the skills required for the career you ultimately want.