Independent engineer · Munich, Germany

DevOps & automation

I turn manual build, deployment and infrastructure tasks into repeatable workflows with explicit checks, permissions and recovery steps.

Discuss your requirements

The client problem

When deployments depend on one person, local scripts or undocumented environment differences, delivery becomes difficult to reproduce. Automation starts by identifying those dependencies and deciding which steps need validation or human approval.

Technical scope

  • CI/CD pipelines and deployment automation
  • Infrastructure as code, containers and environment configuration
  • Monitoring integration and repeatable operational tasks

Deliverables to agree

  • Versioned pipeline or automation definitions
  • Environment prerequisites, verification and recovery steps
  • Runbooks and handover for the team operating the workflow

Example engineering approach

A deployment workflow can build an artifact, run agreed checks, promote the same artifact to the target environment, verify service health and record the result. Credentials and approval requirements are designed around the existing operating model.

Service boundaries

Automation does not remove the need for backups, permissions or change approval. Cloud charges, software subscriptions, infrastructure ownership and any out-of-hours support are agreed separately.

Experience and technical context

Review my published projects and technical expertise to assess the fit for your systems. The project descriptions show the actual work; technology selection and availability are confirmed for your engagement.

Published engineering projects · Technical expertise · Professional background

Buyer questions

Can you improve an existing pipeline?

Yes. A review can start with the existing repository, build failures, deployment steps and recovery process. Replacing the toolchain is considered only when the requirements justify it.

Which operational task should be automated first?

Choose a repeated task with a clear input, a verifiable result and a safe failure path. Frequency alone is insufficient: access, impact and maintenance effort also determine priority.

Start with the business and technical context

Share the systems involved, the problem to solve, the expected delivery window and your access or security constraints. A short initial summary is enough to assess the next step.

Discuss a project

Related services

Enterprise integration

I connect business applications, messaging systems and data flows so that teams can change their systems without losing control of the interfaces between them.

Custom business software

I build custom applications, internal tools and APIs around a company’s actual workflows, including their integration, deployment and maintenance requirements.

Production support

I help teams investigate production problems, maintain business-critical software and make operational knowledge repeatable through monitoring, documentation and automation.