This is a process optimization and continuous improvement role embedded within the BYTE global delivery program. The PMO Process Optimization Analyst is responsible for identifying inefficiencies in the deployment lifecycle, defining and tracking KPIs that measure delivery performance, and systematically reducing the time and effort required to deploy solutions across new markets. This person works across delivery, engineering, and product teams — not as an administrator, but as a coordinator, process architect who makes every new market launch faster and smarter than the one before it.

What this role is about:

• Every new market deployment tends to rediscover the same problems and ask for the same things. This role exists to stop that. They facilitate identification of robust code modules and specific areas where configurations are needed and help Delivery Leads (DLs) explain this difference to each new market. The PMO Process Optimization Analyst will study how we deploy today, find what slows us down, and build the processes, playbooks, and reuse frameworks that progressively reduce implementation time. This is a facilitator and builder role, wherein you are building the process and baseline for how the BYTE program scales.
  
  
  

Key responsibilities:

Process analysis and bottleneck identification:

• Map the end-to-end SDLC (Software development life cycle) for BYTE market deployments. Identify recurring bottlenecks, handoff failures, rework cycles, and delays. Document root causes and propose targeted fixes.

• Maintain a living bottleneck and improvement backlog with owners and timelines

• Run periodic process retrospectives across delivery teams

Code and solution reuse facilitation:

• Work closely with engineering and delivery teams to identify configuration, code snippets, integrations, and solutions that have been deployed in prior markets and can be reused or adapted for new ones.

• Build and maintain a reuse catalog or knowledge base that delivery teams can access at the start of every new market engagement

• This person will not write code but must have enough prior development experience to recognize what is reusable and facilitate those conversations with engineers

KPI definition and metrics ownership:

• Define and establish the delivery performance metrics for the program.

• This includes deployment cycle time, requirements churn, defect escape rates, UAT vs. SIT issue ratios, and any other indicators that reveal how efficiently we are delivering, specifically focused on go-live activities.

• Stand up dashboards or reporting mechanisms to make these metrics visible to leadership
  
  

Track trends over time and flag regressions early:

• SDLC best practices research and adoption: Actively research what other programs and organizations are doing to reduce implementation time. Bring back relevant practices, evaluate fit, and drive adoption where applicable.

• Playbook and template ownership: Maintain and improve the standard delivery playbooks, kickoff and discovery templates, onboarding kits, and process documentation. Ensure these are living assets that evolve based on lessons learned across markets.

• Tooling efficiency: Ensure Jira, Confluence, and related tools are configured and used in ways that support process efficiency. Identify gaps where tooling is adding friction instead of reducing it.

• Lightweight delivery support: In a limited capacity, support delivery leads with coordination and reporting tasks where process governance is at stake. This is not the primary function of the role.

  
  

Day in the life:

• This person starts the week by reviewing delivery metrics and looking for. They spend time with engineering teams understanding what was built for Market A that could to Market B, and they update the reuse catalog accordingly. They run a process retrospective at the end of a market go-live, turn lessons learned into updated playbooks, and track whether the next market launch benefited from those changes. They report on KPI trends to leadership and push for action when the data shows a problem.

What success looks like:

• Measurable reduction in deployment cycle time across successive market launches

• A reuse catalog that delivery and engineering teams use at the start of every new market engagement

• KPIs are defined, tracked, and visible, and leadership can see delivery performance trends over time

• Process playbooks are current, adopted, and improving with each market

• Bottlenecks are identified and addressed before they repeat across multiple markets
  
  
  

Required experience:

• Prior experience as a product manager, scrum master or developer will be helpful because such software development experience will provide the skills to understand how solutions are built, what is reusable, and what UAT vs. SIT means in practice. This is not a developer role, but the development background is crucial.

• Deep familiarity with the SDLC, including requirements, development, systems integration testing, user acceptance testing, and deployment phases

• Experience in process improvement, operational efficiency, or delivery optimization roles

• Hands-on experience with Jira, Confluence, and other related software development tools like MS Project, Gnatt Charts, Dashboarding and reporting from Jira etc.

• Strong analytical mindset, comfortable defining metrics, reading data, and translating findings into action

• Clear written and verbal communication skills; ability to present findings and recommendations to senior leadership

• Experience working in multi-market or global delivery programs is a plus
  
  
  

What this role is not:

• This is not a Jira admin role. Ticket creation and board hygiene are not the job.

• This is not a developer or tester role. You will not write code or execute test cases

• This is not a project manager role. You do not own delivery timelines or scope decisions.

• This is not a PMO coordinator or assistant role. You are not here to take meeting notes or manage calendars for delivery leads.
  
  
  

This role is solely focused on making the solution development by the BYTE team more efficient, identifying what slows us down, building the systems to fix it, and ensuring each new market deployment is faster and better than the last. If that kind of structural, process-level problem solving is what you enjoy, this role was built for you.

The pay range that the employer in good faith reasonably expects to pay for this position is $39.30/hour - $61.40/hour. Our benefits include medical, dental, vision and retirement benefits. Applications will be accepted on an ongoing basis.

Tundra Technical Solutions is among North America’s leading providers of Staffing and Consulting Services. Our success and our clients’ success are built on a foundation of service excellence. We are an equal opportunity employer, and we do not discriminate on the basis of race, religion, color, national origin, sex, sexual orientation, age, veteran status, disability, genetic information, or other applicable legally protected characteristic. Qualified applicants with arrest or conviction records will be considered for employment in accordance with applicable law, including the Los Angeles County Fair Chance Ordinance for Employers and the California Fair Chance Act. Unincorporated LA County workers: we reasonably believe that criminal history may have a direct, adverse and negative relationship with the following job duties, potentially resulting in the withdrawal of a conditional offer of employment: client provided property, including hardware (both of which may include data) entrusted to you from theft, loss or damage; return all portable client computer hardware in your possession (including the data contained therein) upon completion of the assignment, and; maintain the confidentiality of client proprietary, confidential, or non-public information. In addition, job duties require access to secure and protected client information technology systems and related data security obligations.