Slide 2
Hands-on Developer | Strategic Requirements Engineer

For 25+ years, I’ve built software that works — not just on paper.

Starting as a developer (primarily C#), I evolved into Requirements Engineering and Business Analysis, bridging the gap between code, processes, and people.

I turn complex business challenges into actionable solutions: technically feasible, governance-aware, and decision-ready.

My strength lies in connecting business, IT, and strategy, transforming scattered requirements into structured delivery models that actually deliver.

Code, requirements, strategy — I thrive at the intersection where they all meet.

Slide 2
My Services

I approach software initiatives as end-to-end delivery systems — from initial requirements structuring and conceptual design to implementation oversight and stakeholder alignment.

I support organizations in:

  • Requirements Engineering and stakeholder alignment
  • business analysis
  • risk identification
  • as-is/to-be - comparison
  • structuring complex initiatives and defining executable work packages
  • software development and implementation
  • governance-aware documentation and decision preparation
  • operating effectively in agile as well as regulated environments
  • transformation leadership in regulated domains
Slide 2
My Motivation

In demanding environments I focus on creating structure, enabling informed decisions, and helping teams move forward with clarity.

For me, professional growth is not about chasing trends, but about

  • deepening understanding
  • sharing knowledge
  • helping teams move forward with clarity and
  • taking responsibility for sustainable outcomes.

I value collaboration, intellectual honesty, and the continuous refinement of both systems and thinking.

Slide 2
Requirements Engineering
At the core of software creation, I always prioritize the people who use the system.

Clear client goals are essential, but understanding the needs of all stakeholders is what makes the difference.

Analytical skills and interpersonal qualities go hand in hand: asking questions, actively listening, sharing ideas, and sometimes engaging in constructive debate.

Empathy is not just a comfort factor — it helps uncover real needs and forms the foundation for actionable requirements.

This all has long been a deep personal drive for me.

In fact, it was this passion for requirements engineering that ultimately led me into software engineering.

Slide 2
Software Engineering (primarily C# / .NET)

I build maintainable, testable software with a strong focus on C# and the .NET ecosystem — from backend services to integrations and tooling.

Typical topics I cover:

  • API design (REST), background processing, integration patterns
  • .NET architecture: clean layering, modularization, dependency management
  • Quality: automated tests, refactoring, code reviews, CI-friendly workflows
  • Performance & reliability: profiling, pragmatic optimizations, robustness
  • Delivery in regulated / governance-heavy environments (traceability & documentation)
  • see an overview of my experience
Slide 2
Industries

Most of the time I worked in those industries:

  • Biotech, focusing on the synthesis of Biopolymers (Peptide/DNA), development of a LIMS
  • Biopharma, Fermentation processes, Upstream/Downstream in the Process Science context, Labware LIMS Consulting
  • Biotech, Production & QA of a PCR Test kit, IPC - Digitization
  • Healthcare, Development work for a KIS with various 3rd Party Integrations
  • Automotive: Development work for a GPS-based Rail Control Solution
  • Legal/Contract Management: Development of a Contract Generator
Slide 2
Integrations

This aspect of software development has always particularly fascinated me. A significant part of a system's value is defined by how well it can communicate with other systems: distributed data thus becomes centrally available information.

With the ongoing digitalization, it has become essential to network information from various subsystems, extract it, transfer it, and convert it into an analyzable form. This process is key to moving from "islands of information" to a "connected plant."