Senior engineer.
Product mindset.
Systems discipline._
I work best where product complexity, technical debt, and delivery pressure meet. My job is usually to simplify the system, make the team faster, and keep the user experience coherent while the architecture evolves underneath it.
Background
I started as a full-stack engineer and grew into the kind of role that sits between product delivery and architecture. That usually means inheriting complicated systems, clarifying tradeoffs, and turning loosely defined requirements into shippable work.
Over the last decade, I've worked across consumer products, fintech, legal tech, enterprise software, and internal tooling. The through-line is consistent: reduce unnecessary complexity, improve operability, and keep the product team moving.
I still enjoy broad ownership, but I'm most useful when the work requires judgment: choosing what not to build, drawing cleaner boundaries, and turning architectural decisions into something the team can actually maintain.
Experience
SAP
2021 — PresentSenior Software Engineer
Leading frontend architecture work inside a large enterprise environment, with a focus on maintainable React systems, design-system quality, and delivery practices that scale across teams.
smava GmbH
2019 — 2020Senior Full-Stack Engineer
Built and evolved lending-platform software across frontend and backend, balancing performance, reliability, and compliance-heavy product requirements.
Legal One GmbH
2018 — 2019Senior Full-Stack Engineer
Helped modernize a legal-tech platform by separating concerns, improving developer workflow, and moving critical product surfaces toward a more maintainable React-based stack.
SPARWELT GmbH (RTL)
2016 — 2018Full-Stack Engineer
Delivered customer-facing product features for high-traffic publishing and affiliate platforms, including mobile initiatives and performance-sensitive frontend work.
Customer Alliance
2015 — 2016Full-Stack Engineer
Worked on data-heavy SaaS systems and internal tooling in a polyglot environment, shipping features while navigating large legacy codebases.
Plinga GmbH
2015Software Engineer
Supported backend modernization and API work for a large gaming platform with strong emphasis on stability and scale.
Independent Consulting
2014 — 2015Freelance Software Developer
Delivered software projects for international clients across web, backend, and consulting work, building the commercial foundation for the career that followed.
Dräxlmaier Group
2013Software Engineer Intern
Developed low-level Java tooling for automotive manufacturing, enforcing strict reliability over complex interior electrical modules.
Tunisie Télécom
2012Software Engineer Intern
Engineered raw socket communications in C to enforce synchronized interactions between distributed Linux databases.
Core Stack
Operating Principles
- 01Prefer simpler systems over impressive ones.
I bias toward architectures teams can operate and change confidently, not architectures that look sophisticated in diagrams.
- 02Build for maintainers, not just launch day.
Readable boundaries, sensible defaults, and clear ownership matter more than clever abstractions that only make sense to their author.
- 03Reliability needs visibility.
Logs, metrics, and operational feedback loops are part of the product. They are not optional cleanup work for later.
- 04Good UX starts with sound architecture.
Fast interfaces are easier to design when the underlying data flow, loading behavior, and failure modes are understood early.
- 05Faster feedback makes better teams.
I care about developer experience because slow CI, unclear ownership, and fragile tooling directly reduce product quality.