From Biochemistry to Data Platform Engineering: Choosing the Hard Path on Purpose

I didn’t start in tech.

My background is in Biochemistry and for a long time, I explored different directions trying to understand where I truly belonged.

After university, I also ventured into entrepreneurship, which gave me early exposure to building, problem-solving and working independently. But even then, I knew I was still searching for something more defined and more technical.

My entry into tech began with data analysis.

At that stage, I was simply trying to understand how data works, how it is structured, interpreted and used to make decisions. It felt like a good starting point, but I was also aware that I was still at the beginning of a much longer journey.

I later progressed into data science through WorldQuant University, where I deepened my understanding of analytical systems and statistical thinking. That phase gave me structure, but it also made something clear to me. I was not yet where I wanted to be in terms of depth and technical direction.

I started asking myself better questions.

Where does data actually come from?
What systems generate it?
What infrastructure makes large scale data possible in the first place?

Those questions shifted my focus completely.

I became less interested in just analyzing data and more interested in how data systems are built and sustained.

That curiosity eventually led me into Data Engineering.

At the time, I was also thinking carefully about long term direction. I did not just want to work in a field because it was popular. I wanted a space that required depth, where skill compounds over time, and where fundamentals still matter even as tools evolve.

And with AI everywhere now, that question became even more serious for me.

If AI is built on data, then I do not just want to use the tools. I want to understand and build the systems that make those tools possible. That is how Data Engineering started making sense.

But even within Data Engineering, I realized I wanted to go further than building pipelines and moving data. I wanted to understand how the entire system is designed, how data platforms are structured, how networks communicate, and how everything connects end to end. That shift pushed me toward data platform engineering and cloud infrastructure, where you are working with the full environment that data lives in, not just parts of it.

There is also a personal dimension to that decision.

I am a woman in a field that is still largely male dominated, but I have never seen that as a limitation. If anything, it has reinforced my mindset that I want to build where the work is hard, not where it is convenient. I have always been drawn to spaces that challenge me to grow into them.

I believe capability is not defined by gender, but by depth of understanding and consistency of effort.

As I continued building in this space, I began gaining visibility beyond my immediate environment.

I have also worked remotely with companies across different regions, including teams in China and Germany. These experiences exposed me to different engineering cultures and reinforced my understanding of how global tech systems are built and how deeply interconnected they are.

Each stage of my journey has reinforced one thing.

Tech is not just about learning tools. It is about exposure, consistency and the willingness to operate in complex systems without needing everything to be simplified first.

Today, I work in Data Platform Engineering, building and engaging with cloud based data systems where architecture, scalability, networking and reliability matter deeply.

Looking back, my path has not been linear, but it has been intentional.