JNDI Experts in Germany
in minutes from over 15,000 CVs with the power of AIHire experts who work with Java Naming and Directory Interface, LDAP lookups, JMS resources, and application server naming. Get fast, precise matching with vetted, available freelancers.
Meet FRATCH Experts in Germany, who have recently used JNDI
Wael Mansour
Last position:
Test Manager at Schwarz IT
- Design, planning, and test case analysis
- Integration testing
- Coordination of UAT in the lab and on site
- Creation of HW and SW test catalogs
- Communication of test results from REST services with the SAP team
- Support for branches in the EU until rollout
- Coordination of defect management and SW updates with the involved vendors
- Checking the configuration of the charging stations in the backend software for different countries
- Continuous reporting of the quality status to project management
- Documentation of the user manual in English and German
- Tools: Confluence, be.Energised, OCPP Postman, OPI, CCV (payone.elavon), Excel, it4you
Sridhar Huple
Last position:
SAP CX Consultant at Anonymous
- Stack: SAP Commerce 2011 (B2C).
- Migrating the data from Stibo system to SAP Commerce Cloud.
- Mapping the data from Stibo system to SAP Commerce Cloud.
- Integrating hot folders to support multiple countries and languages.
- Integrating validation tools for migrated data and generating validation reports.
Michael König
Last position:
Atruvia AG
- Further development of framework components and services in the Enterprise Banking Control Platform (EGP Framework), a set of cross-cutting libraries and services for all bounded context scopes of the platform.
- Migration from Java 17 to Java 21 and from Spring Boot 3.2 to 3.4 in about 80 library and service repositories (updating Maven POMs, Dockerfiles, Jenkins pipelines, source code migration, test updates).
- Writing unit and integration tests with JUnit and JGiven.
- Performing and analyzing performance measurements with Dynatrace.
- Enhancing multi-stage CI/CD pipelines (unit tests, security analyses, Docker builds, Harbor deployments, ...).
- Tech stack used: Java (90%), Python (10%), Spring Boot, JPA/Hibernate, JGiven, OpenAPI, Camunda 7, Podman, OpenShift/Kubernetes, Oracle DB, SonarQube, Dynatrace, Jenkins, Harbor, Bitbucket, Jira, Confluence.
Peter Neumann
Last position:
Pilot testing AI tools & sabbatical for house renovation
- Pilot testing local AI environments to explore local AI use cases and cloud-based AI solutions
- Evaluation of AI tools and techniques
- Use of local AI tools with own data sovereignty
- Prompt engineering
- Creation of example environments for speech-to-text, text-to-speech, text-to-image, text-to-video, and image-to-video
Tools: Grok, Perplexity, ChatGPT, Elevenlabs, Github, Ollama, HuggingFace, Open WebUI, Faster Whisper, LibreTranslate, WSL, Docker Desktop, Shotcut, Audacity, Sound eXchange, Ffmpeg, Coqui TTS, Pinokio, Stable Diffusion Web UI, ComfyUI, OWL, Void Editor
Ulrich Cech
Last position:
Java Architect/Developer – Freelancer at DHL/DP – Rentenservice
Implementation of a Java service (daemon) as part of the automated processing of death notifications
Technologies used: Java17, SpringBoot, Hexagonal Architecture, REST API, Oracle, Maven, SonarQube, FindBugs, Checkstyle
Jacqueline Haefke
Last position:
Kitchen Appliance Manufacturer
Setting up and enhancing an international subscription management system
Migrating and decommissioning a Hybris-SAP system and integrating Zuora
Implementing numerous interfaces to various systems (external and internal)
Setting up and improving monitoring with Grafana, Prometheus, and Databricks
Introducing logging with Loki
Implementing business requirements using jQuery, Thymeleaf, Spring Boot, Java, Go, and Python
Adjusting and extending the GitLab CI pipelines
Setting up and extending infrastructure as code with Terraform and ArgoCD on AWS
Setting up and running E2E and performance tests
Expanding the Databricks business intelligence solution to provide various KPIs
Responsibilities: Architecture, DevOps, development, unit tests, coaching employees and apprentices, E2E, smoke, and integration tests, agile methods consulting (Kanban, Scrum)
Technologies and methods: Java, Go, Kotlin, Node.js, Spring Boot, SOAP/REST, Quarkus, Thymeleaf, Vaadin, Slack, Jira, Confluence, IntelliJ, GitLab, SQS, Kafka, AWS, Kubernetes, Terraform, Maven, Gradle, GitLab CI, Databricks
Discover over 15,000 top freelancers
Statistics of experts using JNDI
Aggregated from the professional profiles of matched freelancers.
Experience
25 years
Position duration
1.7 years
Positions per freelancer
19
Top business areas
Information Technology, Product Development, Operations
Top industries
Information Technology, Banking and Finance, Automotive
Certification focus areas
Information Technology, Product Development, Operations
Bachelor's degree or higher
100%
Certifications per freelancer
3
Most common languages
German, English, Hindi
Speak two or more languages
100%
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 Germany 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 Germany using JNDI
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
JNDI basics
JNDI stands for Java Naming and Directory Interface. It gives Java applications a standard way to look up names and directory data such as database connections, mail sessions, JMS resources, and LDAP entries. In many enterprise systems, it is the glue between code and server-managed services.
Where it is used
- Application server resource lookup
- LDAP and directory integration
- JMS destination and connection factory lookup
- Legacy Java enterprise application support
- Externalized configuration and service discovery
JNDI often appears in systems built on Java EE, Jakarta EE, Spring, and older enterprise stacks that still rely on container-managed resources.
Typical work
Freelance specialists are brought in to fix lookup errors, refactor hardcoded resource access, and clean up server configuration. They also help when applications move between environments and naming paths change. In Germany, this is common in enterprise IT, finance, insurance, logistics, and public-sector systems that still run large Java estates.
Ecosystem skills
Strong professionals usually know LDAP, directory schemas, JAAS, JDBC, JMS, and application server configuration such as WildFly, WebLogic, WebSphere, or Tomcat-based setups. They understand how naming contexts, bindings, and environment-specific resources work together. That matters when a lookup succeeds in local testing but fails in production.
What good experts do
- Trace naming and directory lookup flow
- Diagnose bind and context errors
- Separate code from environment-specific settings
- Review security around directory access
- Stabilize deployments across test and production
Good JNDI work is precise. The expert should read server logs, inspect resource definitions, and understand when the problem sits in the application and when it sits in the container or directory service.
When to bring help
Bring in freelance expertise when an older Java system becomes hard to maintain, when LDAP or JMS integration breaks, or when a platform move exposes hidden naming assumptions. It is also useful during modernization, where JNDI calls may need to be isolated, wrapped, or replaced without breaking core business logic. In Germany, remote work is common for code and config review, while on-site sessions help when access to internal directory systems is sensitive.
Frequently asked questions
Before you brief your next project: the most common questions about JNDI.
JNDI is used to look up named resources and directory data from Java applications. That includes database connections, JMS objects, mail sessions, and LDAP entries. It lets the application ask the container or directory service for what it needs instead of hardcoding everything.
JNDI is not the same as LDAP. JNDI is the Java API used to access naming and directory services, while LDAP is one of the common directory protocols it can talk to. In practice, many Java systems use JNDI to reach an LDAP server.
A strong JNDI specialist usually knows LDAP, Java application server configuration, JMS, JDBC, and basic security around directory access. They should also understand how environment-specific bindings work in test and production. That combination is important when a lookup only fails after deployment.
A JNDI project needs expert help when resource lookup breaks, when an application is moved to a new server, or when older enterprise code is too tightly coupled to container settings. It also helps during modernization, when you want to reduce direct naming lookups without changing business behavior. If the system depends on LDAP or JMS, the need is even stronger.
JNDI is often used in older or container-managed Java systems, while direct configuration and dependency injection are common in newer code. JNDI is still useful when the application relies on server-defined resources such as data sources or JMS destinations. The right choice depends on how much of the stack is controlled by the application server.
JNDI work can be done remotely when the freelancer has logs, configuration files, and access to a safe test setup. On-site work can help when directory access is restricted or when production infrastructure is sensitive. In Germany, many teams combine remote analysis with short on-site sessions for environment checks.
A good JNDI expert explains the lookup path clearly, finds the root cause in logs or config, and separates code issues from server issues. They should be comfortable reading application server resources and LDAP bindings, not just Java code. Look for someone who has fixed real deployment problems, not only written sample code.
Java Naming and Directory Interface is the full name behind JNDI, and many searchers still use it when looking for help with older enterprise systems. The full term often appears in documentation, application server settings, and legacy code comments. Knowing both names helps when you need the right specialist quickly.
The average hourly rate of freelancers in Germany who have used JNDI in their recent projects is 95 €, which corresponds to a daily rate of about 760 € based on an 8-hour working day.
Of the freelancers in Germany who have used JNDI in their recent projects, 100% hold at least a Bachelor's degree.
On average, freelancers in Germany who have used JNDI in their recent projects have 25 years of professional experience, with a single engagement typically lasting around 1.7 years.
The most common languages among freelancers in Germany who have used JNDI in their recent projects are German (100%), English (100%), and Hindi (17%).
The most common industries among freelancers in Germany who have used JNDI in their recent projects are Information Technology (100%), Banking and Finance (83%), and Automotive (67%).
The most common business areas among freelancers in Germany who have used JNDI in their recent projects are Information Technology (100%), Product Development (100%), and Operations (67%).
Main locations of FRATCH Experts, who have recently used JNDI
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.
Berlin Hamburg Munich Cologne Frankfurt Stuttgart Dusseldorf Leipzig Dortmund Essen Bremen Dresden Hanover Nuremberg 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!
Philipp Thomaschewski
FRATCH CEO
