Create New R&D PMO Handbook Pages and Remove Outdated Pages

---

title: "R&D PMO"

description: The R&D PMO is a team of Technical Program Managers working across multiple domain areas within Engineering, Product, and Security. 

---

### Mission and Vision

This is in progress and will be finalized at the upcoming R&D PMO offsite in Q2. 

### Core Responsibilities

More information can be found in the R&D TPM Job Family.

### Team Structure

The Program Management Org (PMO) is a cross-functional team that is based within the Engineering org. Our scope of work primarily spans across Engineering, Product, and Security, with some cross over into GTM. While individual TPMs have their own focus areas, we regularly align as a team to ensure we have common practices and standards.

#### Project Assignments

We aim to ensure that TPMs are working in similar ways across different areas of the company. Ideally we want our stakeholders to have a common understanding of how TPMs engage with their programs, without having to know the details of how each team works. Here is a bit more information about how we assign projects across the PMO.

| | Product Focus Area | Engineering Focus Area  | Security Focus Area  |

|-----------------|-------------|---------------|---------------|

| Area of Domain Expertise (primarily focused on) | End to end feature delivery and launches (primarily cross-functional feature development), Monetization strategy and execution, Customer engagement programs that inform our roadmap (CAB, etc) | Large scale eng-led programs that focus on scalability, quality, and resilience, Dedicated reliability and migration, Bug triage / management | Large scale programs that focus on addressing security vulnerabilities, improving security posture, Compliance related efforts |

| Likely connected to the following cross-org areas: | Product, Engineering, Marketing, Sales, CS, Security | Product, CS, Security | Engineering, Security, Legal |

| Requirements | Generally requires prior experience in a technical company, with an understanding of technical and business needs. This can vary depending on the focus area of an individual TPM. | Generally requires an engineering degree or prior experience in a technical role. This can vary depending on the focus area of an individual TPM. | Generally requires prior experience in a technical company, with understanding of security and compliance domains. This can vary depending on the focus area of an individual TPM. |

Core responsibilities are the same by TPM level across both teams. Job-specific responsibilities vary by the focus area of an individual TPM. More info on TPM leveling and associated responsibilities can be found on the job family page.

#### Communication

Our team is (as of this writing) distributed across the United States and EMEA. Individual team members define their working hours according to their personal preferences and their projects’ needs. We are looking to expand our team’s time zone coverage within EMEA.

Generally, our team will default to async communication in alignment with GitLab values. When it is needed, we will pull team members into a call or meeting to ensure we are working effectively and efficiently if needed. Cross-functional initiatives typically need more sync time. If you are part of a core project team, we will likely find recurring meeting time to drive execution for the length of the project.

### Requesting TPM Support

In order to request TPM coverage, please open an issue using [this template](https://gitlab.com/gitlab-com/Product/-/blob/main/.gitlab/issue_templates/TPM-Coverage-Request.md). Details on this process can be found in our [TPM Epic](https://gitlab.com/groups/gitlab-com/-/epics/2471). Work that can benefit from program management support is typically complex, cross-functional, and critical to the business. We determine if a project is a good match for TPM support with the [TPM Coverage Calculator](https://docs.google.com/spreadsheets/d/1Tv9WK9LIBJgLbEWWMEvXLtewDDv-luJWPjQDtkhWaJ0/edit?usp=sharing) (internal only link). The calculator is currently being revised to incorporate security projects.

Incoming project requests will be routed to the right TPM based on resource availability, TPM specialties, and project goals.

Please don’t directly DM individual members of the TPM team to ask for their support on a project. This can seem like a fast way to get support, but it doesn’t allow for proper resource allocation across the PMO. Filing an issue ensures that you are connected with a program manager who is a good fit for your project and has bandwidth to take on something new.

If you’d like to contact the team for general questions or advice, please reach out over slack in #r-and-d-pmo. 

- [Product Management](/handbook/product/product-management/)

- [User Experience](/handbook/product/ux/)

- [Product Technical Program Management](/handbook/product/groups/product-technical-program-management)

## Product Team Mission

---

title: "Product Technical Program Manager"

description: "The Product Technical Program Manager (TPM) role supports cross-division initiatives across Product, UX, Engineering and other functions within R&D along with functions across GTM"

---

### Mission

Our mission as Technical Program Managers is to own the execution of complex, cross-functional initiatives that better enable GitLab to meet company objectives. We aim to make complex programs simpler with proactive, transparent, and efficient practices, while adapting our methodologies to the scenario at hand. We aspire to be trusted partners to stakeholders across the company, in order to accelerate and improve upon program outcomes over time.

### Long-Term Vision

* Define and consistently deliver against a standard of excellence for Program Management at GitLab.

* Have a team reputation as a fundamental and necessary resource when R&D needs to deliver against complex business objectives and ultimately results for customers.

* TPMs are seen across our company-wide stakeholders as a key element to accelerate GitLab's strategic business objectives.

### Near-Term Goals for FY26

* Excel in strategic program delivery; focus on a core group of highly visible and impactful programs, setting the tone for how our expanded team delivers value.

* Create scalable workflows and processes that have a positive impact on GitLab's overall efficiency and solicits positive sentiment from stakeholders.

* Continue to build our TPM team identity as the team expands; develop a strong team foundation and niche within the business. In doing so, evangelize TPM best practices.

### Core Responsibilities

More information can be found in the [Product TPM Job Family](/job-families/product/technical-program-manager)and the [Product TPM Leadership Job Family](/job-families/product/technical-program-manager-leadership)

### How We Work

#### Communication

* Slack is the best way to reach out to our team; our goal is to respond to all requests within 24 hours. The best way is to send us a message in the #technical-program-management slack channel.

* Alternately, if an issue exists for a scope of work, you can tag us directly there.

#### Working hours

* Our team is (as of this writing) distributed across the United States and can accommodate requests during US Business Hours - both east and west coast. We are looking to expand our team's time zone coverage to EMEA.

* Many of our TPM's schedules are more flexible and accommodate hours outside of the hours noted above.

#### Async vs. Sync

* Generally, our team will default to async communication in alignment with GitLab values. When it is needed, we will pull team members into a call or meeting to ensure we are working effectively and efficiently if needed.

* Cross-functional initiatives typically need more sync time. If you are part of a core project team, we will likely find recurring meeting time to drive execution for the length of the project.

### How You Can Leverage The Product TPM Team

If you have an initiative that you think could benefit from program management support, the best first step is to message #technical-program-management following this template to intake a request.

Work that can benefit from program management support is typically complex, cross-functional, and critical to the business. We determine if a project is a good match for TPM support with the [TPM Coverage Calculator](https://docs.google.com/spreadsheets/d/1Tv9WK9LIBJgLbEWWMEvXLtewDDv-luJWPjQDtkhWaJ0/edit?usp=sharing) (internal only link)

#### What about Program Managers outside of the Product Org?

As Technical Program Management is a relatively new function at GitLab, we're continually iterating on how the various TPM and PgM teams collaborate.

|Product|Infrastructure|Security|

|:-----------------|:-------------|:---------------|

|**The R&D Technical Program Manager role supports cross-division initiatives across PM, UX, Engineering and other functions within R&D along with functions across GTM**| **Infrastructure Technical Program Management Team drives the planning, execution, and delivery of complex infrastructure projects across Engineering and Product.**|**The Security Program Manager will be responsible for complete overview and driving security initiatives across product, engineering and business enablement.**|

|Manage and collaborate on key initiatives with stakeholders and leadership across R&D. Drive accountability ensuring all program objectives are met.|Establish a reliable and visible cadence for initiative reviews, decision making, prioritization, and staffing management.|Communicate successfully with partners and drive accountability across teams to ensure program objectives are met |

|Refine and optimize division processes improving overall efficiency and execution of the division.|Lead and drive Infrastructure projects such as: Availability, Disaster Recovery, Releases, CI/CD Pipeline Efficiency, and Engineering Productivity|Gather and examine customer and internal security team needs and opportunities for new information security programs, products and projects |

|Gather inputs and feedback and suggest improvements to our Product Process, and operational model within the Product division.|Provide technical project management, coordination, and inter/intra team communications to deliver outstanding program outcomes.|Drive organizational needs cross-functionally with product, engineering and finance including tracking and reporting of progress and metrics |

| [Product Technical Program Management](/job-families/product/technical-program-manager) | [Infrastructure Program Management](/job-families/engineering/technical-program-management/technical-program-management-ic/) | [Security Program Management](/job-families/security/security-program-manager/) |

### Contacting The Team

The best way to reach out to our team is through #technical-program-management slack channel.

#### Why use the channel and not direct message a PM I already know?

Even though this can seem like a good idea, it [limits visibility to the larger TPM team](/handbook/communication/) and doesn't allow for proper resource allocation.  Sending your requests in this channel will allow for full visibility and ensure our team is connecting you with the program manager who is a good fit for your project and has bandwidth to take on something new.

---

title: "Technical Program Management Individual Contributors"

description: "Driving strategy and initiatives across Engineering"

---

Technical Program Manager (TPM) is responsible for the planning, execution, and delivery of complex projects across Engineering. TPMs work with a variety of stakeholders, including engineers, architects, and business leaders, to ensure that projects are completed on time and within budget, and to the required quality standards. This includes the tracking, monitoring and influencing priority of significant objectives, goals and plans from all sub-departments.

TPMs typically have a background in engineering or computer science, and have a deep understanding of the technical aspects of product management and infrastructure scalability. They also have strong leadership and communication skills, and able to work effectively in a fast-paced and demanding environment.

## Responsibilities

- Establish a reliable and visible cadence for initiative reviews, decision making, prioritization, and staffing management.

- Lead and drive projects such as: Availability, Disaster Recovery, Releases, CI/CD Pipeline Efficiency, and Engineering Productivity

- Provide technical project management, coordination, and inter/intra team communications to deliver outstanding program outcomes.

- Work closely with Software Engineers, SREs, Engineering Leadership, and other Product & Engineer teams to deliver a high quality and resilient SaaS Infrastructure Platform with world class Availability.

- Manage programs, define milestones and success criteria, staffing allocation to ensure successful on-time deliverables.

- Lead strategic planning with direct influence over staffing decisions, project timelines, and planning stakeholders.

- Work on massive distributed, large-scale systems, storage solutions, applications, and new platforms.

- Be a change advocate responsible for initiating and leading multiple organizations through pivots needed to address shifts in business trends and priorities

- Utilize technical acumen in working with large, cross-functional distributed teams.

## Requirements

- Experience managing execution of complex programs that span multiple engineering teams through the software project lifecycle (build, test, and release on time).

- Experience with technologies such as virtualization and complex software infrastructure systems, compute, storage, data migration, capacity, load balancing, and software defined networking.

- Experience driving cross-functional initiatives according to plan and timelines

- Prioritize effectively and multitask efficiently

- Proven track record of successful collaboration with internal and external partners

- Communication, presentation, and documentation skills

## Levels

### Intermediate Technical Program Manager

#### Intermediate Technical Program Manager Job Grade

The role is a [grade 6](/handbook/total-rewards/compensation/compensation-calculator/#gitlab-job-grades).

#### Intermediate Technical Program Manager Responsibilities

All responsibilities listed above (applicable to all roles) plus:

- Define and manage the program scope, schedule, and budget

- Develop and maintain program plans, status reports, and other project documentation

- Facilitate cross-functional communication and collaboration between stakeholders, technical teams, and management

- Ensure program milestones are achieved on time and within budget

- Identify and manage program risks, issues, and dependencies

- Provide regular updates on program status to stakeholders and senior management

#### Intermediate Technical Program Manager Requirements

- Technical degree in Engineering, or related technical field

- 3-5 years of experience in technical program/project management or equivalent

- Experience with infrastructure-related projects such as cloud infrastructure, data center operations, and network engineering

- Experience in Agile development methodologies

- Excellent verbal and written communication skills

- Strong analytical and problem-solving skills

- Ability to work effectively in a fast-paced and dynamic environment

### Senior Technical Program Manager

#### Senior Technical Program Manager Job Grade

The role is a [grade 7](/handbook/total-rewards/compensation/compensation-calculator/#gitlab-job-grades).

#### Senior Technical Program Manager Responsibilities

All responsibilities of previous roles plus:

- Coordinate with technical teams to ensure adherence to established project standards, processes, and methodologies

- Drive continuous process improvement and operational excellence within the program

- Identify and coordinate the interdependencies among programs, products and other critical initiatives for 1 or more engineering sub-departments

- Provide insight and suggestions to mitigate

- Examine risks associated with programs and prioritize risks accordingly

- Collaborate on strategy and direction with organizational stakeholders; Oversee project planning and management

- Communicate successfully within the project team and at multiple levels of management, building trust across the organization, and demonstrating care with sensitive information

- Develop and coach intermediate program managers

#### Senior Technical Program Manager Requirements

All requirements of previous roles plus:

- 5+ years of experience in technical program/project management or equivalent

- Experience with infrastructure-related projects such as cloud infrastructure, data center operations, and network engineering

- Experience influencing others without having direct management authority and motivating them to successfully complete tasks within required timelines

- Risk analysis and problem-solving skills

- Excellent at building relationships with partners.

### Staff Technical Program Manager

#### Staff Technical Program Manager Job Grade

The role is a [grade 8](/handbook/total-rewards/compensation/compensation-calculator/#gitlab-job-grades).

#### Staff Technical Program Manager Responsibilities

All responsibilities of previous roles plus:

- Identify and coordinate the interdependencies among programs, products and other critical initiatives across all engineering sub-departments within our organization

- Assist defining business requirements and roadmaps in alignment with the overall engineering strategy

- Define acceptance criteria for solutions, value proposition and milestones for execution; Validate prototypes with partners and iterate solutions as needed to deliver value

- Track and provide reporting and measurements of program effectiveness and communicate findings to management

- Develop repeatable, scalable, efficient, and effective processes

#### Staff Technical Program Manager Requirements

All requirements of previous roles plus:

- 7+ years of experience in technical program/project management or equivalent

- Advanced understanding of application, development and frameworks

- Advanced anaytical skills for assessing and recommending solutions based on data and research

### Principal Technical Program Manager

#### Principal Technical Program Manager Job Grade

The role is a [grade 9](/handbook/total-rewards/compensation/compensation-calculator/#gitlab-job-grades).

#### Principal Technical Program Manager Responsibilities

All responsibilities of previous roles plus:

- Develop and implement strategies for program growth and expansion

- Contribute to technical program management budgeting and financial reporting artifacts

- Expanded sphere of influence in driving initiatives across Engineering

- Drive goals and objectives that results in further progress of the department roadmap and strategy

- Accountable and responsible for overflow responsibilities from senior leadership

- Identify, define and implement programs across Engineering

#### Principal Technical Program Manager Requirements

All requirements of previous roles plus:

- 10+ years of experience in technical program/project management or equivalent

- Influence and implement change across the company

- Speak to and represent GitLab to customers and vendors

## Specialties

- Currently no specialties defined

## Performance Indicators

- Individual TPM's Performance Indicators will be defined based on their quarterly goals

- Project Completion rate

  - Measure by tracking the percentage of projects completed on time and within budget.

- Stakeholder Satisfaction score

  - Measure through regular feedback surveys or interviews with stakeholders, assessing the program management effectiveness, communication and responsiveness.

## Career Ladder

- To Be Defined (TBD)

## Hiring Process

Candidates for this position can expect the hiring process to follow the order below. Please keep in mind that candidates can be declined from the position at any stage of the process. To learn more about someone who may be conducting the interview, find their job title on our [team page](/handbook/company/team/).

1. Qualified candidates will be invited to schedule a 30 minute [screening call](/handbook/hiring/candidate-faq/#screening-call) with one of our Global Recruiters.

1. Candidates will be invited to schedule a 50-minute interview with a Manager/Sr. Manager within Engineering.

1. Candidates will be invited to schedule a 50-minute interview with a Director/Sr. Director in Engineering.

1. Candidates will be invited to schedule a 50-minute interview with a cross-functional stakeholder.

1. Candidates will be invited to schedule a 50-minute interview with an existing TPM/Program Manager.

1. Candidates will be invited to schedule a 50-minute interview with the CTO.

Additional details about our process can be found on our [hiring page](/handbook/hiring/).