The operator behind the systems.

Works on the unglamorous parts: migrations that can't lose a row, services that stay predictable under load, and making cost and failure observable. Currently Technical Manager at Idekavan, leading Dobare and the messaging backbone behind it.

I care most about the parts of a system users never see: that a migration can be rolled back at any step, that one slow dependency can't take everything down, that the cost of running something is visible to the people deciding what to build next.

Currently Technical Manager at Idekavan, leading Dobare — a multi-tenant loyalty SaaS — and the cross-product Go messaging service behind it. Before that: taught Django and FastAPI to ~120 bootcamp students across three cohorts at Maktab Sharif.

how I work

• Start from the constraint, not the technology. Migrations, reliability work, and cost reduction all start with "what breaks if we're wrong here."
• Prefer boring infrastructure. The interesting part of a dual-write migration isn't the cutover — it's keeping every step rollback-safe.
• Make spend and failure observable before optimising either. You can't cut what you can't see.

notes

• Technical Manager at Idekavan; lead a small backend team and design the SDLC.
• Promoted from intern to Backend Developer in three months; to Technical Manager after six months.
• Left a Computer-Engineering programme (Islamic Azad University) mid-way and kept building. Military service: completed.
• Based in Tehran, UTC+3:30.