Introduction
At IBM, work is more than a job - it's a calling: To build. To design. To code. To consult. To think along with clients and sell. To make markets. To invent. To collaborate. Not just to do something better, but to attempt things you've never thought possible. Are you ready to lead in this new era of technology and solve some of the world's most challenging problems? If so, lets talk

Your Role and Responsibilities

• "Serve as a Development Team Lead, responsible for working with the team to ensure the approved requirements for the Epic are understood and implemented on time and with high quality. Groom and manage the foundational backlog of technical debt for the team. Ensure all dependencies are scheduled for uplifts when necessary. Possess general knowledge of the entire transformation pillar and serve as a technical resource for other related squads in the local lab when required.
• Resolve any hot technical/defect issues, drive fixes to resolution if necessary. Manage defect change risk versus deadlines and release quality goals. Actively participate in Pull Request code reviews, and act as a technical ""tie-breaker"" for solution implementation in code.
• Work closely with the STSM of the Agile Release Train (ART) and serve as a technical representative at cross product meetings. Continually educate and mentor other developers, both internal and external to the squad, pertaining to the code base and technology.
• Assist the Security and Compliance focal on obtaining the appropriate approvals, supplying technical details when necessary. Supply technical details to the ART Release Train Engineer on extra-release issues such as DOUs, Open Source concerns, Export Classification, Copyright registration, Licensing, etc.
• Responsible to coordinate among the other development team leads to determine when all the components are ready for a release integration build and sign off on integration CI/CD pull requests. Ensure details of the upcoming component changes are made available to downstream consumers (e.g. User Acceptance Test, Documentation).
• Be able to demonstrate the product from end to end, understanding how the overall vision impacts components under their area of responsibility. Serve as a technical lab advocate to at least one customer who is utilizing the product.
• Resolve any hot technical/defect issues, drive fixes to resolution if necessary. Manage defect change risk versus deadlines and release quality goals. Actively participate in Pull Request code reviews, and act as a technical ""tie-breaker"" for solution implementation in code.
• Be able to demonstrate the product from end to end, understanding how the overall vision impacts components under their area of responsibility. Serve as a technical lab advocate to at least one customer who is utilizing the product. "
• Responsible to coordinate among the other development team leads to determine when all the components are ready for a release integration build and sign off on integration CI/CD pull requests. Ensure details of the upcoming component changes are made available to downstream consumers (e.g. User Acceptance Test, Documentation).
• Assist the Security and Compliance focal on obtaining the appropriate approvals, supplying technical details when necessary. Supply technical details to the ART Release Train Engineer on extra-release issues such as DOUs, Open Source concerns, Export Classification, Copyright registration, Licensing, etc.
• Work closely with the STSM/ Senior technical architects of the Agile Release Train (ART) and serve as a technical representative at cross product meetings. Continually educate and mentor other developers, both internal and external to the squad, pertaining to the code base and technology.

• Knowledge of LLMs preferred. Exposure to Agile methodology

• "Possess a strong coding language proficiency in at least one programming language (Java preferred)
• Be able to rapidly learn the foundations of other programming languages with self paced education as the transformation pillar is designed to translate code between comparative languages.
• Possess a working knowledge of micro-service architectures and DevOps practices."