I build software, then the teams that build it.
Hi, I'm Meysam. For 15+ years I've gone from writing code to leading engineering organisations at Sheypoor, Takhfifan, and Karnameh — and I still believe the org chart is a system, just like the architecture.
I write about engineering leadership, technical organisations, and the decisions that connect them. Most of what I write comes from building and rebuilding engineering teams in real businesses — including the things that worked, the things that didn't, and the decisions I'd make differently today.
the whole thing is one system. on good weeks, it even bears fruit.
How I think
all five principlesTeam boundaries have architectural consequences.
Teams don't just maintain architecture — the way teams are structured often shapes it.
Shipping is an organisational capability.
A team that cannot release is not necessarily facing only a deployment problem.
Featured case study
evidence, not claims
We didn't have a traffic problem. We had a systems problem.
Diagnosing a prolonged traffic decline, replacing a custom SSR implementation, restoring the ability to ship the Android app — and rebuilding engineering ownership along the way.
Selected writing
all writing-
When Technical Debt Becomes Business Debt
lessons from practiceDebt stops being an engineering concern the moment it affects acquisition, conversion, reliability, or speed.
-
We Didn't Need to Build an SSR Framework
architectureOwnership is valuable when it creates differentiation — a distraction when it doesn't.
-
Your Team Structure Is Part of Your Architecture
organisation designTeam boundaries shape ownership, communication — and eventually the system itself.
Where the lessons come from
the full record-
Sheypoor
VP of Engineering. Two critical problems — declining traffic and no ability to ship — both resolved before I left.
2024–2025 -
Takhfifan
CTO. Owned technology and product as one organisation — shipped our own payment platform.
2022–2024 -
Karnameh
Technical VP. Built an independent engineering organisation from scratch, separated from Divar with zero service disruption.
2021–2022
translation · 317 pages · pdf
Leading Effective Engineering Teams — in Persian
Ten years of Google engineering leadership, made readable for the Persian-speaking community. Translating it felt like giving back the lessons this industry gave me.
About the translationAbout me
the short version
I'm an engineering executive based in Tehran. Since 2010 I've worked across software, systems, and engineering leadership — developer, lead, CTO, VP — at companies including Sheypoor, Takhfifan, and Karnameh.
What I care about professionally: engineering organisations that ship reliably without heroics; technical decisions that are connected to the business; organisation design treated as part of the architecture, not beside it.
What I write about: the decisions that connect engineering and organisation — documented with their context, trade-offs, and the things I'd do differently.
Longer conversations: Email ↗, LinkedIn ↗, or Telegram ↗.