GitLab CI/CD Experts in Hamburg
in minutes from over 15,000 CVs with the power of AI.Hire experts who set up GitLab CI/CD pipelines, GitLab Runner execution, and reliable release workflows for software teams in Hamburg and beyond. Get fast, precise matching with vetted, available freelancers.
Meet FRATCH Experts in Hamburg, who have recently used GitLab CI/CD
Daniel Sedlack
Last position:
Senior Software Engineer at energielenker solutions GmbH
- Designed and implemented a Python-based ETL pipeline with the Dagster framework to transform raw energy data from heterogeneous sources using InfluxDB and visualizations in Grafana
- Defined time-based and dependency-based jobs
- Deployed to managed Kubernetes clusters using Helm
- Integrated InfluxDB Cloud
- Prepared data for use in Grafana, including cleaning, normalization, and time-based resampling in Python
- Developed dashboards and visualizations in Grafana
- Developed unit tests with mocking using pytest
- Set up a CI/CD pipeline in GitLab
Technologies: Python, Dagster, InfluxDB, Grafana, pandas, pytest, REST, CI/CD, GitLab, Container, Kubernetes, Helm, Docker, Cloud
Rutger Boels
Last position:
Partner & Managing Director at AI.IMPACT
- Building an AI & Data Consultancy Practice with the goal of helping European companies adopt Artificial Intelligence and modern data platforms
- End-to-end further development of a production system using modified coding agents (OpenCode). Tech stack: Kubernetes, Argo, Keycloak, Typescript, Grafana, GitOps, DevOps, Playwright
- Internal research project on the use of coding agents in the field of mathematical logic for creating formal models. Use of Cursor IDE and Codex, Codex CLI. Architecture design, quality control and refactoring, as well as writing code and tests. Repository (open source) available pre-launch
- Research on the role of mathematical logic as a formal language that connects IT and AI with business processes
- Project lead for collecting and deploying parking recommendations for rail vehicles with significant savings potential based on real-time data in a mobility and transport company
- Project lead for collecting and distributing process measurement points for real-time control in a mobility and transport company
- Deputy application owner for an app used for communication in the dispatching and provision of rail vehicles
Thorsten Boock
Last position:
Senior Backend Engineer at VTG Rail Europe
traigo is VTG's digital rail logistics and fleet management platform. It processes large volumes of telemetry, mileage, geofence, sensor and wagon-movement events in near real time and provides operational services for rail logistics customers across Europe.
As part of Team Customer Selfcare, I worked on the design, implementation, optimisation and operation of large-scale backend services and event-driven processing pipelines — covering both feature development and operational ownership of business-critical production systems. I also regularly acted as first responder for production incidents, data inconsistencies and performance investigations across multiple distributed services.
- Design and implementation of event-driven backend services.
- Migration and replacement of legacy processing pipelines.
- Development of replay / rebuild mechanisms for large event datasets.
- High-throughput asynchronous event processing on SNS / SQS.
- Database and query optimisation for PostgreSQL and DynamoDB.
- Design of scalable read / write models and aggregation pipelines.
- Production troubleshooting and operational support.
- Performance tuning and infrastructure scaling.
- Design and stabilisation of integration and system tests.
- Technical concepts, architecture documentation, and cross-team collaboration.
- Support the further development of existing GitLab CI/CD pipelines
Geofence & Wagon Stay Processing
- Algorithm to detect vehicles within geofences (entry, exit, dwell time).
- Event sourcing with guaranteed chronological order within the affected time window.
- Refactored geofence event and wagon-stay processing logic for performance.
- Resolved race conditions and event-ordering problems in distributed services; server-side filtering, aggregation and optimised query pipelines.
- Repair and replay tooling for corrupted or inconsistent movement data.
Fleet Metadata & Mileage
- Modernised the service; migrated storage from DynamoDB to PostgreSQL to improve traceability and accelerate new features.
- Scalable mileage aggregation and replay mechanisms.
- Read / write models and optimised queries for high-volume mileage calculations.
Sensor & Telematics Integration
- Integrated telemetry and sensor processing pipelines.
- Snapshot and state-calculation logic for sensor systems.
- APIs and persistence models for wagon sensor data; data-quality improvements.
- Further development of a service using gRPC for intra-service communication.
Movement Segment Processing & Routing
- Migrated services to new movement-segment event streams.
- Built replay and rebuild tooling for segment correction.
- Optimised throughput and reliability for high-volume event processing.
Condition Monitoring & Wagon Analytics
- APIs and backend services for wagon condition monitoring.
- Brake-wear prediction processing and wagon analytics functionality.
- PostgreSQL views and optimised query models for operational dashboards.
Operational Reliability - First Responder
- Investigated production incidents and distributed-system failures; DLQ analysis, replay and operational recovery.
- Tuned database performance and AWS infrastructure under production load.
- Improved observability, monitoring and operational tooling.
- Supported rollout strategies, monitoring and post-deployment stabilisation.
Felix Ortmann
Last position:
Cloud Architect at uni-assist e.V.
- Project lead ‘Cloud Migration’ for moving the on-premise production environment to Scaleway.
- Transformed a Docker-Swarm legacy setup to a modern Kubernetes-based cloud environment.
- Architected a GDPR-compliant cloud landscape and deployment setup – 100% European sovereign cloud.
- Hands-on bootstrapped the cloud environment with Terraform, ArgoCD, and GitLab Pipelines CI/CD.
- Replaced the legacy VPN with modern mTLS PKI and deep AD integration.
- Managed an 11-headed agile team using Kanban, moderating team meetings and plannings.
- Successfully finished the migration, moving infrastructure, services, and data, from planning to execution.
Oliver Langer
Last position:
Developer, Architect at libri GmbH
- Role: Developer, Architect
- Technologies: java, typescript, golang, spring (boot, web, security, data), Angular, AWS (OpenSearch, Aurora, SNS/SQS, CloudWatch, EC2, IAM), Kubernetes, Terraform, Helm, OAuth, Keycloak, CI/CD, gradlew, Liquibase, Test Driven Development, shell scripting
Mark Plaatsman
Last position:
Full-Stack Software Developer, Product Data Import at Otto (GmbH & Co KG)
- Manage and operate the product data import services for the Otto merchant
- Enhance and maintain the backend systems
- Optimize and maintain AWS infrastructure
- Build a new product data import API
- Design and plan stories and features
- Conduct code reviews to ensure code quality and best practices
- Analyze and fix bugs
- Technologies: Java, Spring Boot, Kafka, AWS, Fargate, Terraform, MongoDB, Mongo Atlas, OpenAPI, GitHub, GitHub Actions, GitHub Copilot, Akhq, Debezium, JUnit, Test Containers, Hexagonal Architecture
Christian Hartmann
Last position:
Software Developer / Lead Developer at dpa (Deutsche Presse Agentur GmbH)
- Contributed to the development of the Rubix editorial system
- Implemented various microservices based on Java, AWS S3, AWS SQS, AWS SNS, and Spring Boot, deployed to AWS ECS and AWS Fargate
- Designed and developed AWS Lambdas using TypeScript
- Used PostgreSQL in an AWS RDS Aurora cluster and AWS DynamoDB
- Implemented continuous deployment with GitLab pipelines
- Built an Infrastructure as Code environment with AWS CDK
- Set up and maintained a monitoring platform using AWS CloudWatch
- Developed various frontend components with Vue.js
- Designed the microservice architecture applying Domain Driven Design and GraphQL interfaces
Lars Kleiner
Last position:
Lead Drupal Developer at x-tention
- Lead Drupal 10 developer for several greenfield projects in the health sector
- Drupal architecture in a cloud environment
- Set up and maintain GitLab pipelines and Kustomize scripts for Kubernetes deployments
- Development of Docker images
- Developed custom Drupal modules for features such as OAuth and FHIR
- Drupal frontend theming using Bootstrap 5 and Single Directory Components
- Set up and maintain automated Playwright tests
Johannes Erchen
Last position:
Libri GmbH
- Operation and further development of the inventory system for booksellers (Quimus). It is an in-house development by Libri that is sold to customers as Software as a Service. The software is developed in an agile way by two developer teams (about 5 developers each). The software consists of around 25 Java microservices that mainly communicate via messaging and share a common Angular frontend. The application runs on Kubernetes in AWS.
- Technologies used: Java 17 & 21, Spring Boot 2 & 3, Hibernate, MySQL, Spring Cloud AWS, Lombok, AWS SQS, AWS SNS, AWS RDS, AWS S3, DynamoDB, Kubernetes, Docker, OpenSearch, Hibernate Search, Liquibase, Gradle, Terraform, Helm, GitLab CI, Keycloak OAuth2, TypeScript, Angular
- My focus until December 2023: Connecting additional POS systems to the inventory system. Connecting the data warehouse for report display. Extending existing features (goods receipts, invoicing, item management, ...). Operations and DevOps tasks.
- Focus from January 2024: Extracting the product search from the inventory system into a global service to use in other applications. Integrating the product search into the booksellers' online shops (also run by Libri). Importing and providing digital items in the product search.
René Schmidt
Last position:
CRM Developer at CiS GmbH
- Developed a greenfield CRM for managing incoming customer requests for a municipal utility provider
- Implemented with PHP/Symfony 5, EasyAdmin, Doctrine ORM and Oracle XE
- Handed over to CiS GmbH after initial groundwork as planned
Anurag Singh
Last position:
Data Analyst (SME) at Cognizant
- Build data pipelines for raw and curated data layers using AWS S3, Glue, Athena, and Lake Formation
- Establish CI/CD using GitHub Actions or GitLab CI with CodePipeline
- Prototype models into demo APIs packaged with Docker, versioned with Git, added basic tests with pytest, and assist deployments on AWS SageMaker Endpoint
- Perform exploratory data analysis and feature engineering with pandas and PySpark; track experiments in MLflow or Weights and Biases
- Design and execute A/B tests to optimize user engagement and drive data-informed decisions
Taher Solimany
Last position:
DevOps Engineer at Confidential
- Collaborating with developers, security, and operations teams to align requirements
- Supporting product owners and development teams in deploying logging and monitoring solutions based on the Elastic Stack
- Developing and standardizing log schemas as well as defining practical standards for observability
- Designing and further developing logging architectures for complex, distributed multi-tenant environments
- Connecting application and infrastructure logs as well as security tools and metrics
- Optimizing data flows and modeling for analysis and reporting purposes
- Building automated infrastructures using Terraform/Terragrunt and Ansible
- Maintaining and evolving CI/CD pipelines in GitLab as well as automated development environments in Hetzner Robot
- Operating and automating Proxmox clusters including Ceph storage
- Setting up and running Kubernetes (k3s) clusters on Fedora CoreOS including core services like Vault, OpenLDAP, and HAProxy
- Implementing security-critical infrastructures according to BSI basic protection and securing existing systems
- Supporting the operation of solutions in cloud environments (e.g., AWS)
- Working in agile teams following Scrum and Kanban
- Technologies/Tools: Elastic Stack (Elasticsearch, Logstash, Beats/Elastic Agent, Kibana), Terraform, Terragrunt, Ansible, GitLab CI/CD, GitOps, Proxmox, Proxmox Ceph, Kubernetes (k3s), OpenShift, Helm, Kustomize, Vault, OpenLDAP, HAProxy, Hetzner Robot systems, AWS, Prometheus, Grafana, Syslog Linux/Windows, Docker, NGINX, Apache Security & Compliance (BSI basic protection, SIEM/SOC)
Frank Wolf
Last position:
Fullstack Software Developer at Goodright GmbH
- Built backend APIs using Quarkus, Kotlin, MongoDB, Docker Compose and NGINX
- Developed frontend with React, TypeScript and Ant Design
Discover over 15,000 top freelancers
Statistics of experts using GitLab CI/CD
Aggregated from the professional profiles of matched freelancers.
Experience
20 years (Germany: 17 years)
Position duration
2.3 years (Germany: 2.7 years)
Positions per freelancer
14 (Germany: 12)
Top business areas
Information Technology, Product Development, Business Intelligence
Top industries
Information Technology, Transportation, Professional Services
Certification focus areas
Information Technology, Business Intelligence, Product Development
Bachelor's degree or higher
70% (Germany: 90%)
Master's degree or higher
30% (Germany: 55%)
Doctorate
10% (Germany: 6%)
Certifications per freelancer
1 (Germany: 3)
Most common languages
German, English, French
Speak two or more languages
92% (Germany: 98%)
Based on our profile pool as of 30 Aug 2026.
Daily rate distribution
The chart shows how the daily rates of freelancers in this technology in Hamburg are distributed, based on recent contracts on our platform. Each bar covers a rate range — its height shows how many freelancers charge within that range.
Average rates of experts in Hamburg using GitLab CI/CD
Rates are based on recent contracts and do not include FRATCH margin.
The average daily rate is the mean of all daily rates from recent contracts of comparable freelancers on our platform.
The median daily rate is the middle value of all daily rates — half of comparable freelancers charge less, half charge more. Unlike the average, it is barely affected by outliers.
Calculated based on our freelancers’ daily rates as of 30 Aug 2026. Actual rates may vary depending on seniority level, experience, skill specialization, project complexity, and engagement length.
About the technology
Pipeline delivery
GitLab CI/CD is used to automate build, test, and deployment work inside GitLab. It helps teams turn code changes into repeatable release steps, from simple validation to full delivery flows. Companies bring in specialists when they need faster releases and fewer manual handoffs.
What it covers
- CI pipelines for code checks and test runs
- CD flows for staged or direct deployments
- Merge request rules, approvals, and quality gates
- Environment handling, secrets, and release triggers
Core setup
Strong professionals know .gitlab-ci.yml, GitLab Runner, artifacts, caches, variables, and environment scopes. They also understand how to structure jobs so pipelines stay clear and easy to maintain. In Hamburg, this often matters for product teams that work across office and remote setups.
Ecosystem fit
GitLab CI/CD fits closely with the rest of GitLab: source control, issues, merge requests, security scans, and container workflows. It is often compared with GitHub Actions, Jenkins, and Azure DevOps when companies choose a delivery setup. The best specialists can explain tradeoffs without forcing one tool everywhere.
When to bring in help
Companies usually ask for freelance expertise when pipelines become slow, fragile, or hard to review. Common reasons include migration from Jenkins, a release process that needs tighter control, or a new product line that needs clean delivery from day one.
What good work looks like
A strong specialist leaves behind pipelines that are readable, secure, and easy to extend. They document runner setup, job logic, and deployment steps, and they remove duplication where possible. The result is a delivery flow teams can keep using without constant cleanup.
Frequently asked questions
Everything clients usually want to know about GitLab CI/CD, in one place.
GitLab CI/CD is used to automate the path from code change to tested release. It usually covers build steps, automated tests, packaging, and deployment to one or more environments. For many teams, it becomes the main way to keep releases consistent and reviewable.
GitLab CI/CD is often chosen when teams want source control, merge requests, and delivery automation in one place. Jenkins is more flexible but can take more upkeep, while GitHub Actions is strong if the code already lives in GitHub. The right choice depends on how much control, standardization, and admin work you want.
A strong GitLab CI/CD specialist usually knows Linux basics, YAML, Docker, and deployment patterns for web apps or services. Security handling matters too, especially for variables, tokens, and environment separation. If the setup uses Kubernetes or cloud targets, that experience is very useful.
You do not need a huge platform to justify help with GitLab CI/CD. Teams often bring in a freelancer when they are moving from manual releases, adding more services, or cleaning up a pipeline that has grown too complex. The key signal is not size; it is whether the delivery flow is becoming hard to trust.
Yes. GitLab CI/CD works well when people collaborate across Hamburg and remote locations because the pipeline gives everyone the same release process and the same checks. Clear naming, good documentation, and stable runners matter even more when the team is not always in one room.
Look for clarity, not just working pipelines. A good GitLab CI/CD expert writes jobs that are easy to read, avoids duplicate logic, and can explain why each stage exists. They should also think about security, rollback paths, and how future changes will be handled.
For many real projects, GitLab CI/CD and GitLab Runner go together. A freelancer who understands both can diagnose why jobs run slowly, why executors behave differently, or why builds fail in one environment but not another. If your setup is simple, basic CI knowledge may be enough; for self-managed runners, deeper runner experience helps.
The most common problems are messy YAML, unclear stages, poor cache use, and secrets handled too loosely. GitLab CI/CD works best when the pipeline is built in small steps and reviewed like any other important code. A good specialist will simplify the first version so the team can maintain it later.
The average hourly rate of freelancers in Hamburg, Germany who have used GitLab CI/CD in their recent projects is 97 €, which corresponds to a daily rate of about 775 € based on an 8-hour working day.
Of the freelancers in Hamburg, Germany who have used GitLab CI/CD in their recent projects, 70% hold at least a Bachelor's degree, 30% hold at least a Master's degree, and 10% hold a doctorate.
On average, freelancers in Hamburg, Germany who have used GitLab CI/CD in their recent projects have 20 years of professional experience, with a single engagement typically lasting around 2.3 years.
The most common languages among freelancers in Hamburg, Germany who have used GitLab CI/CD in their recent projects are German (100%), English (92%), and French (15%).
The most common industries among freelancers in Hamburg, Germany who have used GitLab CI/CD in their recent projects are Information Technology (100%), Transportation (54%), and Professional Services (46%).
The most common business areas among freelancers in Hamburg, Germany who have used GitLab CI/CD in their recent projects are Information Technology (100%), Product Development (85%), and Business Intelligence (77%).
Main locations of FRATCH Experts, who have recently used GitLab CI/CD
Our freelancers and interim experts are at home across the DACH region — available on-site in the major business hubs or fully remote. Choose a location to discover matched specialists, local market insights and up-to-date availability.
Request a free demo
Get in touch with the FRATCH team and we will get back to you within 4 hours.
Would you rather directly get in touch?
We always have the time for a call or email!

Berlin
Munich
Cologne
Frankfurt
Stuttgart
Dusseldorf
Leipzig
Hanover