When are you available?
I am available for full-time roles (IC or leadership) and high-impact contract work starting April 2026. I prefer jobs around Karlsruhe, Germany, but I am open to remote work.
Are you open to remote work?
Yes. I’ve worked remotely since 2021, leading distributed design teams and facilitating virtual workshops across time zones. I’m equally comfortable with fully remote, hybrid, or on-site arrangements.
Do you need visa sponsorship for jobs within the EU?
No, I don’t need visa sponsorship for a job within the EU. I hold German permanent residency and am authorized to work in Germany and across the EU without sponsorship.
What industries do you have experience in?
While my recent work has focused on enterprise B2B SaaS in life sciences (Cytiva) and healthcare/clinical trials (Clario), I’ve worked across a wide range of industries. These include financial services (Swiss Life), consumer products and services (Samsung, Spoon Radio), automotive (BMW), industrial technology (Bosch), as well as public-sector and government projects (UNDP, Brazilian Government), where accessibility, compliance, and long-term maintainability were key constraints.
I specialize in tackling complex, high-stakes problems, especially in regulated or technically demanding domains, by translating ambiguity into clear product strategy, intuitive user experiences, and scalable design systems. I’m particularly strong at working with cross-functional teams to align business goals, technical constraints, and real user needs, from early discovery through delivery and iteration.
Can you work as an Individual Contributor (IC)?
Absolutely. I’m equally effective as a senior IC delivering hands-on product design work and as a design lead guiding teams. As an IC, I focus on deep problem-solving, rapid iteration, and shipping high-quality, well-reasoned solutions independently.
My leadership experience strengthens my IC work: I understand the full product lifecycle, anticipate downstream implications, and collaborate autonomously with product and engineering, often requiring minimal direction while maintaining high standards and alignment.
What is your design process?
Research → Problem framing → Rapid prototyping → Validation → Deliverywith feedback loops between each step
Work starts with evidence. Research, data, and stakeholder input help define the real problem before solutions are explored. Assumptions are tested early through rapid prototyping and validation, so teams can go back, adjust, and test again before committing to development.
The result is clear, buildable interfaces and patterns that engineering teams can implement confidently, with accessibility in mind and attention to real-world constraints. Iterative collaboration with product and engineering ensures solutions can be shipped, maintained, and evolved over time.
How do you integrate Generative AI into your workflow?
AI tools, used in line with company policy (GitHub Copilot, Figma AI, Cursor, Windsurf, Claude Code, v0), help accelerate prototyping and exploration, reducing idea-to-wireframe time by roughly 40%. This enables faster iteration and broader exploration, while outcomes are still validated through user research and usability testing.
I presented on this topic at the Danaher Software Conference 2025, sharing best practices for integrating AI into design workflows without compromising quality. It became the most viewed session of the event.
How do you ensure design quality in handoff?
Code is treated as a design tool. A solid understanding of HTML, CSS, JavaScript, React, and Angular enables production-ready prototypes and design systems that map directly to component libraries.
Design quality is protected through close collaboration with engineering throughout the process, not just at handoff, so design intent, interaction details, and edge cases are preserved during implementation.
How do you measure design success?
Peter Drucker famously said that “the purpose of a business is to create a customer.” Roger Martin later captured the same idea from a design perspective, arguing that “the goal of design thinking is not better design, but better business.”
Design success, in that sense, depends on context and level. In the end, it is measured by business results such as revenue growth, margins, or competitive advantage. These results are often achieved indirectly, through clearer strategy, better alignment, and healthier team culture, rather than through isolated artifacts alone.
Measurement combines a few clear signals. At the business level, this includes outcomes like conversion, retention, time-to-value, or reduced support costs. At the product level, usability and user satisfaction show whether solutions work for people. At the team level, fewer revisions, smoother handoffs, and faster iterations indicate that better decisions are being made earlier.