I started my career where many engineers should start but often do not — at the database layer. My early years were spent designing and developing database systems using Oracle 10g, 11g, SQL Server, and other relational technologies. That foundation shaped how I think about software. I learned that performance, scalability, and reliability begin with data modeling. If the data layer is weak, everything above it eventually collapses.

Around 2010, I moved into application development using C# and the .NET ecosystem. I built desktop applications with WPF and Silverlight, and later web systems with ASP.NET and .NET Core. This period expanded my understanding of full system design — from database to user interface.

In 2012, I pursued a Diploma in Statistics at the Federal School of Statistics. That decision sharpened my analytical thinking. Statistics trained me to question assumptions, validate results, and approach problems with structure rather than guesswork.

After completing my diploma, I spent two years teaching computer science students at a college. Teaching was transformative. It forced me to simplify complex concepts, refine my thinking, and truly understand the fundamentals behind the code.

In 2015, I moved to India to pursue a BSc in Computer Applications at Bangalore University, completing the degree between 2015 and 2018.

While studying, and even after graduating, I worked with several companies as a software engineer. Those years were intense. I was learning formally during the day and building production systems in real environments. Some projects even required travel to places like the Maldives while I was still based in India. It was a period of rapid growth and exposure.

Before moving to India, I had already begun exploring Python. But around 2017, I made a deliberate decision to focus on it seriously. I immersed myself in backend development using Django, FastAPI, and modern API design principles. Python felt expressive and powerful. It allowed me to move quickly without sacrificing structure.

Between 2017 and 2019, I also worked as a contractor for a US based client on data analytics and machine learning projects. That experience combined my statistics background with engineering practice. I worked on real datasets, built analytical pipelines, and contributed to ML driven solutions. It strengthened my ability to build systems informed by data, not guesswork.

In 2019, I built a backend system singlehandedly for a real estate tech company based in Saudi Arabia using Laravel and MySQL. It became the backbone of their operations. After that engagement, I returned fully to Python and backend architecture, where I have focused ever since.

In 2022, I relocated to Dubai and joined an Insurtech company as a Senior Software Engineer. That was a defining chapter.

For three years, I worked on production systems at scale — building and refining backend services, improving architecture, and contributing to systems that supported significant business growth. These were not side projects. These were revenue generating systems handling thousands of users.

Later, I relocated to England and continued working with the same company in their London office. The transition reinforced something important about my career — my work travels well. Solid engineering principles translate across teams, regions, and industries.

In January 2026, I concluded that chapter, having contributed across multiple geographies and stages of growth.

Today, I specialize in backend engineering and system architecture using Python, particularly Django and FastAPI.

I build systems that:

• Scale reliably
• Support complex business workflows
• Integrate with external systems
• Ensure data security and compliance
• Scale with business growth

My background across databases, statistics, teaching, analytics, .NET, PHP, and Python gives me range. I understand systems from the storage layer up to the API surface. I do not just write endpoints. I design foundations.

I value clarity over cleverness. Structure over shortcuts. Engineering decisions backed by reasoning, not trends.

At my core, I am still that database engineer who believes everything begins with well designed data.

The difference now is scale, responsibility, and experience.

And I am just getting started.