I make
software
that works for humans
I'm a senior product engineer who works across the stack — but my real job is reducing the distance between a user's problem and a working solution. That usually means staying close to design and product, prototyping early, and shipping in small, observable steps.
I'm opinionated about the unglamorous fundamentals: clear interfaces, tests that catch what matters, telemetry that turns guesswork into evidence, and release pipelines that don't get in the way. I think most product quality comes from boring discipline, not heroics.
I started in Barcelona, moved to the Netherlands, and these days I split my time between writing maintainable code, mentoring teammates, and pushing back — gently — when a feature is solving the wrong problem. Outside work: smart-home tinkering, OSS on the Home Assistant frontend, and long walks with my husky Iglu.
My journey,
honestly told.
InSpace
· Senior Engineer · Experience Team Lead- →Lead the Experience Team, building NOVA: the AI SEO & GEO platform our clients see and use every day.
- →Build the components and patterns that scale across NOVA, through a shared design system.
- →Work from the user outward: who is using it, what they are trying to achieve, and what the interface is really asking of them.
- →Designed an agent-driven engineering workflow: isolated tasks, quality gates, independent reviews and review checklists that learn from every PR.
YieldComputer
· Senior Software Engineer- →Automated the entire release pipeline, increasing deployment frequency 5×.
- →Defined a complete testing strategy (unit, integration, E2E) — production incidents dropped 70%+ over 6 months.
- →Introduced product analytics and instrumentation; gave the team visibility into user behaviour and a basis for prioritisation.
- →Shifted the team from pure development to product-oriented thinking.
- →Acted as a technical leader without formal authority — identifying bottlenecks and lifting standards across teams.
finsit by Wolters Kluwer
· Product Software Engineer- →Built scalable frontend modules in pure JavaScript on top of internal libraries.
- →Strengthened reliability with automated testing in Cypress and Jasmine; cut regressions in critical flows.
- →Contributed to backend services in C# alongside cross-functional teams.
- →Modernised shared components and tooling, accelerating the entire frontend team.
Nakima
· Fullstack Developer- →Delivered web and mobile apps including on-device facial recognition.
- →Shipped to major marketplaces with scalable Firebase / MongoDB backends and real-time pipelines.
- →Owned end-to-end client requirements: scoping, delivery, iteration.
- →Acted as the technical anchor between designers, backend, and stakeholders.
What people say.
Jan is a key driver within the YieldComputer team, bringing strong initiative, thoughtful decision-making, and a calm, professional leadership style. He combines strategic thinking with solid technical skills and a rare ability to truly listen and align people around the right direction.
Recognition
More about me →Synced zoom across history charts, one of the release's Noteworthy changes.
From chart features to login and energy fixes, in one of the largest open-source user interfaces.
Written recommendations from the CTOs of YieldComputer and finsit, and the architect who managed me.
Threat detection, privacy and data confidentiality, network vulnerabilities.
From the blog.
All posts →
Review is the job now
When agents write most of the first drafts, the scarce skill is judging code, not typing it. How I review code I didn't write: triage, a full-diff read, Claude's first pass, a cold second opinion, and a loop that learns from every human comment.
A menu bar that knows about my meetings
A personal tool that touches my calendar deserves the same care as a product feature. How my menu bar keeps important meetings visible while I'm in focus mode, and keeps private titles off a shared screen.
Release pipelines that make shipping boring
From building on a laptop and dragging files onto a server to a pipeline nobody has to think about: why automating releases changes how a team behaves, and how to introduce it without formal authority.