2002
Learn the craft
I started my career writing production software in Mashhad. Those early years taught me to stay close to the details, understand the user, and never confuse complexity with quality.
About me
I grew from writing code to carrying the decisions around it.
I wrote my first production code in 2002. Since then, I've worked as a developer, solution architect, engineering leader, founder, and technical director. The titles changed, but the motivation stayed the same: understand the real problem and build something people can depend on.
My career has taken me from small teams in Iran to complex delivery across the UAE, the wider MENA region, and the United States. I've built products from zero, modernized legacy platforms, led multidisciplinary teams, and learned what it means to make difficult decisions when the answer is not purely technical.
I'm still a builder. I just see the work more completely now: the architecture, the people, the product, and the trust required to hold them together.
The path here
The work changed. The responsibility kept growing.
2009
Take on bigger systems
My work expanded across the UAE, the wider MENA region, and the United States. I moved from implementing features to shaping architecture, guiding teams, and delivering platforms for organizations with very different constraints.
2016
Become responsible for the whole
Founding Profile changed my understanding of leadership. I was no longer responsible only for the technology, but also for the product, the team, the business, and the decisions that connected them.
Now
Build the next generation carefully
Today I work from Dubai, helping organizations modernize important systems and introduce Agentic AI with clear boundaries. I'm also open to a full-time leadership role in the UAE where that work can go deeper.
A defining chapter
Profile taught me what ownership really means.
I founded Profile as a professional social network for Iranians. Over seven years, we grew a team I was proud of, rebuilt the platform from a legacy monolith into a modern distributed system, and served a community that gave the product real meaning.
The hardest decision came when investment opportunities required compromises in governance and transparency that I could not accept. I chose to close the company rather than build a version of it that no longer reflected why we had started.
That experience made my definition of leadership simpler: take responsibility for the outcome, especially when the right choice is the difficult one.
Read why I closed Profile →What experience taught me
The principles I bring into every room.
01
Architecture is a people decision
A system succeeds when the people responsible for it can understand it, operate it, and keep improving it after the original architect has moved on.
02
Reliability is a promise
Performance, maintainability, security, and clear ownership are not technical extras. They are how a product keeps its promise to the people who depend on it.
03
Some compromises cost too much
Closing Profile taught me that growth is not automatically progress. The terms, governance, and principles behind a decision matter as much as the opportunity in front of it.
Why Agentic AI
A new capability deserves mature engineering.
Agentic AI brings me back to what has always interested me most: systems that do meaningful work under real constraints. The difference is that these systems can now choose, act, and adapt. That creates enormous potential, and a new level of responsibility.
My focus is on making that capability useful in the real world: clear permissions, bounded autonomy, observable decisions, rigorous evaluation, and human judgment where it matters. The objective is not to make AI look impressive. It is to make it dependable enough to earn a place in important work.
Let's work together