
JWT Experts in Munich
matched in minutes by AIHire experts who design token-based authentication, integrate OAuth 2.0 and OpenID Connect, and secure APIs for web and mobile products. FRATCH connects you with vetted, available freelancers through fast, precise AI matching.
Meet FRATCH Experts in Munich, who have recently used JWT
Ales L.
Last position:
Senior DevOps Consultant (Freelance) at European Union Agency (via IBM)
- Worked as freelance Senior DevOps Consultant on-site for IBM at a European Union Agency, operating in a highly secure, air-gapped environment managing classified systems.
- Led automation and DevOps initiatives for a large-scale OpenShift platform (>400 nodes), driving deployment efficiency, GitOps adoption, and operational automation using Ansible, Python, and Bash while ensuring compliance with security requirements.
- Spearheaded automation of release and deployment workflows in a private cloud environment hosting 400+ OpenShift nodes, significantly improving deployment speed and reliability.
- Migrated existing playbooks, roles, and templates from Ansible Tower to Ansible Automation Platform (AAP), ensuring full compliance with fully-qualified collection names (FQCN) and preparing custom Execution Environments (EE) for containerized automation.
- Implemented GitOps Agent for AAP Controller Configuration as Code, enabling automated synchronization (CRUD) of Ansible Controller objects based on repository-stored configuration definitions using GitHub webhooks.
- Designed and automated complex multi-step operational workflows including environment cleanup, Helix cluster component re-creation, Kafka topic management, and OpenShift object lifecycle management across ~100 environments.
- Achieved a reduction of multi-day manual operations to under a few hours through automation improvements spanning multiple AAP clusters and OpenShift environments.
- Integrated Ansible Automation Platform with Thycotic (Delinea) Secret Server via lookup plugin to enhance secure credential management in automated processes.
- Managed deployment tasks, platform troubleshooting, and Istio network configurations while adhering to stringent EU PSC security and compliance standards.
- Collaborated with infrastructure and application teams to refine deployment procedures, develop naming conventions, and continuously improve automation coverage in an air-gapped, classified environment.
Karen M.
Last position:
Personal AI Engineering Project — Croky AI at Crocky AI
Product:
- Built a production-ready AI platform for generating brand-aware marketing images and videos from product data, user requirements, and uploaded media.
- Own the platform architecture, technical roadmap, API design, security, deployment workflow, operational reliability, and model-provider strategy.
- Developed the core platform in .NET and built supporting AI and workflow prototypes in Python, applying language-independent API contracts and structured interfaces between services and model providers.
- Implemented reliable background processing with RabbitMQ, persisted workflow state, idempotent handling, retries, failure recovery, logging, secure storage, authorization, and credit accounting.
- Made pragmatic build-versus-buy and model-routing decisions based on reliability, latency, cost, and maintainability rather than novelty.
Agent Orchestration & RAG Systems
- Built and compared agent workflows using Microsoft Agent Framework, LangGraph, and LangChain, including tool use, conditional routing, clarification steps, state management, and hand-offs between agents.
- Implemented reusable .NET components for agents, prompts, tools, model providers, structured responses, and retrieval with pyvector, making it easier to change AI providers without rewriting the core workflow.
Fred H.
Last position:
Software Architect and Developer at Personal project
Recurring problem in my own AI-assisted projects: requirements analysis, use cases, and architecture decisions can be created quickly with AI support, but remain difficult to follow and scattered across Markdown files – knowledge is lost as soon as it is no longer in the context window. arknet turns requirements engineering and architecture knowledge into structured, verifiable data instead of plain text: requirements, use cases, and architecture decisions form a consistently linked knowledge graph, traceable from requirement to architecture decision – queryable by both people and AI agents. Technically based on RDF/OWL and a custom MCP server.
Result: Working MCP daemon, Docker image published automatically to GHCR, nine hexagonal modules, eleven ADRs (including an Open-Core licensing model). Requirements engineering and Ubiquitous Language hexagons are active. Public as a Community Edition under Apache-2.0 since 07/2026 (github.com/kogn-io/arknet), together with the Claude Code plugin and GHCR image; Open-Core model.
Label: Java, Maven, RDF, RDF4J, OWL, SPARQL, Model Context Protocol, Spring AI, Docker, GitHub, Git, Claude Code, Obsidian, DDD, Hexagonal Architecture, ArchUnit, JUnit, AssertJ, Interface Development, Software Architecture, Continuous Integration, Knowledge Management
Marcus B.
Last position:
Java and Quarkus Expert at Large German energy service provider
- Modernization of a large-scale Java enterprise application*
The project is modernizing a complex enterprise application that has grown over many years. The existing Spring-based legacy system runs on Java 8, OSGi, and Eclipse RCP and is being gradually migrated to a modern, maintainable architecture with Java 25 and Quarkus.
Marcus works on analysis, architecture, refactoring, and implementation. One focus is on untangling historically grown structures and dependencies and on building a clean, sustainable Java and Quarkus technology stack.
Tools & technologies: Java 8, Java 25, Quarkus, Hibernate ORM with Panache, EclipseLink, OSGi, Eclipse RCP, Maven, JUnit, Mockito, REST, JSON, Git, Eclipse IDE, IntelliJ IDEA Ultimate, Jira, Confluence
Thomas H.
Last position:
Senior MLOps, DevOps Engineer at Trianel Energy
- Build and operate an end-to-end MLOps platform on Azure ML and Kubernetes (Kubeflow) for the automated deployment, monitoring, and scaling of forecasting models (including Temporal Fusion Transformer, Informer, Autoformer).
- Implement CI/CD pipelines in Azure DevOps for the full ML lifecycle – from resource provisioning (Terraform), data transformation (Hugging Face Datasets, Pandas, PyTorch, CUDA cluster) through training and evaluation to model registry and endpoint deployment.
- Integrate MLflow for experiment tracking, model versioning, performance monitoring, and automated registration in the Azure Model Registry.
- Develop and containerize PyTorch training jobs (Azure Notebook, Jupyter Notebooks) for price and time series forecasting (PFC models) with automatic rollout via Azure ML Endpoints and REST/gRPC interfaces, Docker containerization, secured with OAuth 2.0.
- Set up monitoring and alerting mechanisms (Prometheus, MLflow Metrics), log centralization, and cost monitoring.
- Automate infrastructure provisioning and model deployment using Terraform, Helm, and Azure CLI; connect to existing market data systems and event pipelines.
- Migrate existing workloads and databases (IONOS → Azure, MongoDB) with integration into central MLOps workflows and internal networks.
- Extend the platform with LLM-based tools (LangChain, LangServe) to integrate GPT-based analysis modules into existing Spring Boot services for market anomaly detection and automated reports.
- Analyze and architect a software solution to process large volumes of data efficiently (>3000 messages/sec.) (market data store).
- Spring Boot / Java 21 container development with RabbitMQ for distributing stock market data via MongoDB (Kubernetes) with fast storage of data in Redis RMaps, deduplication, forwarding messages to Read Model queues, and building Read Models for UI display in MongoDB.
- Integration of RESTHeart to create a REST API for MongoDB.
- Build an Angular frontend to simplify data queries and master data maintenance.
- Agentic coding with remote and local LLMs (Claude Sonnet, Ollama Qwen) and MCP servers.
- Develop Python scripts for transforming and cleaning incoming stock market data (Pandas, scikit-learn).
Srinivasu K.
Last position:
Atruvia
Project: Tax Exemption Order Application
The client has an existing application for creating and maintaining tax exemption orders for end customers; design and implementation of a comparable application for internal employees.
- Design and implementation of microservices and the UI for the business area "tax exemption orders" using Domain Driven Design as well as Spring Boot and Angular.
- Implementation of reactive, non-reactive, and asynchronous APIs (Spring REST, WebFlux, GraphQL).
- Development of the Angular application, including state management using Signals, RxJS Observables, and subscriptions.
- Securing the API and the application using OAuth2, JWT, and OpenID Connect.
- Configuration and setup of CI/CD pipelines with Jenkins.
- Collaboration with cross-functional teams and conducting code reviews.
Environment: Java, Spring Boot, Angular 18 & 19 (standalone, signals), RxJs, Bootstrap CSS, Vitesting, OpenShift, Istio, microservices, Kafka, Dynatrace, Jenkins, GitLab, Graylog, Sonar, Oauth2, OracleDB
Serge K.
Last position:
MLOps (machine learning operations) at REWE Digital GmbH
- It is like a startup within REWE, where we have to build a new forecasting system on Google Cloud Platform from the scratch. Although, officially my role is called MLOps, my actual tasks also include development of data processing pipelines (data engineering) and data scientists tasks such as feature engineering and model trainings.
- GCP: Terraform (tofu), Vertex AI (Kubeflow), Cloud Run, IAM, Google Cloud Storage, BigQuery, Artifact Registry
- Data engineering: Snowflake as the main data warehouse, Terraform, DBT for data model implementations
- CI/CD: GitLab. We have built a CI/CD pipeline that automates deployments of new releases up to production environment
Enis S.
Last position:
Software Developer at 50Hertz Transmission GmbH
- Participated in the gradual modernization of components into cloud-native 12-factor applications.
- Worked closely with the business operations team to eliminate manual processes and resolve several performance bottlenecks.
- Designed and implemented a CI/CD pipeline to increase developer productivity, enforce quality and security checks, and automate product delivery.
- Migrated several components into the OpenShift Kubernetes cluster.
- Built a monitoring stack from scratch with Prometheus and Grafana to monitor services running in OpenShift.
- Developed dashboards in both Grafana and Splunk for operational transparency.
- Implemented an OIDC/OAuth2-based single sign-on (SSO) solution with Keycloak to secure multiple applications.
- Technologies: Java, Spring, Quarkus, Kafka, MySQL, Cassandra, Redis, Spring Data, Hibernate, Docker, Kubernetes, OpenShift, Keycloak, OIDC, OAuth2, Helm, Prometheus, Grafana, Splunk, Spark.
Alois F.
Last position:
Software Architect / Backend Developer at GEO API
- Design and implementation of a Laravel backend API for provider-based geo search, feature details, boundary geometries and neighborhood detection.
- The API serves as a server-side proxy, cache and enrichment layer, protecting credentials for external geo services and persisting features, localizations, geometries, hierarchies and neighborhood relationships in MariaDB.
- Key areas included normalization of autocomplete and feature data, caching strategies for expensive boundary/polygon requests, spatial processing of GeoJSON and MultiPolygon geometries, as well as neighborhood detection using hierarchies, bounding box filters and topology checks.
- Additionally, separate production and diagnostic endpoints were created, along with status and error catalogs, discovery logging, a Docker development stack, API documentation, and unit and feature tests.
- Technologies: PHP 8.3, Laravel, REST API, geo data API, GeoJSON, MariaDB Spatial, Eloquent, Laravel Queues, PHPUnit, Mockery, Docker, Docker Compose, API design, geocoding, boundary data, spatial queries.
Stephan S.
Last position:
Senior Data/ML Consultant & Technical Lead at Jolin.io
Role: Software Engineer & Applied Mathematician (Mathematical optimization for scheduling; duration: 1 months; team setting: Team of 2, remote; technologies: JuMP, Julia, Pluto, Svelte, JavaScript, TypeScript, JetBrains Space, Terraform, Nomad)
Role: Software & Cloud & Web Engineer (Building scalable data science compute cluster from scratch; duration: 11 months; team setting: Team of 1, on-site; technologies: Terraform, Kubernetes, k8s ingress, k8s services, k8s RBAC, k8s networking, k3s, etcd, S3, DNS, certificates, Julia, Pluto, JavaScript, Tailwind, Astro, npm, Parcel, Preact, MUI, JWT, AWS SQS, AWS RDS, Python, GitLab, GitHub)
Role: AI & Web Engineer (Custom ChatGPT service; duration: 1 months; team setting: Team of 2, remote; technologies: Python, Poetry, LangChain, Tailwind, ChatGPT API, Flask, FastAPI)
Role: Architect & Data Engineer (Central datalake setup and ingestion; duration: 9 months; team setting: Team of 5, remote; technologies: Infrastructure-as-code, AWS CDK, Python, Boto3, PySpark, AWS Glue, IAM, S3, ECS, Fargate, Lambda, Apache Hudi, DeltaLake, Databricks, GitHub, Jira, Miro)
Role: Software Engineer (PoC Julia migration of scikit-decide; duration: 1 months; team setting: Team of 2, remote; technologies: Python, Julia, GitHub)
Bela B.
Last position:
Full Stack Lead Developer, Backend Architect at Telefonica (O2)
The software supports the complete planning and approval of antennas for mobile telephony.
The system was implemented using an event-driven microservice architecture for cloud-native deployment with Quarkus on the backend, Kafka for communication, and Angular for the frontend. Services run on Kubernetes in Google Cloud. A special challenge was synchronizing with the legacy system still used by some users.
Mario V.
Last position:
Freelance Developer at Centrotherm International AG
- Did a complete rewrite of centrotherm.de with Next.js, migrating from Gatsby
- Built a system to automatically generate printable product datasheets
- Technologies: React, TypeScript, Storybook, SASS, Next.js, I18n
Janusz M.
Last position:
IoT Edge Computing / Self-Driving-Cars at Automotive consulting company
- Platform: Python ecosystem, RHEL 8, K10, AWS IoT Core, AWS Lambda, MLOps
- Software: Java JEE/cloud, IntelliJ IDEA, AWS IoT Core, AWS Edge and Lambda, AWS SageMaker SDK, Docker Compose, Kubernetes, OpenShift 4, Tekton, Flux, Helm charts, JSON/XML technology, Nginx, Apache Spark, OpenAI (GPT Plus, DALL-E 3, Whisper), GAN, GitHub Copilot, AI/machine and deep learning, Jupyter notebooks, TensorFlow 2, Colab, Keras API, Prometheus, Grafana, Conda, Python 3.9, PySci stack (NumPy, pandas, Scikit-learn, matplotlib)
- Responsible for webinar:
- IoT edge computing: architecture, components, resources, management
- IoT edge computing with MicroK8s, designing and creating flows/diagrams for AWS, three-step model for IoT ecosystem
- IoT processes, connectivity, data transfer and deployment, security
- Optimization of edge computing for IoT networks and services (AWS SQS queue, SNS notifications, events, analytics, buttons, device management/defender, Things Graph)
- Machine/deep learning frameworks (models, training, pipeline optimization, deployment in the cloud/at the edge (OpenShift), monitoring workloads with Prometheus and Grafana)
- Performance optimization for low latency/resilience using adaptive ML/DL/RL models for customer IoT data
- Analysis of large sensor data sets with Apache Spark, Kafka clusters
- Kasten K10 data management platform on Kubernetes multi-cluster with Helm chart, deployment, backup/disaster recovery (RTO/RPO), data lifecycle and security management
- Implementation of multilayer artificial neural network (ANN) with TensorFlow 2 and Colab for regression and classification; data analysis and provisioning for applications; development of models for testing and training, deployment of models
- Automation of business streamline processes with AI (Azure OpenAI, Discord bots/Zapier apps AI assistants (IntelliJ, GitHub Copilot))
Discover over 15,000 top freelancers
Statistics of experts using JWT
Aggregated from the professional profiles of matched freelancers.
Experience
23 years (Germany: 17 years)

Position duration
1.8 years (Germany: 2.7 years)

Positions per freelancer
14 (Germany: 13)

Top business areas
Information Technology, Product Development, Operations

Top industries
Information Technology, Automotive, Media and Entertainment

Certification focus areas
Information Technology, Project Management, Business Intelligence
Bachelor's degree or higher
100% (Germany: 86%)
Master's degree or higher
80% (Germany: 53%)
Doctorate
20% (Germany: 5%)

Certifications per freelancer
2 (Germany: 3)

Most common languages
German, English, Spanish

Speak two or more languages
100% (Germany: 98%)
Based on our profile pool as of 19 Sep 2026.
Daily rate distribution
The chart shows how the daily rates of freelancers in this technology in Munich 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 Munich using JWT
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 19 Sep 2026. Actual rates may vary depending on seniority level, experience, skill specialization, project complexity, and engagement length.
JWT 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%)
- Automotive (54%)
- Media and Entertainment (54%)
- Retail (54%)
- Banking and Finance (46%)
- Insurance (46%)
- Energy (38%)
- Government and Administration (38%)
Please note that freelancers can work across multiple industries, so percentages overlap.
About the technology
What JWT does
JSON Web Token, usually called JWT, is a compact format for carrying signed claims between parties. It is widely used for stateless authentication and authorization in web applications, mobile apps, microservices and APIs. A token can identify a user, describe permissions and prove that data was issued by a trusted service.
Core token flow
A client authenticates with an identity service and receives an access token. It sends that token with later requests, while the receiving service verifies its signature, issuer, audience and expiry before granting access. Strong implementations also handle refresh tokens, revocation, clock differences and secure storage on the client.
Ecosystem and tooling
JWT work often sits beside OAuth 2.0 and OpenID Connect rather than replacing them. Professionals use libraries for Java, Spring Security, Node.js, .NET, Python, Go and other runtimes, together with identity services such as Keycloak, Auth0 or cloud-based identity providers. They also configure JWKS endpoints, RSA or EC keys, claims policies and API gateways.
- Define claims, scopes, issuers and audiences
- Implement signing, validation and key rotation
- Connect single sign-on and external identity providers
- Test expiry, tampering, replay and privilege boundaries
Where companies use it
Companies use JWT for single-page applications, native mobile clients, partner APIs and service-to-service communication. It supports distributed systems because services can validate a signed token without checking a central session store on every request. In Munich, it is relevant to product teams across software, manufacturing, finance and mobility that connect internal and external services.
When to bring in expertise
Freelance expertise helps when authentication is being introduced, migrated or audited, especially across several services or identity providers. It is also valuable during an OAuth 2.0 rollout, a monolith-to-microservices transition, an API gateway project or an incident involving leaked tokens. Munich teams may work remotely with specialists or combine remote delivery with on-site workshops; clear English or German communication should be agreed early.
- Review an existing token design and threat model
- Separate access, refresh and identity token responsibilities
- Reduce excessive claims and unnecessary token lifetime
- Document integration decisions for application teams
What strong specialists deliver
Strong professionals understand cryptographic signing without treating JWT as encryption. They choose suitable algorithms, validate every security-relevant claim and keep secrets and private keys out of application code. They also explain trade-offs: stateless tokens can simplify scaling, but revocation, logout and immediate permission changes need deliberate design. Quality shows in threat-focused tests, useful logs, key rotation procedures and clear integration guidance.
Frequently asked questions
Quick answers to the questions that come up most around JWT.
JWT is used to carry signed claims between an identity service and an application or API. It commonly supports authentication, authorization, single sign-on and service-to-service access without storing a server-side session for every request.
JSON Web Token authentication can scale conveniently across distributed services because each service can validate a token locally. Server-side sessions make revocation and logout control more direct, so the right choice depends on architecture, risk, token lifetime and operational needs.
JWT is a token format, while OAuth 2.0 is an authorization framework and OpenID Connect adds an identity layer on top of OAuth 2.0. OAuth access tokens may use JWT, but they can also use another format, so the terms should not be treated as interchangeable.
A strong JWT specialist should understand OAuth 2.0, OpenID Connect, TLS, API gateways and identity providers. Experience with secure key storage, JWKS, role and scope design, frontend token handling and automated security testing is also valuable.
The required level depends on the risk and integration scope, not simply on the presence of JWT. A basic API integration may need focused implementation expertise, while several identity providers, microservices, compliance requirements or an incident call for a specialist who can lead architecture and threat review.
Yes. JSON Web Token projects are well suited to remote collaboration when repositories, test environments, identity-provider access and security decisions are documented. Teams in Munich should define expectations for English or German communication, working hours and any on-site workshops before the engagement starts.
Common JWT mistakes include accepting an unexpected signing algorithm, skipping issuer or audience checks, putting sensitive data in claims, using long-lived access tokens and storing tokens unsafely in a browser. Weak key management and missing refresh-token protection can turn a contained credential leak into broader access.
Ask the JWT professional to explain the trust model, key lifecycle, validation rules, revocation approach and failure handling in plain language. Review threat-model coverage, negative tests, audit logs, documentation and whether the design limits claims and permissions to what each service actually needs.
The average hourly rate of freelancers in Munich, Germany who have used JWT in their recent projects is 101 €, which corresponds to a daily rate of about 804 € based on an 8-hour working day.
Of the freelancers in Munich, Germany who have used JWT in their recent projects, 100% hold at least a Bachelor's degree, 80% hold at least a Master's degree, and 20% hold a doctorate.
On average, freelancers in Munich, Germany who have used JWT in their recent projects have 23 years of professional experience, with a single engagement typically lasting around 1.8 years.
The most common languages among freelancers in Munich, Germany who have used JWT in their recent projects are German (100%), English (92%), and Spanish (23%).
The most common industries among freelancers in Munich, Germany who have used JWT in their recent projects are Information Technology (100%), Automotive (54%), and Media and Entertainment (54%).
The most common business areas among freelancers in Munich, Germany who have used JWT in their recent projects are Information Technology (100%), Product Development (100%), and Operations (62%).
Main locations of FRATCH Experts, who have recently used JWT
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
Frankfurt