I like being the person who both writes the code and answers for it

I'm a senior full-stack engineer in Helsinki. For the past five years I worked on one thing properly: a process and task mining platform that I joined as the third engineer at a startup and ended up owning as ProcessMaker's primary technical owner after it was acquired. I rebuilt the team, relaunched the product, and ran it for enterprise customers across Europe, the US, and Australia, staying roughly 70% hands-on the whole time.

I got here the long way. I grew up around technology and was always the tech-savvy one, and my brother spent years telling me to go into IT, but I trained as an electrician instead and worked at Helsinki Airport. It took moving to Vietnam to teach English to see it clearly: electrical work wasn't the life I wanted, and the thing my brother had been pointing at all along was the obvious fit. I came back, took University of Helsinki's open programming courses, and picked Laurea for my degree because it let me study remotely; the plan was to do it from Vietnam. COVID closed the borders one week before my flight, so the degree happened from Helsinki instead, and it led me to Workfellow, where the real story begins.

Outside work I practice Hokutoryu ju-jutsu, cycle, travel, read quite a bit to keep developing myself, and still speak a little Vietnamese from my teaching days.

Staying with the same product from startup code to enterprise platform, across two companies, taught me things greenfield work can't: what architecture decisions cost three years later, what actually keeps a platform reliable, and what a small team can maintain without drowning. That's the experience behind the headline above.