I'm Mohammed Abdo. Most of my time sits in the messy middle where FinTech ambition meets regulatory pressure. As a software and systems architect, I do not stop at shipping code—I help teams make sharper architecture choices, build scalable platforms, and move compliance discussions forward with quiet confidence.
Mohammed Abdo
// Software architect & engineer · Maal Tech
One person behind this site—directly with you: public engineering notes on the blog, a roadmap for your learning path, and hands-on consulting when you need less guesswork and a foundation that still holds after launch.
From the field—straight to you
Where the experience formed
My experience didn't start in slide decks—it was forged under delivery pressure: distributed systems (including microservices), payment stacks, and automated investing platforms (robo-advisory). I've seen how fuzzy requirements sink programmes—and how supervisors expect hardened infrastructure, not promises.
Maal Tech today
Through Maal Tech I put that field experience to work for you: the blog is my engineering notebook in public, the roadmap is your guide, and my consulting is where we reduce guesswork in your programme—so financial systems do not fall apart after launch week.
$ catjournal.txt
journal.txt — field notes on regulated FinTech, architecture trade-offs, and what actually holds up in review.
How I work (you deal with me—not a faceless team)
Radical candor
I will be direct when proposed architecture is fragile, or when deferring technical debt will cost far more later. I sell you the sound path—not the easy story.
Engineering without excess
Measured bets: an MVP built with intent, hypotheses tested at clear checkpoints, and an architecture that can grow—without unjustified complexity.
In the trench with you
Not a consultant who drops a PDF and vanishes. I join planning, review architecture, and stay in the sharp technical conversations that steer the compass.
Depth on sensitive surfaces
Extra rigour where failures cluster: digital identity (IAM), payment integration, data protection, and designs that auditors and risk teams can actually inspect.
Technical angles I keep unpacking
Sandbox, licensing, and supervisory language
I can help your team translate regulatory expectations (for example Saudi Central Bank and CMA) into concrete product features and technical evidence from day one.
Distributed, security-minded architecture
Design grounded in ideas such as Zero Trust and hexagonal boundaries—systems that stay isolable, integrate cleanly with gateways and partners, and remain operable at scale.
Financial products in local context
Aligning product intent with Gulf market behaviour—from UX expectations to integration with domestic rails such as Mada, SARIE-style flows, and Sadad, where operational detail matters.
Want to go deeper?
Reach out for consulting, architecture reviews, or mentorship—or keep reading the blog.
Get in touch