> Markdown version of [/jobs/ext/4043659-senior-backend-engineer-java](https://www.wearedevelopers.com/jobs/ext/4043659-senior-backend-engineer-java). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Backend Engineer | Java - **Company:** ILIAS Solutions - **Location:** Diegem (Machelen), Belgium - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Java (Programming Language), Application Programming Interfaces (APIs), Business Logic, Batch Files, Federal Information Processing Standards (FIPS), Github, Hibernate (Java), Java Database Connectivity, Java Persistence API, Java Virtual Machine (JVM), Python (Programming Language), Key Management, PostgreSQL, Liquibase, Microsoft SQL Server, Network Connections, OpenID, Oracle (Applications), Query Optimization, Role-Based Access Control, Simple Object Access Protocol (SOAP), Software Engineering, SonarQube, PL-SQL, Management of Software Versions, Openapi, Datadog, Data Logging, Transport Layer Security, Okta, Delivery Pipeline, Grafana, Apache Spark, Spring-boot, Indexer, Backend, Database Migration, Kubernetes, Information Technology, Apache Kafka, Restful APIs, Heap (Data Structure), OpenSearch, Docker, Jenkins - **Published:** October 14, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=4293bcc81ece9fea ## About the Role * 6+ years of professional backend engineering experience with Java as your primary language, and a solid track record across complex, production-grade systems. * Expert-level Java 17+ with deep knowledge of Spring Boot or Quarkus, and strong JVM internals: garbage collection tuning, memory profiling, heap and thread dump analysis. * Production Kafka experience at depth: producers, consumers, idempotency handling and schema evolution, not familiarity, but real operational ownership. * REST API design with OpenAPI, including versioning strategy and backward compatibility across release cycles; strong JPA/Hibernate, JDBC and database migration tooling (Flyway or Liquibase); PostgreSQL query optimisation, indexing, partitioning and large-table migrations. * Docker, Kubernetes and Helm in production packaging contexts, not only local development; CI/CD pipelines (Jenkins or GitHub Actions); security and quality tooling including SonarQube, dependency scanning, SBOMs and image signing used in a real delivery pipeline. * OIDC and Keycloak at the integration and usage level for authentication and authorisation; secrets management, TLS and RBAC; structured logging, metrics and observability tooling (Grafana, OpenSearch or equivalent). * Clear written and verbal communication in English with both engineering and product stakeholders; a degree in computer science or software engineering, or equivalent professional experience that demonstrates the same capability. * Eligibility to obtain and maintain the required national or NATO security clearance for this role (we support candidates through the clearance process)., * Legacy integration depth: Oracle, SQL Server, PL/SQL, SOAP or batch file exchange in production contexts. * Air-gapped or offline software delivery experience, particularly using signed bundles or tooling such as Zarf; experience with FIPS mode or STIG-hardened environments is especially relevant given our deployment constraints. * Advanced Keycloak administration and fine-grained authorisation configuration; reactive or async Java patterns using virtual threads or Project Reactor. * Experience in regulated or defence-adjacent industries; working knowledge of Dutch or French., This is a role for an engineer who finds legacy integration intellectually interesting rather than career-limiting, who wants to set standards rather than just meet them, and who values a codebase they can be proud of over one they are the only person who understands. The working language is English; Dutch or French is useful but not required to do the job well., Because of the nature of our work, this role may require eligibility under applicable export-control regulations and the ability to obtain national or NATO security clearance. We assess eligibility lawfully and on a role-by-role basis; specific requirements are discussed during the selection process. We do not exclude candidates on the basis of nationality except where mandated by applicable export-control or security-clearance law. ## Description Offline, air-gapped installations for NATO customers mean your API versioning and backward-compatibility decisions are not technical hygiene, they are the difference between a fleet that can operate and one that cannot. The backend services you design and maintain run in constrained, version-locked environments where an incompatible release cannot simply be rolled back over a network connection. Beyond feature delivery, this role carries real technical leadership weight: you will help set Java coding standards, guide architectural decisions, and mentor engineers across the Backend Engineers chapter, with an explicit goal of distributing knowledge rather than concentrating it., * Design and maintain Java backend services and APIs so they remain stable and versioned across releases, allowing customers in offline environments to upgrade on their own schedule. * Build and own complex business logic and integration layers connecting to legacy and customer systems, working across REST, SOAP, batch file exchange and event-driven patterns with Kafka. * Package and deliver services for Kubernetes deployments including offline customer installations, applying reproducible build, image signing and SBOM practices throughout. * Define and embed Java coding standards, dependency policies, security defaults and testing practices across the chapter, reducing bus-factor risk through shared ownership. * Contribute to build-or-not decisions alongside product owners, translating technical constraints and integration complexity into options the product team can act on. * Collaborate with analytics engineers on Python and Spark integrations, and review technical design documents to raise the quality bar across the team. What success looks like Over time, the backend services you own become the most dependable part of the platform: APIs hold their contracts across releases, new engineers can read and extend the codebase without escalating to you, and offline deployments ship with a clear, reproducible packaging trail. As your ownership grows, the chapter's standards documents reflect decisions you have driven and stress-tested with domain experts, and build-or-not conversations happen earlier because the team trusts your technical reading of complexity and risk.