Cloud architect and engineering manager

Platform engineering for working systems.

Cloud architect and engineering manager focused on platform design, backend systems, and pragmatic delivery.

Portrait of Manuel Schweigert
Role Manager, Cloud Architecture & Platform Engineering
Experience 16+ years in software delivery
Depth Software and enterprise architecture
Base Germany ยท German / English
01

Platform engineering

Cloud foundations, paved roads, service catalogs, governance, and operating models.

02

Developer platforms

Self-service, CI/CD, infrastructure as code, observability, and clear ownership.

03

Architecture

Software and enterprise architecture grounded in decisions teams can implement.

04

Backend systems

API-centric and event-driven systems with .NET, Aspire, Azure, and clear contracts.

.NET .NET Aspire Azure APIs Events Backstage Kubernetes Terraform Bicep GitOps CI/CD IAM AI workloads

Selected work

A few public-safe signals, without the customer names.

Platform

Internal Developer Platform

Product owner and lead architect for a reference platform around self-service, service catalogs, DevOps, IaC, monitoring, and developer enablement.

Backend

Cloud-native .NET systems

Architecture and team steering for backend platforms using C#, ASP.NET, .NET Aspire, Bicep, Azure Container Apps, Service Bus, API Management, and Microsoft Graph.

Enterprise

Architecture to delivery

Target pictures, requirements, governance, tradeoffs, and delivery paths across financial services, mobility, renewable energy, media, and IT infrastructure.

Leadership and delivery

Architecture is most valuable when it helps people decide.

Project and team leadership, facilitation, stakeholder alignment, architecture development, requirements engineering, and technical delivery without losing sight of implementation reality.

Credentials

Cloud, architecture, requirements, service management.

  • Azure Solutions Architect Expert
  • IREB CPRE
  • iSAQB Software Architecture
  • TOGAF 9 Certified
  • ITIL 4 Foundation
  • M.Sc. Computer Science, KIT

Working style

Less ambiguity. Less ceremony.

Clear boundaries, visible tradeoffs, and guidance teams can act on.