5 answers
Asif
Student
1
Question
Updated
4049 views
Struggled with DSA as a Backend Developer — Considering a Switch to Data Analyst. Is This the Right Move?
I’ve been working as a backend web developer, and for the past year, I dedicated myself to learning Data Structures and Algorithms (DSA). Despite giving it my all, I couldn’t get a proper grasp of it — I genuinely struggled to understand the concepts.
To add some context, I’m from a BCA not a engineering background, so DSA has been particularly tough for me to crack. Still, I didn’t give up easily — I tried for a whole year, but it just didn’t click.
That said, I don’t want to stop growing in my career just because I failed at something. I’ve done some self-reflection and research, and I feel drawn toward the field of Data Analytics.
Before getting into backend development, I worked in operations, where I used to interact with clients, gather requirements, and pass them on to the tech team. So, I already have some exposure to data and communication. Combining that with my coding background, I believe I can bring value as a Data Analyst.
I know I failed with DSA, but I’m ready to give 100% again — this time in a field that aligns more with how I think and work.
Does this career switch make sense? Has anyone here gone through something similar? I’d really appreciate any advice or honest thoughts.
Login to comment
5 answers
Wyatt .
Retired Corporate Executive
54
Answers
United States
Updated
Wyatt’s Answer
Hi Asif,
I bring over 25 years of experience in the technology industry, having progressed from engineer to corporate executive while leading multiple departments.
It’s completely valid to reconsider your career path when something isn’t aligning with your strengths or interests, and in your case, switching from backend development to data analytics makes a lot of sense. Your experience reflects a strong work ethic you spent a year trying to master DSA, which shows determination. But it’s also important to recognize that not every technical role requires the same skill set. DSA is critical in certain areas like competitive programming or system design-heavy roles, but it’s not the only gateway to a successful tech career.
Your background in backend development, combined with prior experience in operations and client communication, actually gives you a strong foundation for a transition into data analytics. The field requires both technical ability like SQL, Python, and data visualization and a clear understanding of business goals, which you already have from your operations role. This hybrid of technical and business understanding is highly valuable in analytics roles.
Struggling with DSA doesn’t mean you’re not capable in tech it just means your strengths may lie elsewhere. Many professionals pivot successfully within the tech industry to find roles that better suit their mindset and skills. As long as you’re willing to commit to learning analytics tools and concepts (like Excel, Tableau, Power BI, or basic statistics), the switch is not only feasible but potentially a great move.
In my humble opinion, yes this career switch makes sense. It’s not a failure, but a strategic shift based on self-awareness and a desire to grow in a direction that suits you better. You’re not alone in facing such challenges, and many have found success by doing exactly what you’re considering. Keep moving forward.
PS: Make sure you are engaged in AI tools around data analytics!! This will set you apart with those not embracing these important tools.
Best Wishes,
Wyatt
I bring over 25 years of experience in the technology industry, having progressed from engineer to corporate executive while leading multiple departments.
It’s completely valid to reconsider your career path when something isn’t aligning with your strengths or interests, and in your case, switching from backend development to data analytics makes a lot of sense. Your experience reflects a strong work ethic you spent a year trying to master DSA, which shows determination. But it’s also important to recognize that not every technical role requires the same skill set. DSA is critical in certain areas like competitive programming or system design-heavy roles, but it’s not the only gateway to a successful tech career.
Your background in backend development, combined with prior experience in operations and client communication, actually gives you a strong foundation for a transition into data analytics. The field requires both technical ability like SQL, Python, and data visualization and a clear understanding of business goals, which you already have from your operations role. This hybrid of technical and business understanding is highly valuable in analytics roles.
Struggling with DSA doesn’t mean you’re not capable in tech it just means your strengths may lie elsewhere. Many professionals pivot successfully within the tech industry to find roles that better suit their mindset and skills. As long as you’re willing to commit to learning analytics tools and concepts (like Excel, Tableau, Power BI, or basic statistics), the switch is not only feasible but potentially a great move.
In my humble opinion, yes this career switch makes sense. It’s not a failure, but a strategic shift based on self-awareness and a desire to grow in a direction that suits you better. You’re not alone in facing such challenges, and many have found success by doing exactly what you’re considering. Keep moving forward.
PS: Make sure you are engaged in AI tools around data analytics!! This will set you apart with those not embracing these important tools.
Best Wishes,
Wyatt
Thank you, Wyatt for the advice.
Christopher Carpenter
3
Answers
Updated
Christopher’s Answer
From the sound of your experiences, you have the capability to understand DSA.
When I've seen people struggle with a topic that is within their grasp, it is often due to their introduction and/or the perception of the topic. If you want to tackle the topic again, I'd recommend starting simple and practical.
For example, no one implements linked lists themselves, but for learning it's great due to how simple it is.
The learning gathered in the simpler topics will help provide the foundation to understand theore complicated topics.
TLDR - crawl, walk, run
When I've seen people struggle with a topic that is within their grasp, it is often due to their introduction and/or the perception of the topic. If you want to tackle the topic again, I'd recommend starting simple and practical.
For example, no one implements linked lists themselves, but for learning it's great due to how simple it is.
The learning gathered in the simpler topics will help provide the foundation to understand theore complicated topics.
TLDR - crawl, walk, run
Ashutosh Raina
Software Developer
13
Answers
Campbell, California
Updated
Ashutosh’s Answer
You have some great options ahead of you! Taking an online course from platforms like Coursera can help you learn DSA at your own pace. Remember, practicing problem-solving is key, and it might take some time and focus. If you can team up with a study buddy, it can make the journey more enjoyable and effective.
If you're interested in a different path, consider roles like business analyst, technical program manager, or program management. These positions also require some experience, but starting in an entry-level role can open doors for growth and learning. Having a basic understanding of development will definitely help you stand out in these fields.
Good luck on your journey! You’ve got this!
If you're interested in a different path, consider roles like business analyst, technical program manager, or program management. These positions also require some experience, but starting in an entry-level role can open doors for growth and learning. Having a basic understanding of development will definitely help you stand out in these fields.
Good luck on your journey! You’ve got this!
Chinyere Okafor
Educationist and Counseling Psychologist
1205
Answers
Port Harcourt, Rivers, Nigeria
Updated
Chinyere’s Answer
Hi Asif,
I want to start by saying thank you for sharing your experience so openly. It takes bravery to be open about difficulties, and much more bravery to keep going. It speaks highly of your dedication and work ethic that you committed to trying to master DSA for a whole year even though you found it challenging.
Actually, your experience with backend operations and development provides a strong basis for your move into data analytics. Many data analyst jobs are more concerned with dealing with data, analyzing trends, and sharing findings than they are with having in-depth knowledge of DSA. You already demonstrate that you have good analytical thinking and communication abilities, which are necessary for a data analyst, from your prior work with information gathering and your exposure to business processes.
Additionally, it makes sense that you are thinking about a position that aligns with your natural way of thinking and working. Not everyone is wired for algorithmic problem-solving to the degree needed for positions involving a lot of DSA or competitive programming. It only indicates that your talents might be in a different area, and data analytics might be that area. That doesn't mean you're less capable.
You can try the following for going forward with this switch:
- Get hands-on with data: Learn SQL, Excel/Google Sheets, and a data visualization tool like Tableau or Power BI.
- Pick up Python for data analysis: With your coding background, learning libraries like Pandas and Matplotlib will likely feel familiar.
- Build a portfolio: Start small with personal projects or datasets from Kaggle. Try analyzing something relevant to your background — like operations or web performance metrics — to show your unique perspective.
- Certifications: Consider beginner-friendly certificates like Google Data Analytics or IBM Data Analyst (available on Coursera). They’re well structured and add credibility.
Last but not least, a lot of professionals have made the successful shift from various tech positions, such as backend programming, to data analytics. Your path is completely valid, and you're acting thoughtfully and not out of fear. That's a wise and responsible job choice. Therefore, this switch makes perfect sense. Keep on; your past experiences serve as the basis for your future move rather than a diversion.
Best wishes!
I want to start by saying thank you for sharing your experience so openly. It takes bravery to be open about difficulties, and much more bravery to keep going. It speaks highly of your dedication and work ethic that you committed to trying to master DSA for a whole year even though you found it challenging.
Actually, your experience with backend operations and development provides a strong basis for your move into data analytics. Many data analyst jobs are more concerned with dealing with data, analyzing trends, and sharing findings than they are with having in-depth knowledge of DSA. You already demonstrate that you have good analytical thinking and communication abilities, which are necessary for a data analyst, from your prior work with information gathering and your exposure to business processes.
Additionally, it makes sense that you are thinking about a position that aligns with your natural way of thinking and working. Not everyone is wired for algorithmic problem-solving to the degree needed for positions involving a lot of DSA or competitive programming. It only indicates that your talents might be in a different area, and data analytics might be that area. That doesn't mean you're less capable.
You can try the following for going forward with this switch:
- Get hands-on with data: Learn SQL, Excel/Google Sheets, and a data visualization tool like Tableau or Power BI.
- Pick up Python for data analysis: With your coding background, learning libraries like Pandas and Matplotlib will likely feel familiar.
- Build a portfolio: Start small with personal projects or datasets from Kaggle. Try analyzing something relevant to your background — like operations or web performance metrics — to show your unique perspective.
- Certifications: Consider beginner-friendly certificates like Google Data Analytics or IBM Data Analyst (available on Coursera). They’re well structured and add credibility.
Last but not least, a lot of professionals have made the successful shift from various tech positions, such as backend programming, to data analytics. Your path is completely valid, and you're acting thoughtfully and not out of fear. That's a wise and responsible job choice. Therefore, this switch makes perfect sense. Keep on; your past experiences serve as the basis for your future move rather than a diversion.
Best wishes!
James Constantine Frangos
SOFTWARE ENGINEER SINCE 1972; NUTRITIONIST SINCE 1976.
7094
Answers
Gold Coast, Queensland, Australia
Updated
James Constantine’s Answer
Good Day Asif!
You have just reached a 'sticking point' in DSA [Data Structures and Algorithms]. The 'sticking point' is a routine problem experienced by weightlifters who train by 'pressing iron' - lifting heavy weights to gain physical strength. I had the equivalent trying to learn SQL [Structured Query Language] in Microsoft Visual Basic 4.0 in 1996.
I struggled for months trying to access databases of various sorts. My code seemed correct, and it seemed to be set out correctly on the tiny laptop. I had bought reference books because the Internet was something new to Australia at that time. What has happened with your DSA is that you have missed some essential information; the 'pin has not dropped yet'.
With me, the problem was that I needed to follow protocol in my setting out of code. SQL is a specialized beast! It was the way I was setting out my statements to get information out of a database field
♪ ♬ "You'll Never Get To Harvard If You Don't Eat Well" ♫ ♪ - Dionne Warwick?
You have just reached a 'sticking point' in DSA [Data Structures and Algorithms]. The 'sticking point' is a routine problem experienced by weightlifters who train by 'pressing iron' - lifting heavy weights to gain physical strength. I had the equivalent trying to learn SQL [Structured Query Language] in Microsoft Visual Basic 4.0 in 1996.
I struggled for months trying to access databases of various sorts. My code seemed correct, and it seemed to be set out correctly on the tiny laptop. I had bought reference books because the Internet was something new to Australia at that time. What has happened with your DSA is that you have missed some essential information; the 'pin has not dropped yet'.
With me, the problem was that I needed to follow protocol in my setting out of code. SQL is a specialized beast! It was the way I was setting out my statements to get information out of a database field
♪ ♬ "You'll Never Get To Harvard If You Don't Eat Well" ♫ ♪ - Dionne Warwick?