From AML Analyst to Full Stack Developer: My Pivot Story
In 2022, I was sitting in a compliance office in Accra, reviewing transaction reports for a telecom company. I was good at it — detail-oriented, methodical, comfortable with data. But I kept thinking about the dashboards I used every day and how much better they could be.
The Moment That Started It
There was a reporting tool we used that was genuinely painful. Slow, counterintuitive, designed by someone who'd never had to use it daily. I started sketching what a better version might look like in my notes app during lunch breaks.
That simple frustration — 'I could build something better' — was the spark. I'd always been curious about software, but that was the moment I decided to do something about it.
Learning While Working
I didn't quit my job and join a bootcamp. I couldn't afford to. Instead, I carved out time every evening. YouTube, freeCodeCamp, The Odin Project. I learned HTML first, then CSS, then JavaScript. It took months before anything I built looked decent.
What helped was building real things — not tutorial apps, but things I actually wanted to exist. A movie trailer tracker. A simple landing page for a friend's business. Projects that gave me a reason to push through the hard parts.
The First Real Job
Getting hired at Union Systems Global as a Frontend Developer felt surreal. I remember staring at the offer email for a few minutes before replying.
The first few months were humbling. Production codebases look nothing like tutorial code. I was working with React, Node.js, Oracle databases, and Java — technologies I'd barely touched. I asked a lot of questions and read a lot of pull request comments.
Slowly, it clicked. And with each shipped feature, I got faster.
What the Analyst Background Actually Gave Me
People sometimes assume a non-traditional background is a disadvantage. I've found the opposite. My time in AML compliance made me deeply comfortable with data, edge cases, and the question 'what could go wrong here?'
I approach code the way I approached compliance reports — looking for what doesn't add up, thinking about how someone might misuse a system, caring about the accuracy of what's displayed to the user.
That background also made me a better communicator. I learned to write clearly, explain technical concepts to non-technical stakeholders, and justify decisions with data.
If you're considering a pivot into development, my honest advice is this: don't wait until you feel ready. Start building something real. The skills compound quickly once you have something to work toward.