The gap between a design and a shipped product is where I work.

I'm a Design Engineer. The design and the code come from the same person.

Most products lose their best ideas in the translation between the person who designs the interface and the people who build it. I removed that step by learning both sides. I design the information architecture and the microcopy, and then I write the TypeScript and run what ships.

The proof is TenderMonitor.sk, a procurement intelligence SaaS I run alone, from the AI matching pipeline and self-healing scrapers down to billing, GDPR flows, and daily digests. Before that I spent years designing dense enterprise software: pricing platforms, dashboards, AI copilots. The hard problem there is always the same: how to make a complex system feel legible.

• 01

  Shipped beats perfect

  A live product with rough edges teaches more than a flawless prototype. Everything in my portfolio runs in production or did.

• 02

  Systems, not screens

  I design components and rules, not pages. Tokens, modular libraries, and constraints are what let one person move like a team.

• 03

  AI with guardrails

  Putting AI into a real workflow takes more than a chat box. Users need to see what it will do, confirm it, and stay in control.

• 04

  Clarity is the feature

  Enterprise software is notoriously cluttered. The job is to strip noise and surface the next action exactly when and where it's needed.

Outside production work I experiment with agentic development: I orchestrate specialized AI agents under tight specs and see how far one design engineer can take a product. Some of those experiments are in the Lab.