Patrik Schmitz

Technical responsibility in a lead engineering context for DevOps, software design, and architecture as part of the replacement and modernization of existing governmental applications. Work in a security-relevant governmental environment with existing security clearance (SÜ1).

Conception, setup, and operation of the cloud and runtime infrastructure based on Kubernetes (RKE2), including stable development, testing, and production environments. Introduction of a GitOps-based CI/CD approach for end-to-end automation of build and deployment processes.

Design of the target architecture and development of distributed backend services with Spring Boot and PostgreSQL. Implementation of robust persistence and data access concepts, considering governmental requirements for security, traceability, and availability.

Conception and connection of standardized governmental interfaces as well as integration of central registry systems in the migration and asylum context (anonymized). Securing of applications and services via a central Identity & Access Management solution (Keycloak).

Technical leadership and guidance of a development team as Lead Software Engineer, including architectural decisions, technical coordination, and quality assurance across multiple project stakeholders.

Technical responsibility in a lead engineering context for the development and operation of Kubernetes-based cloud infrastructures for governmental online portals within the scope of the Online Access Act (OZG). Responsibility for stable development, testing, and production environments as well as for the implementation of end-to-end CI/CD and deployment processes.

Participation in the design of the target software architecture of the primary portal and the connected frontend and backend services. Derivation of technical guidelines and support for development teams in implementing architectural specifications.

Development and technical management of distributed backend services with Spring Boot for data storage and for sending and receiving messages from the portals. Integration of existing, nationwide used services and standards (including FIT-Connect, OSCI).

Conception and implementation of a project-wide test tool for simulating and validating incoming messages, usable by internal development teams as well as project stakeholders of the connected federal states.

Connection, configuration, and operation of a central Identity & Access Management solution based on Keycloak for multiple services and portals.

Cross-team technical coordination and professional leadership of the involved development teams, including coordination of technical decisions, support in architectural matters, and ensuring development and quality standards.