
OpenTelemetry Expert in Berlin
for reliable observability, matched in minutes with vetted freelancersHire experts who instrument distributed systems, standardize traces, metrics and logs, and connect telemetry to tools such as Jaeger, Prometheus and Grafana. FRATCH matches you quickly and precisely with vetted, available freelancers.
Meet FRATCH Experts in Berlin, who have recently used OpenTelemetry
Julius H.
Last position:
Freelancer at Freelancer — Pharma Industry
- Led migration to GCP using Terraform, GKE, and GitOps, improving deployment consistency and scalability
- Implemented Datadog observability stack via Terraform and datadog-operator
- Established automated end-to-end tests and on-call processes, improving incident response and service reliability
- Migrated from NGINX Ingress Controller to Kubernetes Gateway API (NGINX Gateway Fabric)
- Migrated stateful services (PostgreSQL and Redis) to GCP, improving scalability and operational reliability
Jorge N.
Last position:
Senior Developer at NDA
AI Platform Backend – Senior Developer
Hired to design and build an AI platform backend from the ground up, including multi-provider LLM orchestration and real-time infrastructure for AI influencer personas at scale.
Tasks and Responsibilities
- Architected and implemented a multi-LLM orchestration layer with Semantic Kernel to integrate GPT-4 and other providers for core platform logic and AI influencer personas, reducing model-switching overhead by abstracting provider APIs behind a unified interface.
- Designed and developed a backend from the ground up in C# / .NET 10, including domain modeling with DDD, a versioned RESTful API layer, and cloud infrastructure on Azure.
- Built real-time chat infrastructure with Server-Sent Events (SSE), message persistence, and delivery guarantees for running AI influencer personas live at scale.
- Developed a media management service with cloud object storage integration for uploading and retrieving influencer-generated content.
- Created an integration and unit test suite with data seeding for reliable regression testing across all core platform flows, significantly reducing the production error rate.
Tools and Technologies: C#, .NET, ASP.NET Core, Python, TypeScript, MySQL, Semantic Kernel, EF Core, Minimal APIs, LLM Orchestration, Prompt Engineering, Agentic AI, Generative AI, AI-Assisted Engineering, Claude Code, GitHub Copilot, Google Gemini, OpenAI API, Ollama, Redis, Azure, Azure Container Apps, Azure Database for MySQL, Docker, GitHub Actions, Clean Architecture, Vertical Slice Architecture, CQRS, Domain-Driven Design, REST API, xUnit, Integration Testing, Unit Testing, Jira, Confluence, Scrum
Caleb C.
Last position:
Senior Python Backend Engineer at Simon-Kucher
Transmission system operator – network provisioning platform (team lead)
- Designed the saga orchestrator in Python that provisions network fabrics with rollback.
- Split IP, identity, and resource allocation into bounded contexts with their own databases and typed clients.
- Implemented data access using DDD repositories and units of work, with no SQL in the domain code.
- Required integration tests using real PostgreSQL and RabbitMQ containers, and API fuzzing for every service.
- Introduced an agent workflow where a spec starts each change and a human approves every merge.
- Rolled out OpenTelemetry auto-instrumentation through GitOps across eighteen Kubernetes clusters.
- Led incident response for stuck provisioning and recorded every outage as a post-mortem.
Languages and software used: Python, FastAPI, Pydantic v2, SQLAlchemy async, PostgreSQL, RabbitMQ, Celery, pytest, testcontainers, schemathesis, Helm, Flux CD, GitLab CI, OpenTelemetry, pi coding agent.
Software product company – datacenter simulation SaaS (backend development)
- Built the asynchronous simulation pipeline as the second-largest contributor among more than twenty team members.
- Tagged every image by commit SHA and semver in the GitHub Actions deployment workflows.
- Diagnosed the RabbitMQ memory alarm that froze every simulation and fixed the limits in the Helm chart.
- Converted the test suite to function-style pytest, with coverage reported in every pipeline.
Languages and software used: Python, FastAPI, SQLAlchemy, Alembic, Celery, RabbitMQ, Redis, PostgreSQL, S3, EKS, Helm, Keycloak, GitHub Actions, pytest, mypy, ruff, SonarQube.
Internal AI platform – model serving and telemetry
- Built the FastAPI service that deploys open-weight models on GPU tiers as OpenAI-compatible endpoints.
- Upgraded production EKS by two Kubernetes minor versions and fixed zone-bound storage faults.
- Traced every model call, including its token count, cost, and latency, through the OpenTelemetry operator.
Languages and software used: Python, FastAPI, vLLM, LangGraph, pydantic-ai, OpenAI and Anthropic APIs, EKS, Helm, Flux CD, Terraform, GitLab CI, OpenTelemetry, Grafana.
Hamza K.
Last position:
Academic Research Contributor in Health Sector (Volunteer) at n/a
- Acted as technical consultant to optimize multi-layer ensemble models combining ResNet, CNN-BiGRU-Attention, and XGBoost.
- Guided implementation of a Logistic Regression meta-learner to solve class imbalance problems, achieving 92.86% accuracy and 0.9644 AUC on PTB-XL and Chapman-Shaoxing datasets.
Qaiser A.
Last position:
Freelance Lead DevOps Engineer at Schwarz Gruppe Produktion
Bootstrapping a CloudOps team and building a multi-cloud provider backend for a low-code Internal Developer Platform (IDP) with env zero
Introducing user story mapping, ADRs, milestones, and backlog management
Designing and developing core APIs, setting up CI/CD pipelines, OpenTofu/Terraform scripts
Representing and communicating the team with third-party stakeholders (e.g. env zero)
(Cross-)team coaching on DevOps, software design, Terraform, Golang, and agile practices
Karthikeyan R.
Last position:
Full-Stack Developer — Own Product at Self-employed
Java 21 · Spring Boot 3 · Keycloak · PostgreSQL · Docker · Nginx · GitHub Actions · DigitalOcean · React 18 · TypeScript · Plasmo
- Architected and shipped a production-ready Job Application Tracker end-to-end: REST API with 5-stage workflow, pagination, sorting, and dynamic filtering — full ownership from design to live cloud deployment on DigitalOcean.
- Implemented production-grade identity management: OAuth 2.0 / OpenID Connect / JWT / RBAC via Keycloak, applying Hexagonal Architecture and DDD principles.
- Built automated CI/CD pipeline (GitHub Actions); containerised with Docker; Nginx reverse proxy with path-based routing and SSL termination.
- Developed a Chrome Extension (Plasmo framework, Manifest V3) that auto-fills job applications directly from LinkedIn into the tracker — demonstrates full product thinking across backend API and browser client.
Shriya S.
Last position:
Product Manager at passify
- Leading the setup of Passify’s internal automation and risk management portal, connecting workflows across teams through SharePoint and Power Automate.
- Moderating retrospective workshops and creating PRDs and design tickets during PDLC.
- Supporting ISO 27001 documentation and compliance, focusing on customer support, user registration, and internal communication processes.
- Helping align design, development, and operations in a modular design cycle, ensuring each release meets both business and user needs.
- Contributing to feature planning and validation for subcontractor flows, training dashboards, and terminal portal improvements.
Amogha S.
Last position:
Senior Product Manager - OS, platform, IAM at Aleph Alpha GmbH
- Leading the product lifecycle for sovereign AI platform and operating system teams for enterprise & government clients and internal stakeholders (infra, solution delivery, support, revenue)
- Built and scaled the platform from a 200-user beta to a full rollout of 70K+ members at the Bundesagentur für Arbeit (BA), secured with ISO 42001 and EU AI Act compliance
- Architected the shift to a multi-tenant shared inference, increasing GPU cluster utilization from 20% to 85% and reducing infrastructure cost-to-serve by 40% for SaaS clients
- Shipped model quantization, allowing clients to run advanced LLMs on legacy hardware (A100s GPUs) instead of the H100s, saving upwards of 70% cost per enquiry
- Abstracted complex Helm configurations into a dynamic model manager, reducing the time to install or swap models by ~80%
- Killed an expensive move to build own dashboard service, pivoting to an API-first data strategy that clients can consume directly and saving €100Ks in opex and capex
- Built a safety-first agent marketplace and control plane lighthouse project for a Tier-1 bank, allowing internal teams to deploy autonomous agents within strict regulatory guardrails
Kalpesh P.
Last position:
Intern Java Developer at Unzer GmbH
- Developed a Proof of Concept for distributed tracing using OpenTelemetry within a microservices architecture, enhancing system observability and reducing mean-time-to-resolution for issues.
- Built and maintained backend services using Java and Spring Boot, ensuring high reliability and performance for payment transaction workflows.
- Implemented comprehensive automated testing with JUnit and Mockito, achieving 95% test coverage to ensure code quality and maintainability.
- Gained insight into payment transaction workflows, validating end-to-end system reliability and gaining domain knowledge in financial processes.
- Tech used: Java, Spring Boot, Microservices, REST API, Kafka, Grafana, Datadog, Docker, MongoDB
Discover over 15,000 top freelancers
Statistics of experts using OpenTelemetry
Aggregated from the professional profiles of matched freelancers.
Experience
13 years

Position duration
1.8 years

Positions per freelancer
8

Top business areas
Information Technology, Product Development, Operations

Top industries
Information Technology, Banking and Finance, Education

Certification focus areas
Information Technology, Project Management, Quality Assurance
Bachelor's degree or higher
100%
Master's degree or higher
71%

Certifications per freelancer
1

Most common languages
German, English, Spanish

Speak two or more languages
100%
Based on our profile pool as of 29 Oct 2026.
Daily rate distribution
The chart shows how the daily rates of experts in this technology in Berlin are distributed, based on recent contracts on our platform. Each bar covers a rate range — its height shows the share of experts charging within that range.
Average rates of experts in Berlin using OpenTelemetry
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 29 Oct 2026. Actual rates may vary depending on seniority level, experience, skill specialization, project complexity, and engagement length.
OpenTelemetry experts industry focus
See which industries our matched freelancers work in most often — every figure is calculated live from the freelancers on FRATCH.
- Information Technology (100%)
- Banking and Finance (67%)
- Education (44%)
- Healthcare (33%)
- Professional Services (33%)
- Retail (33%)
- Automotive (22%)
- Cosmetics (22%)
Please note that freelancers can work across multiple industries, so percentages overlap.
About the technology
What OpenTelemetry does
OpenTelemetry is an open-source observability framework for generating, collecting and exporting traces, metrics and logs. Its vendor-neutral APIs, SDKs and protocols help teams understand requests as they move through services, queues, databases and external systems. OTel is the common shorthand used across its documentation and community.
Instrumentation scope
Professionals use OpenTelemetry to add consistent telemetry to applications and infrastructure without tying the codebase to one monitoring vendor. They configure context propagation, sampling, resource attributes and semantic conventions so teams can connect a user action to the services and dependencies behind it.
- Trace HTTP, messaging and database operations
- Capture application metrics and structured logs
- Propagate context across asynchronous services
- Control sampling and telemetry cost
Ecosystem and tooling
The OpenTelemetry Collector receives, processes and routes telemetry through receivers, processors, exporters and connectors. Specialists often work with language SDKs, automatic instrumentation, OTLP, Jaeger, Prometheus, Grafana and cloud observability services. They also understand Kubernetes, service meshes and the deployment patterns that affect signal quality.
When expertise matters
Companies bring in freelance expertise when observability is fragmented, outages are hard to investigate or a migration from proprietary agents is under way. Strong professionals can define a telemetry strategy, instrument legacy services and make signals useful across development, operations and security teams.
- Replace inconsistent tracing libraries with OpenTelemetry
- Design Collector pipelines for multiple environments
- Diagnose missing spans, broken context or noisy metrics
- Prepare dashboards, alerts and handover documentation
What quality looks like
A capable specialist treats instrumentation as part of system design, not as decoration added after deployment. They preserve trace context across service boundaries, choose meaningful attributes, avoid sensitive data in telemetry and test exporters under failure conditions. They also explain trade-offs between detail, performance, retention and operational cost.
Working with a Berlin specialist
OpenTelemetry work often spans application teams, cloud infrastructure and observability owners, so clear communication matters as much as configuration skill. Berlin companies can choose on-site collaboration for architecture sessions or remote delivery for instrumentation and Collector work. German and English communication may both be relevant in distributed teams.
Frequently asked questions
Curious about OpenTelemetry? Here are the answers that come up again and again.
OpenTelemetry is used to generate, collect and export traces, metrics and logs from software and infrastructure. It helps teams follow requests across distributed services, investigate failures and measure system behavior with consistent telemetry.
OpenTelemetry combines the goals and technical foundations of OpenTracing and OpenCensus in one project. It offers a broader, actively maintained approach covering traces, metrics and logs, with vendor-neutral APIs, SDKs and the OTLP protocol.
A strong OpenTelemetry specialist usually understands distributed systems, service boundaries, Kubernetes, cloud infrastructure and CI/CD. Experience with Jaeger, Prometheus, Grafana, Collector pipelines and the observability backend in use is also valuable.
The right level depends on the scope. A small instrumentation task may need focused SDK and application knowledge, while a multi-service rollout requires someone who can design semantic conventions, context propagation, sampling, Collector pipelines and operational ownership.
Ask how the professional validates trace continuity, chooses attributes and handles sampling, retries and exporter failures. Good OpenTelemetry work produces useful signals without exposing sensitive data or creating unnecessary processing and storage overhead.
Yes. OpenTelemetry instrumentation, Collector configuration and documentation are well suited to remote collaboration when repositories, environments and observability goals are accessible. On-site workshops in Berlin can still help when several teams need to agree on telemetry standards.
OpenTelemetry rollouts often struggle with missing context propagation, inconsistent resource attributes, duplicate instrumentation and poorly designed sampling. Backend incompatibilities, blocked network paths and untested Collector pipelines can also make valid telemetry appear incomplete.
No. OpenTelemetry provides APIs, SDKs, instrumentation and collection components, but it is not itself a full storage, dashboard or alerting product. It exports telemetry to systems such as Jaeger, Prometheus, Grafana or a commercial observability service.
The average hourly rate of freelancers in Berlin, Germany who have used OpenTelemetry in their recent projects is 76 €, which corresponds to a daily rate of about 608 € based on an 8-hour working day.
Of the freelancers in Berlin, Germany who have used OpenTelemetry in their recent projects, 100% hold at least a Bachelor's degree and 71% hold at least a Master's degree.
On average, freelancers in Berlin, Germany who have used OpenTelemetry in their recent projects have 13 years of professional experience, with a single engagement typically lasting around 1.8 years.
The most common languages among freelancers in Berlin, Germany who have used OpenTelemetry in their recent projects are German (100%), English (100%), and Spanish (22%).
The most common industries among freelancers in Berlin, Germany who have used OpenTelemetry in their recent projects are Information Technology (100%), Banking and Finance (67%), and Education (44%).
The most common business areas among freelancers in Berlin, Germany who have used OpenTelemetry in their recent projects are Information Technology (100%), Product Development (89%), and Operations (56%).
Main locations of FRATCH Experts, who have recently used OpenTelemetry
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.
Countries:
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!
