Hello, I’m Frank
I’ve been solving complex technical problems since 2008. Started at NATO refactoring 2-million-line codebases, now I architect platforms for growing retail organizations.
I step into undefined technical leadership roles — the kind where the problem is clear but the path isn’t. Whether that’s architecting a new platform, designing a risk-controlled migration, or establishing capabilities an organization doesn’t have yet. The goal is always to build foundations that outlast my involvement.
My Background
At HEMA (Dutch retail, 700+ stores, 6 countries), I’ve been Principal Engineer and Solution Architect since 2021. I architected their new order management platform with an incremental migration strategy — starting with small order samples in low-risk markets before expanding. I built their UI Design System, which became the foundation for custom product features and is now expanding across their ecommerce platform transformation.
When HEMA needed automated RFID inventory management operational in 10 weeks for their autumn collection, I designed the integration architecture and data exchange specifications with external suppliers, then guided the development team through implementation.
Beyond architecture, I served as interim Backend Chapter Lead for seven months, handling hiring and developer 1-on-1s while the chapter was still taking shape.
At NATO, I spent seven years across two stints (2008-2012, 2018-2021) building systems for defense operations. That included untangling and refactoring a 2-million-line Air Command & Control application into 40+ Maven modules, building secure federated chat networks, and developing cross-domain information exchange systems. I also authored a technical report on containerization adoption within NATO.
At KPMG, I spent six years building applications for finance, education, and government clients. I designed and developed full-stack systems — educational content platforms, financial compliance applications, government portals. I also introduced modern development practices (CI/CD, Git workflows, automated deployments) to organizations still building on developer machines, and coached teams to maintain them independently.
How I Work
Understand first, then build. I don’t jump into building for the sake of it. I take time to understand the business problem, the constraints, and the goals before designing solutions. This means solutions are technically sound, suitable, and sustainable long-term.
Build capability, not dependency. I create development libraries, design systems, CLI tools, and CI/CD pipelines that teams adopt as their own. The tools I built at HEMA are now organizational standards maintained by teams throughout the company.
Simple over clever. Complexity should be a conscious choice, not an accident. I care about coherence and long-term sustainability of the technology landscape — less is more.
Direct and honest. I’d rather have a difficult conversation early than let problems compound. That means challenging assumptions, identifying blind spots, and translating complex technical challenges into clear business language.
Identity
My visual identity draws from my Indonesian heritage — my great-grandmother ran a batik factory in Indonesia. Batik represents centuries of craftsmanship where intricate designs emerge from careful, deliberate process. Each layer intentional, each step building on the last.
It’s a fitting metaphor for how I approach technical work. Deliberate solutions over quick hacks. Building systems in layers, each one solid. Respect for craft and precision.
Interested in working together? Contact me to discuss your challenges.