Architecture that survives reality
Clean boundaries, explicit domain models, and pragmatic trade-offs for systems that must remain understandable after the launch.
DDDClean ArchitectureMicroservices
Tech Lead · Software Architect · Senior .NET Engineer
I architect the systems behind the transaction.
For more than nineteen years, I have turned complex financial and enterprise requirements into dependable software—then helped engineering teams make that quality repeatable.
M A Sadeghi .NET Developer / 01
Current focusReliable
platforms.NET · SQL
19 yearsof
engineered trust
Scroll to explore
Tehran · 35.6892° N
19+Years engineering software
5Companies across Iran & UAE
10+Recent ASP.NET Core products
B2English proficiency
01
Profile
Technology becomes valuable when complexity feels simple, reliability feels ordinary, and a team understands why the system is shaped the way it is.
I am a software architect and technical leader specializing in Microsoft technologies, enterprise platforms, and banking automation. My career spans transaction systems, ATM operations, web products, back-office tools, and the modernization of long-lived business software.
My approach combines domain knowledge with engineering rigor. I use Domain-Driven Design to clarify the problem, Clean Architecture to protect the core, and test-driven practices to make change safer. Just as importantly, I create the conversations and feedback loops that let developers grow into owners.
M
Mahmoud Ali SadeghiBorn 1982 · English B2
02 / Expertise
Engineering depth, with a leader's perspective.
I work from business capability to production behavior: shaping boundaries, delivery standards, and the operational qualities a platform needs to earn trust.
Banking-grade reliability
Deep experience with ISO 8583, ATM estates, transaction switching, device integration, and the operational discipline behind secure financial software.
ISO 8583NDCATM Operations
Teams that ship with confidence
Architecture ownership paired with mentoring, design reviews, TDD, and stakeholder alignment—so quality becomes a team capability.
Tech LeadershipTDDMentoring
03 / Experience
A career built around consequential systems.
From banking automation to current product architecture, each role has deepened the same craft: making critical software clearer, safer, and easier to evolve.
Tehran, Iran2026 — Present
TajanSystem
Tech Lead & Software Architect
Leading architecture decisions, delivery practices, and engineering alignment for business-critical software.
- Own architectural direction and translate business objectives into resilient technical roadmaps.
- Raise engineering quality through design reviews, coding standards, mentoring, and practical delivery guardrails.
- Align product stakeholders and developers around clear system boundaries, non-functional requirements, and incremental modernization.
.NETASP.NET CoreDDDSQL
ServerTDD
04 / Selected systems
Products, platforms, and operational software.
My portfolio sits where software meets consequential real-world behavior: financial messages, distributed devices, enterprise workflows, and teams responsible for keeping them dependable.
01Banking
infrastructure
Host Simulator Engine
A configurable engine and web control panel for simulating transaction hosts, testing ISO messaging scenarios, and shortening integration feedback loops.
OutcomeFaster certification, safer protocol testing, clearer
diagnostics.
ISO 8583.NETWeb PanelTest Automation
02Transaction
platforms
Banking Terminal Ecosystem
Terminal and device software delivered across major Iranian banking and payment organizations, with careful attention to protocol compliance and operational continuity.
OutcomeReliable terminal behavior across complex
bank-specific environments.
NDCATMCashless DevicesC++
03ASP.NET Core products
Sahma · Samasoo · Sepanta
A group of modern business applications shaped through shared engineering standards, clean service boundaries, and a consistent delivery culture.
Reusable patterns without forcing unrelated domains into one model.ASP.NET CoreRESTSQLReact
04Healthcare technology
Omid Health Care
A domain-focused healthcare platform developed with attention to sensitive workflows, dependable data handling, and maintainable service design.
Clearer healthcare workflows supported by reliable application services.ASP.NET CoreDDDSQL ServerTDD
05Fleet operations
ATM Operations & Security
Operational tooling spanning IRMA, ATM Eye, and OTA capabilities to observe, protect, and update distributed banking-device estates.
Improved visibility and control across field-deployed systems.IRMAATM EyeOTAMonitoring
06Enterprise platforms
DataMatix Enterprise Suite
Back-end engineering and team leadership across ERP, CampSoft, PLM, and petty-cash applications in a multi-product environment.
Stronger workflow consistency and scalable application foundations..NET CoreERPPLMSQL Server
05 / Technology atlas
Broad enough to connect the system. Deep enough to challenge it.
I remain hands-on because architecture should stay connected to code, data, tests, deployment, and operational behavior. Technology choices are tools for managing change—not identity badges.
Design principleProtect the domain. Make the edges
replaceable.
01
Core engineering
C# · .NET Framework · .NET Core · ASP.NET Core · REST APIs · SQL · SQL Server · Python · Django · Javascript · React · Blazor
02
Architecture & Pattern
Domain-Driven Design · Clean Architecture · Onion Architecture · Microservices · Integration Design
03
Quality & delivery
TDD · NUnit · Unit Testing · Integration Testing · Agile · Code Reviews
04
Banking domain
ISO 8583 · NDC · ATM Operations · Cashless Terminals · Device Integration · OTA
05
Interface & legacy
React · JavaScript · HTML5 · WinForms · Web Forms · C++ · Delphi
How I lead
“My job is to make difficult decisions clear—and help the team make the next ones without me.”
Mahmoud Ali Sadeghi · Tech Lead & Software Architect
Architecture with evidence
Connect design choices to measurable reliability, delivery, and business outcomes.
Standards that teach
Use reviews, tests, and examples to transfer judgment—not to create approval queues.
Modernize incrementally
Create seams, protect behavior, and improve the organization’s ability to change safely.
Operate what we design
Include observability, failure recovery, security, and production learning in the architecture.
06 / Writing & field notes
Ideas from nineteen years inside real software systems.
I write about the distance between an architecture diagram and a production system: the language, trade-offs, tests, operations, and leadership practices that close that distance.
01
Domain-Driven Design Is a Conversation Before It Is a Pattern
The value of DDD is not in drawing more boxes. It is in creating a language precise enough for software and business experts to discover the same problem.
02
Reliability Is a Product Feature: Lessons from Banking Platforms
In transaction software, reliability is not a hidden engineering concern. It is the experience customers, operators, and partner systems feel at every boundary.
03
Modernizing Legacy .NET Without Breaking the Business
Legacy software is often the evidence of business value, not the absence of engineering skill. Modernization should preserve what the organization has learned while changing how safely it can move.
04
Technical Leadership Beyond Architecture Diagrams
Technical leadership is the practice of improving the decisions a team can make without waiting for the technical leader to make all of them.
07 / Education & research
Academic curiosity, applied to engineered systems.
MSc, Software Engineering
Islamic Azad University, Science and Research BranchTop-performing student. Research focused on link prediction using Learning Automata—exploring how adaptive models can identify relationships in evolving networks.
BSc, Software Engineering
Payame Noor University · EstahbanBuilt the computer science and software foundations that led into banking automation, enterprise development, and a career of continuous technical learning.
Research-minded engineering
I bring the same habit to architecture that I brought to research: define the problem precisely, test assumptions, observe evidence, and improve the model when reality disagrees.
08 / Let’s build something
dependable
Complex system? Ambitious team? Let's make the path clear.
I am open to technical leadership, software architecture, and senior .NET engineering opportunities with teams that value robust systems, thoughtful modernization, and engineering growth.
MAS
Direct contactsadeghi.yasser@gmail.com+98 917 330 9971
Location & mobility
Tehran, Iran
Open to relocation and international opportunities