Problem first, systems second
I am a senior product-focused backend engineer. I spend most of my time on the parts of products that need to stay reliable when traffic, data, or team size grows.
I have led and contributed to backend systems across fintech, HR, food delivery, EdTech, charity, and mobility, usually from early architecture through production. I care more about whether the system still holds six months later than whether it shipped on Friday.
When I lead, I stay hands-on. I would rather review a schema change than delegate it blindly. When I build, I think about the product constraint behind the ticket: who is blocked if this API is slow or wrong?
Experience
Technical Team LeadCurrent
HCMatrix
Technical Team Lead
Snapnet Limited
Tech Lead & Backend Architect
Zaakiyah
Backend Engineer
Snapnet Limited
Backend Engineer
Jekaeat
Fullstack Developer
234 Web Resources
Back to school
Student Intern
Edawah Technologies
How I approach work
Understand first
I start with the business problem and the constraints, not the stack. Clear architecture usually follows once you know what actually has to work.
Design for change
Requirements shift. I prefer systems that can evolve without a rewrite: clear boundaries, boring interfaces, and documented tradeoffs.
Own the outcome
Shipping is the baseline. After that I care about monitoring, failure modes, and whether the system holds under real load.
Working with me
- I ask a lot of questions upfront. Context saves rework later.
- I prefer written decisions for anything architectural.
- I will push back if a deadline conflicts with correctness on financial or user data.
- I am direct in reviews, but I care about the person behind the code.
Currently
Technical Team Lead at HCMatrix. Writing on Code Along. Mentoring through community programmes.
What people say
Reviews from colleagues and clients I have worked with, plus feedback from readers on my system design and backend writing.
Previous teams
“Thank you for your support. Capacity dey shout omo! I'm looking up to you boss. Thank you for all you do.”
From readers
“I love reading your articles. You've a way of explaining concept. Thank you for sharing.”
“Absolutely love this, thanks for sharing”
“Highlighting the potential pitfalls of an improperly set up API Gateway is crucial. It's more than just a proxy; it centralizes and streamlines microservice orchestration, enhancing security and efficiency. A must for scaling apps!”
What I work with
Tools from systems I have shipped or led: HR SaaS, fintech, food delivery, EdTech, and charity platforms. I pick what fits the problem over what is trending.
Languages & Runtimes
Frameworks & ORM
Data & cache
Messaging & real-time
Infrastructure & ops
Integrations