Job Summary

Backend Engineer. Two engineers are required for 6-8 weeks. Both are expected to cover the full scope of the migration - backend SPI development, infrastructure changes, and OIDC integration.

Role Description

The migration rewrites a Keycloak User Storage SPI (Java, EJB Quarkus), upgrades the Keycloak runtime and supporting infrastructure, and configures GRP as an external OIDC Identity Provider. Engineers on this project will work across all three layers: Java provider code, container/CI configuration, and OIDC/identity federation.

Must Have

- Java (qualified level, Java 11 or later) - all three Maven components target Java 21
- Keycloak SPI development - has written or maintained a User Service Provider or equivalent; understands how providers are packaged and deployed to Keycloak
- JPA / Hibernate - comfortable managing an lifecycle without container injection
- OIDC / OAuth 2.0 - understands token structure, identity federation,



and broker login flows; must be able to configure an OIDC Identity Provider in Keycloak and interpret token claims
- Docker (multi-stage builds) - the Dockerfile is a full rewrite from a WildFly entrypoint model to a Quarkus two-stage build
- AWS

Good to Have

- Jakarta EE migration experience
- Quarkus (datasource configuration, extension model)
- Keycloak administration - configuring realms, clients, identity providers, and mapper flows via the admin UI and REST API
- AWS ECS / ECR - image promotion via CI/CD pipeline
- GitHub Actions - updating existing workflows
- PostgreSQL - version upgrade (13 17); no schema changes required
- Spring Security - existing password verification logic is preserved in the SPI
- Github Copilot

Disclaimer: This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.

📌 Java Backend Engineer (Bengaluru)
🏢 Embitel Technologies
📍 Bengaluru