Founding full-stack developer, Quulio
FoundationalFirst developer on an all-in-one business platform for the self-employed in Finland. Laid the architecture others would build on.
Own theWhole stack
I build software that has to survive contact with real users, and I'd rather own the whole stack than hand off the hard parts.
I'm an AI-augmented full-stack engineer working mostly solo, across Python, TypeScript, and whatever the product actually needs. Most of the platforms in my work are ones I built from the first commit: architecture, schema, APIs, frontend, and the deploy pipeline underneath, because I've found that owning the whole surface is what makes a product actually ship.
Lately that's meant a lot of AI integration work: retrieval systems that need to be debuggable, not just impressive in a demo, and LLM products that have to behave predictably for a paying customer, not just a hackathon judge.
ThePath
HeroGeneration, Leo, Magic Makers
Solo buildsTook on sole-developer roles across HIPAA-compliant SaaS, AI transcription, and consumer AI products, architecture through deployment.
Lead engineer, OGE
22 monthsJoined at the first line of code and led architecture across a real-time AI crisis-simulation platform, ~136,000 lines delivered continuously.
Sole DevOps engineer, Dayonai
Cloud & securityBuilt a SOC 2-ready AWS foundation from scratch for a 20-engineer org, entirely as Terraform IaC.
AI Augmented Engineer
NowWorking across AI integration, full-stack product builds, and cloud infrastructure, mostly solo, always shipped to production.
What IBelieve
Opinions earned the expensive way.
- A feature that ships broken teaches you more than a feature that never ships.
- If you can't observe it, you don't actually control it.
- Access control is a design decision, not a patch you add before launch.
- The best architecture is the one a second developer can understand without asking you.
- AI products live or die on retrieval quality, not model choice.
BeyondCode
When I'm not shipping, I'm usually reading about the systems behind whatever I'm building next, or arguing with myself about whether a feature actually needed the complexity I gave it.
Book a call