AWS Cloud Architect & Technical Lead

Position Summary

The Architect and Technical Lead provides daily technical leadership for an Agile Sprint Team building a modern cloud native platform on AWS. This role guides engineering implementation, enforces code quality standards, mentors developers, and ensures that team deliverables align with program architecture and engineering best practices. Working closely with the Product Owner, Scrum Master, architects, developers, and other delivery teams, the Architect and Technical Lead converts architectural direction into actionable technical decisions, resolves engineering impediments, and supports successful sprint execution. The role also drives adoption of AI assisted development tools to improve productivity, software quality, and delivery efficiency.

Key Responsibilities

• Provide daily technical leadership and engineering direction for an Agile Sprint Team

• Translate platform architecture standards into practical technical designs and implementation choices

• Guide development of cloud native application features and services using AWS technologies

• Review code for quality, maintainability, performance, security, and adherence to engineering standards

• Lead peer code reviews and promote consistent software engineering best practices

• Mentor and coach developers to support technical growth and continuous improvement

• Partner with the Product Owner and Scrum Master to refine stories, assess feasibility, estimate effort, and support sprint planning

• Resolve technical challenges and engineering impediments affecting sprint delivery

• Coordinate cross team dependencies, technical interfaces, and integration points

• Promote continuous integration, automated testing, and continuous delivery practices

• Drive adoption of AI assisted development tools across coding, testing, debugging, documentation, and code review

• Participate in design discussions, engineering planning sessions, architecture reviews, and release readiness activities

• Communicate technical decisions, risks, dependencies, and recommended solutions to technical and nontechnical stakeholders