You're recruiting for senior/staff.
Available for senior remote roles. Backend, architecture, AI-native, distributed team leadership. Bilingual CV, open calendar.
See full CV →12+ years of architecture, leadership, and backend on high-traffic eCommerce platforms. Magento, Hyvä, complex integrations, and AI-native workflows. I write about what I learn leading distributed teams.
Three paths
No need to disguise the site depending on who walks in. Here's the map, plainly.
Available for senior remote roles. Backend, architecture, AI-native, distributed team leadership. Bilingual CV, open calendar.
See full CV →Stories on architecture, scalable systems, Claude in real pipelines, and what I learn leading distributed teams. They ship when they're ready, not on a schedule.
Enter the stories →Audits, architecture, performance, team mentoring. Scoped engagements, clear metrics, real deliverables.
Let's talk about it →Latest stories
Long reads, no filler. Each one makes a point and tells the story behind it, technical or not.
The engineering process behind a RAG system for software, told problem by problem: retrieval, chunking, metadata, tools, citations, and security.
Agent orchestrators are repeating the history of operating systems, mechanism by mechanism. Today they resemble it; tomorrow they will be a copy. Parallels, differences and predictions.
How MageObsidian serves the checkout page from the full page cache: a public shell, a private section, and everything the controller used to do on every request.
Work
Concrete cases you can verify, not promises. Two here; the rest at /work.
I'm embedding every story and engagement into a vector store. Claude will answer using those sources and cite exactly where each claim came from. If there's no answer grounded in my content, it will say so instead of making something up.
The best engineering I've done doesn't show. It lives in systems that don't call attention to themselves, teams that don't panic, and metrics that climb while nobody's watching.