About
Early Days
A Borrowed Oric-1, and Iran's First PC Game
Pooyan is Persian for the one who seeks — who keeps moving toward what he doesn’t yet understand. I can’t say whether the name shaped the kid or the kid grew into it, but it fit early. I was hands-on before I was anything else: carpentry, chemistry, electronics — whatever could be taken apart and made to explain itself.
Then, at nine, an Oric-1 found its way to me, and everything else became a hobby. Computers were scarce, so I went wherever one was — and wherever there was someone who knew more than I did. By fifteen, I had written a VGA rendering engine in assembly for the first PC video game released in Iran. Writing games in assembler on scarce hardware teaches you something permanent: constraints aren’t the enemy of the work. They’re the shape of it.
Training
Why Industrial Engineering, Not Computer Science
By university, I could already build software. Industrial Engineering — Technology Management — did something more useful than teach me to code: it widened the question. Product lifecycles, lean processes, whole systems instead of single programs. It turned a programmer’s how do I build this? into the question I’ve asked ever since: why this — and why this way?
The Road Here
Tehran to Saskatoon, in Four Chapters
As an organizational diagnostics specialist at Yekan Consultant Group in Tehran, I walked into companies of every size to find where the system — not the people — was failing. It was my first proof of something I still believe: most broken things break upstream of where they hurt.
I founded Paradise Software Group and ran it as CEO, shipping software into the Iranian market: antivirus, disk-duplication tools, installer makers, screen savers, and an educational game pack for toddlers. Running a small software company means doing every job in it at least once — the fastest education I’ve ever had.
At a Samsung Electronics subsidiary, as Program Manager and Head of Software Engineering, I led Smart-TV content localization and agile product delivery — global standards, enterprise scale, and the discipline both demand.
Then I crossed the world. At TinyEYE in Canada, I began the way I’d begun at fifteen — building games, this time for children in therapy — and grew into Director of Technology and Innovation: product, engineering, and the cloud infrastructure that delivers therapy to students across North America. The kid who wrote a game engine at fifteen ended up making games that help kids find their words. Life is rarely that tidy. I try to deserve it when it is.
What I Hold On To
Values, Not a Skills List
The skills live on LinkedIn. These are the operating principles.
Curiosity — infinite, and not decorative. It’s the closest thing I have to a justification for existence.
Integrity — absolute, and partly for selfish reasons: every lie you keep is state you have to manage, and I’d rather carry less.
Why before how — the first question protects you from building the wrong thing beautifully.
And people at the center. I read philosophy and psychology as part of the engineering, not apart from it, because every system I’ve ever worked on was made of people first.
Philosophy
The Obstacle Is Information
Whether I’m refactoring legacy code, re-architecting cloud pipelines, or mentoring someone through a stuck season, the constraint usually points at the opportunity — you just have to look at the inconvenient thing long enough to hear what it’s offering.
I learned that on 8-bit hardware. I’ve relearned it in every job since.
Let’s Connect
If you’re looking for a technology leader, software architect, or a consultant on leadership and process — someone who brings engineering rigor, product vision, and a human-centred perspective in the same person — find me on LinkedIn. The blog is where I think out loud, in English and in Farsi.
The name means seeker. I’m still earning it.