Back
Metro location and generalist Java title increase competition, but Keycloak specialization reduces candidate pool.
Specialized Keycloak/OIDC expertise limits cross-industry transferability, requiring identity-focused experience.
Numerous mandatory technical requirements (Keycloak SPI, Java 11+, OIDC, JPA, Docker, AWS) create strict shortlisting filters.
Login to See Your Match Score
Create a free account or log in to unlock your CV match score across:
Lead the migration and redevelopment of Keycloak User Storage SPI from Java EJB to Quarkus.
Develop and manage backend Java provider code, container and CI configurations, and integrate OIDC Identity Provider.
Upgrade Keycloak runtime and supporting infrastructure, including Dockerfile redesign and AWS deployment.
Professional Java developer with experience in Java 11 or later, preferably Java 21.
Experience in Keycloak SPI development, specifically User Service Provider or equivalent.
Proficient in JPA/Hibernate lifecycle management without container injection.
Strong understanding and ability to configure OIDC/OAuth 2.0 Identity Providers in Keycloak, Docker multi-stage builds, and AWS.
Work Experience Required: Not explicitly mentioned in the JD.
Experienced backend engineer comfortable working across Java code, containerization, CI/CD, and identity federation layers.
Prior exposure to Keycloak administration and configuration, Jakarta EE migration, and Quarkus.
Familiarity with AWS ECS/ECR, PostgreSQL upgrades, and GitHub Actions for CI/CD pipelines is advantageous.