These team members will be embedded in the platform engineering team's scrum teams.
These people will be expected to be across multiple scrum teams as their skills allow and as the client needs.
However, the primary footprint at present will be with the infrastructure automation / devops / cloud engineering pod that is focused on infrastructure.
These are all technical roles expected to be embedded within this pod.
PMO will ultimately be led by the customer in the new working model.
Daily activities will, in general, include: Attending team ceremonies (stand ups, reviews, etc.
), working backlog items against a prioritized backlog, and updating in JIRA (migrating away from GitHub at present).
Infrastructure automation development & engineering (via TypeScript CDK, GitHub Actions).
Platform capabilities design (think more application level items such as shared microservices like a login/authentication service), proof of concept, and implementation work.
Developing test scripts, automation, and executing tests for their developed engineering capabilities.
In general, we should be looking for full stack engineers to fill these roles, but tactically I know that's a unicorn term for resourcing.
So the following big ticket skills and nice to haves spread in some way across the team are where we would focus: Core platform skills & technologies Automation pipelines - GitHub Actions Container Orchestration - AWS EKS Infra Automation - AWS CDK - TypeScript General AWS security comprehension (understanding of security best practices) General AWS architecture comprehension (understanding of common AWS services and patterns across VPC, RDS, ELB, Route 53, S3, etc.)
Nice to haves Continuous Deployment - Argo CD Backend - application development skills/experience, REST patterns & event-based Experience developing in a gXp or other highly regulated industry a plus #J-18808-Ljbffr