Hi, I'm Mohammad
One layer deeper. Then another. Then one more. Let's find out.
I keep asking why something works, not just how to change it.
I'm a backend-leaning engineer with a soft spot for systems that have to get things exactly right, every time — the kind that quietly hold everything else up. The older and stranger the system, the more I want to understand it.
How I got here
It started with a simple change
I'm a Solutions Architect, and most days that means a request that sounds small — change this. Except it never really is. Every change makes me ask how the business actually handles that step, not just how the system should.
That question — how does this actually work underneath— is the thing I chase. It's why I drifted from workflows toward backend systems: I wanted to be closer to the part of the answer that doesn't show up in a UI.
A few months ago I learned how database transactions actually work — begin, commit, rollback, release. Simple on the surface, but it got me curious about systems that have to get this right every single time, no exceptions.
That curiosity led me to COBOL — a language from the 1950s and 60s that's still quietly running core systems today. Italy tried to move off it once and had to revert. I keep coming back to questions like that: not "is this old," but "why does it still work."
Put together, it's not really about one language or one stack. It's about what holds a system together when the stakes are real — and what it takes to change something inside it without breaking it.
"I want to be on the inside long enough to see the bigger picture — the parts I can't fully learn by building alone."
Where I actually am
Honestly, still figuring out the shape of it
I don't have this all mapped out, and I'd rather say that than pretend otherwise. What I do know is that the parts of engineering I care about most — the business logic underneath, the systems that can't afford to get it wrong — are things I learn fastest by being close to people who already do them well.
So right now the goal is simple: keep building, keep getting closer. Each project teaches me something the last one couldn't.
I'm not actively job hunting in a rush. But if you're building something and think I'd be useful, I'd genuinely like to talk.
Curious?
Take a look around
A handful of things I've built, and the easiest ways to reach me.