I’m Not a Career Changer. Stop Calling Me One.

The framing that holds finance professionals back from building analytical skills — and the one that actually works.

Every time I mention that I’m a Chartered Accountant learning Python and building data analytics projects, someone tells me I’m brave for making such a big career change.

I’m not making a career change. That framing — well-meaning as it is — is part of the reason more finance professionals don’t build analytical skills. It makes the whole thing sound like starting over. Like walking away from everything you already know.

What I’m actually doing is the opposite.

Seven years of statutory audit gave me something that no data science bootcamp or analytics programme can replicate: I know what financial data looks like when it’s lying to you.

Not through code. Not through a model. Through the kind of accumulated pattern recognition that only comes from sitting across a table from management teams who are hoping you won’t look too carefully at a specific line item — and looking carefully anyway.

I know why certain transaction patterns appear at quarter end. I know what a related-party disclosure that’s technically correct but structurally misleading looks like. I know the difference between a timing difference and a structural problem, and I know it before I’ve written a single line of Python.

That knowledge is the most valuable thing in a financial data analytics workflow. And it doesn’t come from analytics. It comes from audit.

What Python gave me was not a new career. It was a faster, more scalable way to act on what I already knew.

When I detect anomalies in banking transaction data using Z-score analysis and IQR, I’m not doing something separate from my audit work. I’m doing the same thing my audit work always trained me to do — identifying what doesn’t belong — at a scale and speed that manual processes can’t match.

When I build a customer segmentation model and find that age has essentially zero correlation with loyalty, I’m applying the same scepticism about assumptions that audit demands. The tool is different. The instinct is identical.

The “career change” framing implies that your existing experience is a sunk cost you’re walking away from. But for finance professionals moving into analytics, the existing experience is the competitive advantage.

A data analyst who learned Python first and finance second can build a clean model. A finance professional who learned Python second can build a clean model and tell you which assumptions in it are likely to be wrong — and why — before it runs.

That combination is not common. It’s not taught in any single programme. It takes time in both worlds, and most people only spend time in one.

I’m not starting over. I’m finishing a sentence that took seven years to set up.

If you’re a finance professional sitting on years of domain knowledge and wondering whether it’s “too late” to build technical skills — it’s not. And the framing that it requires starting over is wrong.

The domain knowledge doesn’t become irrelevant when you add technical skills. It becomes the thing that makes the technical skills unusually valuable.

That’s the intersection I write about here: what happens when audit experience meets data analytics, and why the combination produces something that neither world produces alone.

If that’s useful to you, follow along. There’s more coming.