Some things about me:

• I studied CS at the University of Eastern Finland.
• I started out as an FDE3, back when PHP and AJAX still ruled the stack, and took ownership of everything under it: racking, networking, Linux/Windows, up through the app layer.
• I've also built applied AI systems elsewhere: RAG pipelines and search-inference services running at scale behind an API.
• I built products at Invisible Technologies (an AI workforce and process-automation platform): LLM-powered search and verification systems, plus a business-automation platform used in production every day.
• I also built the human-data side of LLM training there: an annotation platform for data collection, and SFT/RLHF/RLAIF annotation myself.
• I worked on robotics systems at UEF Robotics Club.
• I love building things that are robust, well-designed, and insanely useful. Too much software today is disposable, and I try not to add to that pile, so I read documentation and sweat the details.
• I default to open source (think Linux, FFmpeg): when something breaks, I can read the code and find out why, not wait on a vendor.

Some things I'm interested in:

• Robotics and autonomous systems. The intersection of software, hardware, and intelligence is where the most interesting engineering problems live.
• Infrastructure and distributed systems, and everything that keeps things fast and fault-tolerant.
• AI/ML, especially training pipelines and making models useful in production.
• First-principles thinking across energy, compute, hardware, physics, history, philosophy, and well the threads that tie them together.

Check out my portfolio, reading, alpha and deep dives.

1. I just go by Glory. ↩
2. MTS = Member of Technical Staff: a generalist technical title, not scoped to one layer of the stack. ↩
3. FDE = Forward Deployed Engineer: embedded on-site to build and ship directly against complex system. Mine was healthcare, so read: heavy compliance, strict determinism, zero room for flaky behavior. ↩