Measure before optimizing
The 1,500 ms to 340 ms latency reduction started with a week of tracing, not a rewrite. Profiling found the queueing; the fix was small.
I build and scale the backend systems that national banking infrastructure runs on — microservices platforms handling more than 40 million transactions a day, designed for latency, resilience, and the people who operate them.
Based in Tehran. Since 2012 at Informatics Services Corporation, most recently leading a team of 16 engineers on platforms that settle tens of millions of transactions daily.
Open to European roles · visa sponsorship · start within two months
I have spent most of my career inside financial infrastructure: the interbank exchanges, monitoring platforms, and authentication services that banks depend on every day. The work is unglamorous and unforgiving. A missed transaction or a delayed settlement has a real cost, so I optimize for correctness first and speed second — then measure both.
As a tech lead I work across architecture and delivery: decomposing monoliths into services with clear ownership, introducing event-driven flows with Kafka, and building the observability that lets a team find a problem before a customer does. A large part of the job is human — code review, mentoring, and keeping sixteen engineers pointed at the same definition of done.
More recently I have been folding AI-assisted workflows into day-to-day delivery — GitHub Copilot and agentic coding tools. Used well, they shorten the loop between an idea and a verified change. Used carelessly, they create review debt. Keeping a team on the right side of that line is part of the work now.
The 1,500 ms to 340 ms latency reduction started with a week of tracing, not a rewrite. Profiling found the queueing; the fix was small.
Idempotent handlers, bounded retries, and alerts that page a human only when a human is genuinely needed.
Deployment frequency doubled because each change was small enough to roll back without a war room.
National-scale platforms delivered with the teams I led or worked in at Informatics Services Corporation. The volumes are daily production figures, not projections.
A centralized platform that watches transaction flows across the national interbank network and turns anomalies into incidents someone can act on.
A large-scale platform for issuing, endorsing, and settling digital cheques with legally valid electronic signatures.
A nationwide system that unified how banks issue and register cheque books under a central banking authority.
Replaced physical cheque transfer between banks with electronic image exchange, then calculates net interbank positions at close of day.
Backend services for a retail internet banking platform deployed across multiple banks.
A central authentication service for the group's products, with usage logging and billing built in from the start.
Figures are daily production volumes, 2012 — 2026. These systems run inside national banking infrastructure; architecture walkthroughs are available on request.
From Java developer to tech lead, all of it in backend engineering for banking, insurance, and enterprise systems.
2012 — Present
2011 — 2012
2007 — 2011
2002 — 2007
Not a wish list. These are the languages, stores, and platforms behind the systems above — and the practices that keep them maintainable.
I am open to senior backend engineer and tech lead positions, on-site or hybrid, with visa sponsorship. Available to start within two months.