The full story
Full-stack engineer with a firmware background and a product habit that never went away.
// background
It started with a soldering iron, not a text editor.
I started out in embedded systems, writing firmware close to the metal, wiring up sensors, and debugging protocols like UART, SPI, and CAN with an oscilloscope instead of a browser console.
Hardware doesn't forgive sloppy thinking. Limited memory, no garbage collector to bail you out, and bugs that only show up at -10°C in a customer's warehouse. It taught me to understand a system fully before touching it, a habit that never left.
// the turn
I cared more about the people using it than the chip running it.
The turning point wasn't a framework, it was watching someone use software I'd helped build and struggle with a screen that made perfect sense to me and no sense to them.
That pulled me toward product and SaaS, where the feedback loop is fast and brutal: you ship, you watch what people actually do, and you find out immediately whether your mental model matched theirs. I've been chasing that gap between code that works and software that feels right ever since.
// what I value
A few things I don't compromise on.
Ownership over tickets.
I follow a feature from the first user conversation to the metric it was supposed to move. A ticket closed is not the same as a problem solved.
→ Creator Analytics PlatformTalk to users before you talk to Figma.
Most bad software isn't badly built, it's built for the wrong problem. I'd rather spend a day in user interviews than a week rebuilding the wrong feature.
→ Creator CRM & AutomationClean enough that nobody has to ask me.
Architecture and naming are a courtesy to whoever reads the code next, including me in six months. No clever tricks that only make sense today.
→ This Portfolio// skills
Only listing what's shipped, not studied.
// today
Full-stack, product-minded, based in Munich.
These days I work across the stack, architecture, backend, frontend, and the interaction details in between, on products where the outcome, not the tech stack, is the point.
If that sounds like a fit, I'm reachable at me@kampa.dev.