About
The person who writes your code is the person you talk to
I'm Hau Vo, a product engineer and software architect in Ho Chi Minh City. 15 years, 20+ products, six industries — IoT, automotive, edtech, logistics, energy, and one fashion-tech startup of my own that did not make it.
Most of that time was spent as the senior engineer inside someone else's team, which is why the way I work independently still looks like joining a team rather than delivering to one. I have also sat on the other side of the table as a CIO, which is where the habit of asking what breaks at 3am comes from.
Teams I've built for
How an engagement runs
What it is like to work with me
I do the work
There is no team behind this page and no account manager in front of me. The person who scopes your project, writes the code, and tells you when something is going wrong is the same person. On the rare project that genuinely needs a second specialist — a designer, a data engineer — I bring one in, tell you who they are, and stay accountable for the result.
You get direct access
Your Slack, your standups, your repo, your review standards. I join what you already run rather than asking you to adopt a process. Weekly demos on project work, so direction gets steered while steering is still cheap.
Time zones, honestly
I work from Ho Chi Minh City, UTC+7, with teams across Asia, the Middle East, Europe and North America — every one of those zones is workable, including the US. What makes that true is not enthusiasm: before an engagement starts I agree specific overlap hours with you, in your time zone, and I keep them. Ask for the hours you actually need rather than the ones you assume are possible.
You hear the bad news early
If the plan will not scale, or the thing you asked for is not the thing you need, you hear it before the first commit rather than in a retrospective. I have been the founder who got that wrong and the CIO who had to fix it afterwards.
Background
Where the experience came from
Stack
What I reach for
Deep in the first two rows, working knowledge in the rest. I pick the tool that fits the problem and the team who has to maintain it after I leave, which is not always the one I would enjoy most.
FRONTEND
BACKEND
AI / ML
DATABASES
DEVOPS / CLOUD
PAYMENT / BILLING
MOBILE
Still deciding whether I'm the right person
Tell me what you're building. If it isn't a fit I'll say so on the first call, and point you somewhere better when I can.