The coding class that changed everything
I never planned to work in tech. I studied journalism, expecting to become a journalist, until one unexpected class changed everything.
“So, what did you study in university?” a colleague asked me over coffee the other day.
“Journalism,” I replied with a small smile, already anticipating their reaction.
“Wait, but… you’re in tech now? How did that happen?”
I get this question all the time, and honestly, I love it. Because it takes me back to where it all started - the moment I realized I wanted a career change and how I took the leap into tech. It reminds me of the long journey that brought me to where I am today.
So, if you were sitting across from me right now, coffee in hand, and you just asked me how I got here, I’d probably laugh and then say to you:
“Funny enough, I never expected to be here either, but I’m so glad I am. It’s a bit of a long story but I’d love to talk about it”
So, let’s imagine we’re at that coffee shop together. Let me take you back to where it all started. And who knows? Maybe by the end of this conversation, you’ll see that you can do it too.
How did I realize I wanted a career change
When deciding what to study at university, I chose journalism, fully intending to become a journalist. Halfway through my degree, we had to take a required class called Coding for Storytelling as part of the curriculum. I remember thinking, Why would I ever need to learn how to code as a journalist? So, I was skeptical at first.
But then, I walked into that first class, completely unaware that it was about to change the trajectory of my career. It only took one session for me to fall in love with coding. I loved the problem-solving, the creativity and the feeling of turning an idea into something real. It was one of those lightbulb moments where I realized how cool coding was and how it could be a potential career for me. Up until then, I had never considered tech or coding as a possible career path. The truth is that it wasn’t something I had much exposure to, and I certainly didn’t see myself as someone who would be “good” at it.
Then, there was my professor, who later became my mentor. She was the one who saw potential in me and encouraged me to keep going. She pushed me to take more coding classes and get involved in the Interactives Desk of our student newsroom, where we used code to create interactive stories. Eventually, I became the editor of that desk in my senior year, helping others build stories with code. That was the real start of my journey into tech.
I wanted to keep learning, so I spent a summer at a coding bootcamp to sharpen my skills further. A few years later, I found myself landing my first job as a software engineer. I couldn’t believe it as I never thought I’d end up working in tech given my background and lack of a computer science degree. But it turns out, that didn’t matter. And so, I graduated with a degree in journalism but I never went back to it. Instead, I kept moving forward in tech.
And at this point, you might ask me: “Wait, so was it really that easy? You just took a bootcamp and landed a job?”
Not quite. On paper, my career change might look like a smooth transition. But in reality, there were plenty of ups and downs from imposter syndrome to rejections and self-doubt. I spent months questioning whether I was even qualified to apply for tech jobs. I held myself back, convinced companies would always choose someone with a CS degree over me. And even after landing my first role, the challenges didn’t stop. And that’s what I want to share next: the real picture of what it’s like to switch careers, the struggles I faced, and the wins that kept me going.
The struggles & wins of changing careers
The doubts: First, there was the guilt and disappointment of potentially not sticking to the career path I had originally set for myself. So, I decided to stick to it instead of switching to computer science, partly because I felt like I owed it to my past self to see it through. But also, because I found a way to merge the two - I was using code to tell stories, and that felt exciting. That felt like enough. But, the doubts remained. I remember thinking “Am I wasting my university years studying the wrong thing? Should I switch to a more technical degree?”. As humans, we want things to work out the way we imagined them. Leaving journalism behind felt like letting go of an old dream of mine and accepting that wasn’t easy.
Then came the actual learning curve - hours and hours of coding, debugging, and feeling like I was constantly behind. I was starting from scratch, and wasn’t sure if I could ever catch up to others with years of programming experience or education in their resume..
And of course, there was imposter syndrome. I didn’t have a computer science degree, just a short bootcamp under my belt. So, I convinced myself that companies would always choose someone else over me - someone with a traditional tech background and all the technical knowledge and skills needed in the industry. I remember seeing job postings requiring a CS degree and immediately assumed I wasn’t qualified. In the end, I didn’t apply. I didn’t apply to the jobs that felt “too technical” because I didn’t think I was “technical enough”. I was having so many intrusive thoughts:
Am I really capable of this? What if I’m just fooling myself?
Others are way more qualified — how can I possibly compete?
How do I expect to get hired if I don’t check all the boxes?
Maybe this isn’t worth it. Maybe I should just quit now.
That same mindset followed me into the technical interviews I had to go through. I thought I had to be the biggest expert in the room to succeed and always dreaded the moment someone would ask about my background. I was embarrassed and afraid to admit I had studied journalism, fearing they would question my abilities as a result. Fearing they’d see right through me, that I was just pretending to be someone I wasn’t, that I was an imposter.
My first role in tech was an internship at a data visualization company - honestly, the best scenario I could have imagined. It was a small startup at the time, filled with people who saw my background as a strength and engineers who mentored me, supported my growth, and made me feel like I belonged.
But it was only a three-month position. So, I kept applying. And applying. And applying. The saying “It only takes one” truly resonated with me during that time. For every 100 rejections I received, I had one company say yes to me. But that journey was brutal. Rejection after rejection only amplified my self-doubt, making me question whether I was ever going to make it in tech.
Eventually, that one opportunity did come. But even then, in my first few months, the self-doubt and lack of confidence only grew stronger. Everyone around me seemed smarter, more experienced, more technical and more deserving of their place in the team. Instead of recognizing my unique background as a strength, I saw it as a weakness and disadvantage. On top of that, I was the only woman on my software team. The representation I had back in university with my professor was gone. I lacked role models around me who looked like me, voices I could relate to, or stories that reflected my own journey.
The wins: But it wasn’t all doom and gloom. The wins were what kept me going. Completing my first coding project, making my first pull request, attending my first standup - each small milestone in my software career felt incredible. A year into my role, I was selected to work on a major UI redesign project, and not long after, I was promoted to mid-level software engineer. In only a few years, I went from not knowing a line of code to being a mid-level software engineer, and that in itself, is something to be proud of despite all the struggles.
But the biggest win of it all is the confidence I built in my skills. Over time, I realized that my weaknesses were in fact strengths, that what I learned during my journalism degree made me a stronger software engineer. I could communicate my ideas clearly, write great documentation, and think critically about storytelling in user experiences. That shift in mindset changed everything.
This is where you might say: “That’s incredible. But looking back now, is there anything you wish you had known before making the switch?”
Lessons from My Journey and Advice for Others
Yes. Definitely.
Transitioning into tech was a rollercoaster of highs and lows. I quickly realized it wasn’t just about learning to code; it was about overcoming doubt, navigating imposter syndrome, and reframing my background as a strength rather than a limitation. My path wasn’t linear, but along the way, I discovered key strategies that made all the difference. Over the years, I’ve come to understand that the biggest challenges aren’t about technical ability - they’re about mindset and confidence.
I didn’t fully grasp these lessons until I transitioned from being a software engineer to a tech educator. I went from navigating my own career shift to guiding others through theirs. It’s when I saw the transformation in my students firsthand and watched their confidence grow as they learned, especially women, that made me realize that my experiences weren’t just personal; they were universal.
That realization is what led me to write this post. For the past few years now, helping others succeed in their tech journeys has become my passion. It’s what drives me every day, and my hope is that this article does the same for you - give you the confidence to make the switch into tech. You’ve probably had thoughts like: Am I technical enough? Where do I even start? What if I fail? I know these thoughts well because I had them too. And so did almost everyone I’ve met in tech.
So, let’s talk about them. Here are some of the most common doubts that pop up when breaking into tech, and how to push past them:
“There’s SO much to learn. Where do I even start?”
I know and I get it. Even to this day, I still get overwhelmed by how much there is to learn. This is amplified by the fact that tech evolves rapidly and constantly, so there will always be something new to pick up. The key is to understand you don’t need to learn everything all at once.
Try this: Create a clear learning path to keep you focused and reduce the feeling of being lost. Whether you choose a bootcamp, online courses, or self-paced projects, having a roadmap gives you structure and direction.
How?
Break it down: focus on one skill at a time instead of trying to master everything at once. You want to get comfortable with the fundamentals first, and let them guide your next steps.
Track small wins: look back at the journey you’ve had so far and how much you’ve grown since day one. It could be useful to journal your wins and challenges along the way to be able to reflect back to where you started. I ask my students to do this all the time because it helps them remember how far they’ve come.
Ask for help: this is something I struggled to do early in my career because I felt like I was bothering people around me. But, that couldn’t be further from the truth. No one builds a career in tech alone, and leaning on people who can support you will be the secret to a successful career.
“I don’t feel technical enough to do this”
Tech isn’t just about coding speed or complexity; it’s about problem-solving, creativity, and communication. The industry needs diverse skills and perspectives, which means you belong here, regardless of your background.
Try this: Reframe your background as an asset.
How?
Think about your transferable skills: consider how your past experiences contribute to tech. For example, my background in journalism helped me in tech, as it made me a better communicator and collaborator than my peers. Whatever you’ve done before, chances are it brings something valuable to the table.
What you see as a weakness might actually be a strength: your unique perspective can bring valuable insights that others may lack. For example, if you’re a software engineer in a healthcare company and previously worked in healthcare, you know the real pain points, the inefficiencies, and the gaps that technology can fill in a way that someone without that background might not. And that is invaluable.
“What if I fail?”
Sorry to break it to you but you will fail, and that’s okay. Embracing failure is part of the process. If you never struggle, you’re probably not pushing yourself enough.
Try this: Reframe failure as feedback.
How?
Ask yourself the right questions
Instead of thinking “What if I fail?”, shift it to “What will I learn if this doesn’t work?”
Instead of thinking “I don’t belong here”, shift it to “I bring a unique perspective that adds value.”
Instead of thinking “I’m not technical enough”, shift it to “I have skills that others don’t, and I can always improve my technical knowledge”
Keep a “bug journal”, or a learning log to keep track of your mistakes and how you solved them. This can help you build confidence over time, reinforce your learning and see patterns.
“I don’t see people like me in tech”
Yup. Representation matters. Seeing educators and mentors that look like you in tech can be transformative because it reinforces the belief that you do belong here. So, if you’re not seeing people like you in tech, it’s natural to feel isolated.
Try this: Find or create a community where you feel seen and supported
How?
Join a group that reflects your experiences and interests: whether through meetups, LinkedIn, or Slack groups, engage with tech spaces where diverse voices are present. Over the years, I’ve been part of different organisations, and they’ve been the spaces I go back to when I’ve felt low about my abilities.
Find a support system: whether it’s a mentor, an online group, or even just a few friends on the same journey, surround yourself with people who can invest in your growth and learning. Having someone who’s had a similar path can help you see success for yourself. For me, that person was my coding professor in university. Just having her simply exist besides me showed me that I could do it too. And, I have seen this firsthand in my own classes - when students see someone who looks like them thriving in tech, it shifts their mindset and reinforces that they do belong.
If you can’t find a space for yourself, create it: if it doesn’t exist, chances are others are looking for it too. Creating that space can empower not just you, but others who need it as well. Be the change you want to see.
“I don’t feel ready yet.”
Whether it’s sharing your work or applying for jobs, waiting until you feel “ready” can hold you back. The truth is, no one ever feels 100% prepared. Even the best engineers google things daily, continue to refactor their code constantly, and sometimes will push code with errors. No one’s work is perfect and no one knows everything.
Try this: Start sharing your work (applying) before you feel ready
How?
Post your progress, no matter how small: write about what you learned today, share a messy project, or even post a question on LinkedIn. Being open about your journey shows vulnerability and authenticity, which encourages others to do the same. You’ll not only connect with people with similar struggles, but also attract those who can support, guide and help you grow.
Engage with the tech community: people love helping beginners because they’ve been there too.
Apply to jobs before you feel 100% qualified: if you meet 60–70% of the requirements, go for it. Many companies hire for potential, not just for existing skills. When I applied for my first tech role, I only met about 60% of the job description, but I still got the job. And it meant that I learned so much on the job. Applying to a job shouldn’t be a tick-boxing exercise.
Shift your mindset: instead of saying, I don’t have experience with X, try I’m excited to learn X, and here’s how I’ve tackled similar challenges before. Or I don’t have experience with X but I have experience with Y, which could bring better value
Accept that it’s okay not to know everything: even experienced engineers are constantly learning. Most employees will look for someone who is hungry and curious to learn, not someone who already knows everything. And, let’s be honest - everyone can agree being a know-it all is boring.
So, what’s the takeaway?
At this point, you’re probably overloaded with everything I’ve just thrown at you. You look at me, with eyes saying, “Alright, Sarah… let’s wrap this up.”
And you’d be right.
But here’s what I want to end our conversation with:
The best engineers I’ve come across in my life, whether as a software engineer myself or as an educator, share a few key qualities. They’re the ones who take initiatives, communicate effectively, bring creativity to the table and think outside of the box. They’re the ones who are curious to learn, unafraid to fail, and just as willing to follow as they are to lead. They’re the ones that can be vulnerable and authentic about their own struggles, and in doing so, they empower those around them.
I’ve seen firsthand how someone with almost no confidence can transform into someone who believes they can do anything. I was that person and I taught those people. And that transformation wasn’t about being the most technically skilled person in the room - it was about being the most open, curious, confident, and eager to learn.