I may have stepped away from the dispensing counter, but I never stepped away from healthcare.
If someone had told me a few years ago that I would move from dispensing medications to building data solutions, I probably would not have believed them. My career started in pharmacy. Like many pharmacists, I spent my days reviewing prescriptions, dispensing medications, counselling patients, and making sure they received the best possible care. It was rewarding work. Every interaction had the potential to improve someone's life.
But as I worked with patients and medicines, I found myself becoming curious about something bigger. Beyond every prescription was a story. Beyond every pharmacy shelf was a pattern. Beyond every patient interaction was data waiting to be understood. I wanted to know what those numbers could tell us.
Curiosity is a strategic imperative
Seneca said that as long as you live, keep learning how to live. I have taken that seriously, not as a passive principle but as an active commitment. That curiosity about data did not stay as curiosity for long. It became a discipline.
I began learning Excel more deeply, then moved to SQL, then Python, then Power BI, then data engineering in full, completing my Global Diploma in Data Engineering at AltSchool Africa. Many evenings and weekends were spent studying, practising, and building projects while still working within healthcare. The more I learned, the more I realised that many healthcare challenges are not purely clinical problems. They are also data problems. Questions about medicine usage, treatment trends, patient behaviour, market performance, and access to care all require good data and meaningful analysis.
I became fascinated by the idea of using data to answer these questions and support better decisions. Not as a departure from healthcare, but as a deeper entry into it.
Pharmacy taught me how to understand healthcare. Data taught me how to understand healthcare at scale.
Every challenge became a stepping stone
Marcus Aurelius wrote that the impediment to action advances action. My transition proved this. There were periods of stalling, of feeling like the technical ceiling was too high, of wondering whether the investment of time was going to pay off. Each of those moments became the reason to push further, not the reason to stop.
Learning SQL felt immediately familiar. Define the condition, filter the population, return the result. It was the same logical pattern I had been using to review prescriptions for years. Python opened a different register entirely. Where SQL asks questions, Python builds systems. It handles the messy, real-world data that does not conform to clean schemas. That was where I began to think like an engineer, not just an analyst.
What kept me going was not confidence that I would succeed. It was conviction that the problem was worth solving.
What pharmacy actually gives you in data work
More than people expect, and in ways that cannot be easily replicated through technical training alone.
Clinical literacy matters enormously. When you work with pharmaceutical datasets, knowing what drug names, active constituents, ATC classifications, and dosage forms actually mean is not a small advantage. It is the difference between cleaning a dataset correctly and cleaning it in a way that looks right but introduces errors that a non-clinician would never catch.
Pharmacy also builds comfort with ambiguity. Drug names are inconsistent. The same molecule appears under different names in different facilities. You learn to navigate that calmly because in clinical practice, getting it wrong has consequences. That instinct carries directly into data work.
And pharmacy trains you to communicate. Every patient counselling session is practice in translating complex information into something a person can act on. In data work, that skill becomes the ability to explain findings to decision makers who are not technical. That is, in my experience, most of the people who actually need to act on data.
As a pharmacist, I helped patients one prescription at a time. Through data, I now contribute to decisions that touch thousands of pharmacies, healthcare providers, and ultimately far more patients than I could ever reach across a single dispensing counter.
An extension, not a departure
Today I work at the intersection of healthcare, technology, and data. I build pipelines, audit datasets, and develop analytical solutions that turn pharmaceutical data into something useful for the people who need to make decisions with it. The scale is different from a dispensing counter. But the mission is identical to the one I started with: making sure the right information reaches the right person at the right time.
Looking back, the journey from the dispensing counter to the data pipeline was not a departure from pharmacy. It was an extension of it. Guided by Stoic conviction, I will continue to grow, innovate, and deliver data-driven solutions that drive meaningful impact in healthcare.
If you are a clinician reading this and you find yourself curious about data, follow that curiosity with intention. The clinical intuition you carry is rarer than you think, and this field needs it more than it currently knows.