The Hardest Part of Changing Careers Wasn't Learning SQL

When people talk about changing careers into data, the conversation usually focuses on technical skills.

SQL.

Power BI.

Python.

Building projects.

Collecting certifications.

For a long time, I thought the same.

I assumed that if I learned enough, practised enough, and built a strong enough portfolio, the rest would eventually fall into place.

Looking back, I think I got that part wrong.

Because learning the tools was never the hardest part.

The hardest part has been something much less obvious.

It has been learning how to bridge the gap between valuable experience and recognised experience.

Over the past decade, I have worked with customers, targets, performance metrics, regulations, and business decisions.

I have worked in banking.

I have run my own business.

I have been a teacher, explaining complex ideas in ways that people could actually understand.

None of those roles had the title "Data Analyst".

Yet many of the skills I use today were built long before I opened Power BI or wrote my first SQL query.

Recently, I received feedback after an interview for an analyst role.

The feedback was positive.

The hiring team highlighted my understanding of compliance, my approach to gathering and analysing information, and my overall performance during the interview.

What surprised me most was not what they said.

It was what they didn't say.

Nobody questioned my ability to communicate.

Nobody questioned my analytical thinking.

Nobody questioned the fact that English is not my first language.

To be honest, those were some of the things I worried about most.

I moved to a different country.

I changed careers.

I was convinced that language, communication style, or cultural differences might be the biggest challenge.

In the end, they weren't.

The challenge was something else entirely.

The candidates who progressed had more direct experience within that specific industry.

And honestly, I understand that decision.

If I were hiring for a highly specialised role, I would probably value direct industry experience too.

What stayed with me afterwards was a different question.

How do you gain recognised experience when the lack of recognised experience is often the reason you are overlooked?

At times, it can feel like a difficult gap to bridge.

You can have years of professional experience.

You can have qualifications.

You can run a business.

You can learn new skills and continuously invest in your development.

And still find yourself feeling as though you are not quite enough because you do not fit perfectly into a predefined box.

I know people who have spent years in roles they dislike, doing the bare minimum and counting down the hours until the end of the day.

I also know people who are curious, hardworking, proactive, and constantly learning.

Yet sometimes it feels as though the first group is easier for the market to understand.

Not because they are better.

But because they are easier to categorise.

Their experience fits neatly into an expected pattern.

This isn't a complaint about the job market.

If anything, it's an observation.

Changing careers has taught me that learning new skills and getting those skills recognised are two very different challenges.

One can be measured through courses, certifications, and projects.

The other takes much longer.

It requires people to look beyond a job title and recognise the value of experience that may have been gained somewhere else.

Looking back, SQL was probably one of the easier parts of this journey.

The harder part has been learning how to connect who I already was with who I want to become.

And perhaps that's the real challenge of changing careers.