IDAM Back-end Java Developer - SC Cleared

IDAM Back-end Java Developer - SC Cleared

Rate: 500 - 535 a day

IR35: Inside IR35

Location: Remote within the UK

Duration: Initially 6 months

Clearance: Active SC Clearance required

You will join a global IT consultancy who are delivering digital transformation to public sector body. They are looking for a back-end Java Developer with proven IDAM (Identity and Access Management) experience. You will be part of a continuous improvement squad delivering enhancements and new features alongside BAU work (i.e. incidents and support maintenance activities). In addition, you will be involved in helping our client transform their IDAM service, re-platforming to Azure Kubernetes Service. You will have a solid understanding of modern deployment pipelines and DevOps principles. The role will require providing out of hours support (i.e. Monday to Saturday once per month).

As a Senior Software Engineer with a focus on back-end development, you will play a key role in designing, building, and evolving high-performance, server-side applications. Your responsibilities will extend beyond coding to include technical leadership, mentoring, and strategic input on technology decisions.

Key Responsibilities:

• Architect, develop, and enhance robust, scalable systems and services in a modern, cloud-based environment.
• Lead or contribute to technical design discussions, translating business requirements into high-quality solutions.
• Participate actively in Agile ceremonies, including daily stand-ups, sprint planning, and retrospectives.
• Guide and collaborate with cross-functional teams, ensuring best practices in coding, integration, and delivery are followed.

Essential

• Knowledge of Identity and Access Management (IDAM)
• Experience in developing applications that interact with at least one IDAM platform (e.g., ForgeRock, One Identity, Okta, Azure AD, AuthO)
• Java development
• Jenkins
• Reverse engineering
• Working collaboratively in a close-knit team and being able to work independently on Jira tickets