I build the software businesses run on, and I have been doing it since 2017 — starting while I was still a computer engineering student, and full time on my own since late 2025.
Most of what I do is the part customers never see: the system underneath, the data in it, and the work of keeping both correct once real people depend on them.
I spent five years as lead engineer on a digital menu platform, and most of another building a monitoring system for a brokerage. Both were the same shape of work: one engineer who knew the whole system, answerable for it, still there a year later.
That is the arrangement I kept choosing, so eventually I stopped pretending it needed a company around it. There is no agency here and no team to brief — the person you email is the person who writes the code and the person who fixes it at eleven at night.
The work I take on is the work I am actually good at. When it is not, I say so on the first call rather than three weeks in, which costs me the occasional project and has never once cost me a client.
Three things I did not believe at the start and would now argue for at length.
01
Almost every project that goes badly went wrong before any code was written, in a conversation nobody had. I spend the first days asking questions that sound obvious, because the alternative is building the wrong thing quickly.
02
Anything worth building gets changed. If a change is frightening, the system has failed regardless of whether it currently works — so the tests, the release process and the documentation are the feature, not the overhead.
03
If you cannot follow what I am telling you, you cannot judge whether I am right, and you are back to trusting a stranger. Every technical decision here has a plain-English version, and I would rather give you that than sound clever.
I have a literary background as well as an engineering one, and I am reading for a master's in English literature. Most of the time I am not writing code, I am reading.
It is less of a detour than it sounds. Both jobs are mostly about saying a complicated thing clearly to somebody who has no reason to be patient with you.
I am deliberately not on many platforms. Email reaches me faster than anything else does.
Since 2017
Building web software, starting while I was still a computer engineering student.
Where I work
Remote, with clients across Europe and North America. I arrange my day around whichever of those you are in, so there are hours every day when you can actually reach me.
Open source
Four small tools I kept needing and eventually published, plus a free URL shortener built as a non-profit. See the code.
I can confidently say that Hesam is one of the most disciplined person I have ever had the opportunity to work with. His leadership skills are excellent and he always ensures that his team is performing at its best. His commitment to delivering high-quality results shows in every project he handles. If you're looking for a Back-end development role, I highly recommend Hesam who makes a positive impact on any team he joins.
I had the privilege of working alongside Hesam from my very first day as an intern, and I can confidently say he played a pivotal role in shaping my growth as a developer. As a backend developer, Hesam combines deep technical expertise with a rare quality—genuine patience in mentoring others. What sets Hesam apart isn't just his technical skill; it's his willingness to stop what he's doing to explain a concept, debug an issue together, or share the why behind a decision—not just the how. Many of the habits and best practices I rely on today were shaped by his guidance. Beyond his technical abilities, Hesam is the kind of teammate every engineering team needs: reliable, collaborative, and genuinely invested in the success of those around him. Any team would be lucky to have him.
The most disciplined coworker I’ve ever had. Hesam is extremely focused and giving up is not an option for him. He’s actually the man who gets things done no matter what it takes. His enthusiasm to learn new things is unbelievable. He’s the one you can get inspired by.
After working with Hesam for about 1 year, I can confidently say that you will have a compassionate friend and strong character in your team.
A paragraph about what you are trying to build is enough to start. You will get an honest answer about whether I am the right person for it, including the times when I am not.