Blessing Okeke is a data solutions architect and engineer with a background in Industrial Mathematics, where she developed a strong foundation in structured thinking and problem-solving. She now applies that foundation to building reliable data systems and translating complex data challenges into practical solutions.
As a Data & Analytics Engineer at a Big Four consulting firm, she designs and builds data solutions that help organisations move from scattered information to confident, insight-driven decisions. Beyond her consulting work, she is a committed data educator who has trained numerous professionals in data engineering and analytics. Whether building pipelines or teaching others how to think with data, her focus remains the same: making data understandable, useful and impactful.
What sparked my interest in data engineering?
Funny enough, data wasn’t the original plan. I studied Industrial Mathematics and had a clear path in mind: I was going to become an actuary. I enjoyed calculations; numbers felt calm and predictable, and I had already mapped out the journey: take two actuarial exams before graduation and continue from there.
However, curiosity led me in a different direction.
During my fourth-year internship at a data and analytics company, what started as simple exposure quickly turned into exploration. It was my first real encounter with the world of data, and I found myself drawn to it: the blend of logic, systems and real-world impact. Before then, I didn’t fully understand what the field involved, but once I stepped into it, something clicked. I remember thinking, “This is it.” And from that moment, I never looked back.
What was my “almost gave up” moment in data?
Interestingly, I never experienced a dramatic “this field isn’t for me” moment. However, there was a phase that truly tested my resolve: the period right after all the learning and preparation, when it was time to break into the job market. It felt like everyone was ahead, and it was easy to question whether breaking into the field was even possible.
What kept me disciplined when things got tough?
What kept me motivated was a combination of curiosity and community. The dynamic nature of the field meant there was always something new to learn (new ideas, tools, and better ways to solve problems), which made the journey continually exciting.
Equally important was the data community. From peers to mentors and individuals sharing knowledge online, the openness and support within the ecosystem played a significant role in sustaining my progress and growth.
There’s a saying that it takes a community to raise a child, and in many ways, I consider myself one of the many professionals shaped and supported by the data community.
Education and skills: what mattered more in my journey?
A combination of both theory and practice has been essential in my development, with a stronger emphasis on hands-on experience: approximately 70% practical and 30% theoretical. While formal education provided a solid foundation in logical and analytical thinking, true understanding came from building solutions and solving real-world problems.
Ultimately, problem-solving remains the most critical skill. Tools continue to evolve, but a strong grasp of fundamentals is indispensable at every stage.
How I stay relevant without burning out
The data and technology space moves incredibly fast. There’s always a new tool, platform or approach emerging, and if you try to keep up with everything, burnout is almost inevitable.
So I rely on curiosity rather than pressure to guide my learning. I focus on understanding new tools through fundamental concepts, learn at a steady pace, and prioritise what’s relevant. I also take breaks to reset. During one of my breaks, for example, I explored cinematography: an entirely different environment with new people, perspectives and a creative process. That experience helped me recharge mentally and return with renewed clarity and focus.
Data solutions architect and engineer, in plain English
I architect the solution and then engineer it.
In simple terms: solving problems using data. My role is to analyse problems, design efficient data flows and structures, and build the systems that enable reliable and scalable data solutions.
Standing out
Standing out, to me, simply means being truly good at what you do.
Tea or coffee, and what does it say about how I debug?
Tea. My debugging method is very tea-aligned: when the bug gets stubborn, I close everything, step away, maybe squeeze in a quick nap, then come back with fresh eyes. Nine times out of ten this strategy works like magic; I suddenly see the problem that was hiding in plain sight.
