From Finance to Tech: My Journey to Securing a Software Engineer Role at JPMorgan

by ripple1953
JPMorgan
junior
Prep: 4 months
13
54

Coming from a finance background, the transition to tech felt daunting. I spent years in a world of numbers, spreadsheets, and financial modeling. But after some soul-searching, I decided I wanted to shift gears into software engineering. The decision was not easy, but it felt right.

I dedicated four months to prepare myself for this career switch. I dove headfirst into coding, immersing myself in languages like Python and Java. Online courses, tutorials, and coding boot camps became my daily companions. I put in about 20 hours a week, wrestling with algorithms on platforms like LeetCode and working through coding challenges every evening after my day job.

The interview process was intense and full of surprises. I faced a total of three technical rounds along with a behavioral interview. The technical problems weren't just about coding—they often involved data structure optimizations and real-world scenario applications, which caught me off guard. In one round, I confidently explained how to reverse a linked list, but when it came to implementing it in code, I completely blanked. My heart raced as I recognized that I wasn’t articulating my thought process well, and it felt like I was stumbling.

Despite the setback, I learned from that moment. I reached out to my network to practice mock interviews, gaining confidence with each session. I tailored my preparation based on feedback, focusing on not just solving problems, but communicating my reasoning clearly. This was a game changer. The mock interviews provided a reality check, and I felt like I was making progress.

Going into the final rounds, I felt a mix of excitement and anxiety. The interviewers challenged me with system design questions that felt like they were galaxies away from my earlier finance days. But I took a deep breath and relied on the structured approaches I had studied. I surprised myself with how well I navigated discussions about scalability and architecture. It felt good to showcase what I had learned.

Finally, I received the phone call offering me the role at JPMorgan as a junior software engineer. The relief was overwhelming, but so was the feeling of pride. I had conquered that steep learning curve. My passion for tech had transformed from a curiosity into a sustainable career opportunity. It was a journey filled with stress, moments of self-doubt, and the occasional imposter syndrome, but ultimately, it was a huge leap of faith.

As I prepare to start this new chapter, I'm both nervous and excited. Reflecting on this journey, I can't help but feel grateful for the lessons learned, the support from friends, and the unwavering belief that switching careers was worth it. I’m now on my way to make a mark in tech, and if I could do it, maybe others in similar boats can find their path too.


Tips

Dedicate specific hours each week purely for study and practice., Engage in mock interviews with peers or through platforms like Pramp., Focus on explaining your thought process out loud during coding to improve communication skills., Use a variety of resources to avoid burnout with one style of learning., Don't be afraid to reach out for help from your network; mentorship can make a difference.


Markdown supported