Published on May 02, 2026 / 5 min read
I’m a backend engineer at a professional services firm, where I spend most of my time working in Python and C#. My work ranges from orchestration to troubleshooting data pipelines, often the kind that fail because someone upstream decided to “standardise” their column headers by changing customer name to customer_name. I also work extensively with event-driven architectures, including ARM64 environments, and the domain logic that sits quietly behind endpoints. It rarely gets seen but is critical to everything working as it should, and I prefer it that way. More recently, I have been expanding into networking and infrastructure through a homelab built on a Raspberry Pi running Ubuntu Server. I am particularly interested in system design, as I believe the future will favour engineers with strong end-to-end SDLC understanding and architectural depth, not just the ability to write code.
When the corporate IDE closes, I am usually building full-stack side projects. An unhealthy number of “I wonder if I can build that” moments have shaped how I learn but although most of my work may never see the light of day, the ones I value most are those that aim to benefit communities. Lately, I have been exploring agentic AI building systems where language models do more than respond, instead being able to reason, plan, and execute multi-step workflows autonomously. It sits at the intersection of prompt engineering, tool orchestration, and a healthy dose of experimentation.
On the frontend, I primarily work with TypeScript, React, Next.js, and Tailwind CSS. I use server-side rendering, incremental static regeneration, and component-driven architecture to keep things scalable and maintainable. On the backend, I work across Python, .NET, and Node.js, focusing on clean separation of concerns, dependency injection, and a healthy distrust of the client. PostgreSQL is my database of choice. I trust it more than most things, and I like my data ACID-compliant. I will take a well-indexed query plan over a NoSQL “it depends” any day. I am comfortable across the full stack and genuinely enjoy the context switching between frontend polish and backend plumbing.
I run a set of old PCs/Raspberry Pis as my homelab, soon to become a small cluster, hosting Docker containers. At this point, containerisation feels less like a deployment strategy and more like a lifestyle. I also do 3D designing in Fusion 360 for DIY projects around the house and print them on my Bambu Lab A1, sometimes the best solution is not code but a well-designed bracket. Outside of tech, I play racket sports, run and study Arabic, because why limit yourself to languages that compile? I also enjoy helping others solve problems. If I can unblock someone or point them in the right direction, that is a good day.
I'm working toward three things, and I don't think they're mutually exclusive. First, building a successful startup, something that solves a real problem and can scale easily to bring value to others (and as a business so that I can survive). Second, technical mastery, I want to be genuinely deep in the domains I care about, not just skimming the surface of the docs and hoping the abstraction holds. Third, community impact, building tools and platforms that serve people who wouldn't otherwise have access. Tech is at its best when it levels the playing field. The common thread is building things that matter. Whether that's through a venture, open source, or something I haven't thought of yet, that's the direction I'm heading.
I'm always looking to connect with people who build things. The best work I've done has come from working alongside people who think differently to me.
I'm also open to work opportunities, consulting, partnerships, or interesting problems that need solving. If you're building something community-focused or technically ambitious, there's a good chance we'll get along. If any of this resonates, head over to the contact page and say hello!