Define ownership
Before work starts, I clarify the objective, decision boundaries, and handover point. Everyone knows what I own and which decisions remain with the team.
About Felix
Technical ownership means making decisions, implementing them, and handing over a system the team can run.
I am Felix Faust, an independent senior product and platform engineer. For more than eight years, I have worked on digital products, cloud platforms, and migrations.
My work connects software development with delivery and operations. Architecture decisions remain grounded in working code, production behaviour, and the needs of the team responsible for the system.
- 8+ years
- Product and platform work
- Hands-on
- Architecture and implementation
- DE / EN
- German and English
- DACH & EU
- Primarily remote
Working across product code and operations
Many technical problems sit between established responsibilities. A frontend depends on an unclear API, a release fails at the platform boundary, or a migration reaches production without a workable operating model.
I work across those boundaries. Depending on the project, I may own product code, APIs, and data models or focus on cloud runtime, delivery, observability, and cutover. The engagement needs a defined area I can take through a verifiable result.
How I work
Test decisions against the system
Architecture needs to work in code, delivery, and production. I implement critical parts myself and validate important assumptions early.
Include operations
Deployment, monitoring, and maintenance are part of product delivery. A feature is complete when the team can release and operate it safely.
Prepare the handover early
Decisions and operational knowledge are captured throughout the project. Documentation and knowledge transfer do not wait until the final day.
Experience
I started in software development and took on platform ownership as the systems grew.
I began my professional career in application development in 2015. My early work covered Java, JavaScript, and React systems before expanding into TypeScript products, APIs, and integrations.
The operational part grew with the applications. I took on cloud infrastructure, Kubernetes, OpenShift, CI/CD, GitOps, Kafka, IAM, and observability. Later engagements combined product development, migration, and platform operations within the same technical responsibility.
This background is useful when a project does not fit cleanly into an application or infrastructure team. I can discuss product and business requirements with stakeholders, then work with engineers on the technical consequences.
Direct collaboration
You work directly with me. I can take responsibility for a defined part of the project or join an established product and engineering team.
I can provide technical leadership while remaining involved in implementation. The team should be able to continue the decisions and operations after the engagement.
- Independent B2B contractor
- Remote across DACH and the EU
- On-site work by agreement
- Native German, fluent English
The work provides the evidence.
Two anonymised cases show how I connected applications, platforms, migrations, and operations in real engagements. The public CV provides further project history and technical detail.
A strong fit
I work best on projects that need experienced technical decisions and direct implementation. The typical engagement involves an existing team and a defined area that needs additional senior ownership.
- New and established digital products
- Modernisation without an unnecessary rewrite
- Cloud, Kubernetes, and OpenShift migrations
- Constraints between applications, delivery, and operations
- Technical direction followed by implementation
Work together
Does your project need technical ownership with hands-on implementation?
Describe the current situation, intended outcome, and planned start. I will assess which defined area I can take responsibility for.