How I think, build, and write.

I'm Jatto Abdul, a senior software engineer building backend, platform, product, and applied-AI systems.

My work sits in the messy middle where product ideas become real software: APIs, data flows, search and reporting workflows, integrations, caching, deployment, and the judgment calls that keep systems understandable as they grow.

I think in systems: boundaries, contracts, observability, blast radius, and the people who have to operate the thing after it ships. I care about communication as much as code because most technical problems get easier when the assumptions are visible.

That is also why I write and create. Writing, videos, and public notes help me turn real engineering work into clearer lessons: what I tried, what broke, what worked, and what I would do differently next time.

Operating style

• I write down assumptions before writing code. Most bugs are assumption bugs.
• I prefer boring, durable architecture and reach for novelty only when boring genuinely doesn’t fit.
• I instrument early. If I can’t see what the system is doing, I haven’t finished building it.
• I review my own PRs first. The fastest way to get useful feedback is to delete my own weak ideas before someone else has to.
• I explain the tradeoff, not just the decision. Good engineering is usually a record of what we chose, what we rejected, and why.
• I build in public where it makes sense. Thinking out loud helps me find the parts of an idea that don’t actually work.

Open to

Senior and staff-level engineering roles, advisory work with engineering-led teams, and collaborations around backend, platform, product, and applied-AI systems. I'm especially interested in teams that value clear thinking, durable software, and products that respect users.