R&D PMO: Technical Program Management
TPM Role Overview
More information about the team, structure and areas of work can be found on the R&D PMO Handbook Page
Key Competencies & Expectations
The Technical Program Management (TPM) competencies are structured across seven main categories for both the Individual Contributor (IC) and Management tracks, in addition to the core GitLab Values.
The competency framework is broken down into the following key areas:
Ambiguity: Measures the degree to which project requirements are pre-defined. Junior TPMs typically work on well-defined tasks, while Senior and Principal TPMs are expected to “bring order to chaos,” operating independently in environments where goals or technical paths are highly uncertain.
Scope & Influence: Defines the breadth of impact, scaling from a single team or feature to managing cross-organizational programs. Higher levels require the ability to influence without authority and drive consensus across diverse departments. Identifies the stakeholders a TPM collaborates with and influences. This shifts from peer-level coordination to acting as a strategic advisor for senior leadership and executives.
Execution: Evaluates the ability to deliver programs on time and within scope while managing risks and dependencies. Advanced execution involves proactive risk mitigation — anticipating blockers before they become emergencies.
Communication: A “best in class” requirement for TPMs. It moves from status reporting to “executive clarity,” where complex technical issues are translated into actionable business insights for different audiences.
Impact: Focuses on measurable outcomes for the business or customer. Senior roles are prioritized based on their strategic impact and their ability to align technical initiatives with long-term company goals.
Technical/Domain Expertise: Measures the depth of understanding in specific fields (e.g., distributed systems, cloud computing, monetization, or AI). As levels increase, TPMs are expected to move from managing execution to being “technically/domain strategic,” architecting resilient systems and scaling solutions.
Problem Solving & Continuous Improvement: The transition from following established agile or hybrid methodologies to designing and optimizing the organization’s delivery frameworks to eliminate waste and increase velocity. This dimension also evaluates the ability to diagnose complex, often ambiguous challenges and drive them to resolution through structured thinking and sound judgment. Junior TPMs learn to distinguish symptoms from root causes and develop escalation awareness within well-defined boundaries. As levels increase, TPMs are expected to move from reactive problem resolution to proactive problem identification — applying systems thinking, data-driven analysis, and root cause rigor to surface and frame organizational challenges before they are escalated by others. At the most senior levels, TPMs serve as the ultimate escalation authority, pioneering solutions to unprecedented problems that span the organization and influencing how GitLab — and the industry — approaches complex program challenges.
Program Management Fundamentals
TPMs should first be experts in Program Management, with their relevant focus area as a secondary area of expertise. This includes knowledge and skill sets in:
- Planning and execution excellence / accuracy
- Resource allocation and optimization
- Timeline and dependency management
- Risk identification and mitigation
GitLab CREDIT Values - applicable to all levels
- Collaboration
- Results
- Efficiency
- Diversity, Inclusion & Belonging
- Iteration
- Transparency
TPM Level Matrix
1. Individual Contributor (IC) Track
Entry & Junior Levels
| Level | Ambiguity | Scope & Influence | Execution | Communication | Impact | Tech Expertise | Problem Solving |
|---|---|---|---|---|---|---|---|
| TPM Intern | Well-defined tasks; clear requirements. | Task level within one team. Building foundational relationships. | Tactical. Executes specific tasks. Learns to escalate blockers. | Basic status updates. Learning to document work. | Minimal direct impact. Contributes to team learning. | Learning technical fundamentals and terminology. | Follows instructions. Identifies blockers before escalating. |
| TPM Entry Level | Defined tasks and small sub-projects. Frequent guidance. | Task/feature level within one team. Focus on internal relationships. | Tactical. Successfully executes assigned tasks. | Consistently clear updates and documentation. | Direct, small-scale contribution to project completion. | Basic understanding of team’s tech stack and concepts. | Follows existing processes. Distinguishes symptoms from root causes. |
| Associate TPM | Projects with defined requirements. Regular guidance. | Owns a defined project within a single team. Bounded scope. | Tactical. Manages defined elements. Tracks dependencies. | Regular updates to project team. Maintains basic docs. | Contributes to delivery. Keeps team organized/on track. | Understands project team’s tech domain. Discusses concepts with Eng. | Solves well-defined problems iteratively. Exercises escalation judgment. |
Professional & Senior Levels
| Level | Ambiguity | Scope & Influence | Execution | Communication | Impact | Tech Expertise | Problem Solving |
|---|---|---|---|---|---|---|---|
| TPM | Manages programs with some ambiguity. Works independently. | Programs spanning 1-2 teams at medium complexity. | Tactical. Owns plans, status, risk. Makes trade-offs (Time vs Scope). | Clear written/verbal. Creates comprehensive docs. | Delivers on time/quality. Enables x-functional alignment. | Solid tech background. Evaluates feasibility/architecture. | Data-driven decisions. RCA for recurring blockers. Systems thinking. |
| Senior TPM | Navigates moderate ambiguity. Defines approach. | Multiple teams spanning departments. Influences senior leaders. | Strat/Tactical. Drives complex execution. Proactive risk mgmt. | Clear, persuasive. Presents to senior leadership. | Delivers high-impact programs. Influences R&D strategy. | Deep understanding. Identifies tech risks; guides Eng decisions. | Drives process improvements. Resolves high-complexity problems. |
| Staff TPM | High ambiguity. Defines problems/solutions independently. | Department level. Drives org change and shapes how teams work. | Strategic. Leads high-complexity programs. Strategic trade-offs. | Communicates complex concepts to executives. | Drives business transformation. Improves velocity/efficiency. | Expert level. Drives architectural decisions & system implications. | Creates scalable processes. Systems thinking across interdependencies. |
Principal & Distinguished Levels
| Level | Ambiguity | Scope & Influence | Execution | Communication | Impact | Tech Expertise | Problem Solving |
|---|---|---|---|---|---|---|---|
| Senior Staff TPM (New) | Thrives in ambiguity. Sets direction. | Portfolio of programs across multiple departments/divisions. | Strategic. Orchestrates multiple complex programs. | Shapes narrative for executive audiences. | Dept-wide impact. Mentors Staff TPMs. | Thought leader. Influences tech standards across depts. | Establishes dept-wide standards. Eliminates recurring problems. |
| Principal TPM | Defines strategy in extreme ambiguity. Creates clarity. | Division scale. Influence extends to external stakeholders. | Strategic. Drives company-wide initiatives. Enterprise risk. | Masterful communicator to all (Board, Customers). | Company-wide impact (Revenue, Market position). | Visionary leader. Shapes R&D direction and tech excellence. | Redefines org operations. Escalation point for complex challenges. |
| Distinguished TPM | Creates new frameworks for unprecedented challenges. | Transformational initiatives. Influences Board/C-suite. | Strategic. Leads transformational initiatives. | Thought leader shaping org narrative. | Org-wide transformation. Competitive advantage. | Sets technical direction for multiple domains. | Transforms org capability/culture. Pioneers new approaches. |
2. Management Track
Functional Management
| Level | Ambiguity | Scope & Influence | Execution | Communication | Impact | Tech Expertise | Problem Solving |
|---|---|---|---|---|---|---|---|
| Manager | Operates in ambiguous environments. Creates frameworks. | Leads a team of ICs. Influence spans 1+ depts. Builds culture. | Strategic. Manages portfolio via teams. Resource allocation. | Influences across depts. Translates strategy into plans. | Multi-team success. Operational efficiency. TPM growth. | Strong tech judgment to guide teams on complex decisions. | Scales leadership. Standardizes practices. Tactical decisions. |
| Senior Manager | Leads through org ambiguity. Defines functional strategy. | Leads managers. Strategic partner to VPs/Execs. Owns talent strategy. | Strategic. Develops long-term strategy. Org design. Hiring. | Communicates vision to executives. Advocates for TPM. | TPM org health and capability. Job family development. | Thought partner to tech leadership on enterprise strategy. | Resolves complex business problems. Scrutinizes assumptions. |
Executive Leadership
| Level | Ambiguity | Scope & Influence | Execution | Communication | Impact | Tech Expertise | Problem Solving |
|---|---|---|---|---|---|---|---|
| Director | Creates clarity from strategic ambiguity (Division). | Leads managers across an entire division. Executive coaching. | Strategic. Sets dept strategy/ops model. Champions change. | Shapes org narrative. Communicates strategy to Execs. | Dept-wide effectiveness. Delivery enabling business goals. | Executive-level judgment. Influences tech strategy & transformation. | Resolves strategic company-wide problems. Long-term consequences. |
| Senior Director | Drives strategy across multi-division environments. | Leads across multiple divisions. Voice to C-suite/Board. | Strategic. Defines division-level strategy. Investment in capability. | Master communicator. Motivates large organizations. | Division-wide transformation. PM excellence at scale. | Shapes how org approaches tech strategy at scale. | Executes strategic plans. Reinvents business practices. |
| VP of TPM | Sets vision for PM in complex, evolving environments. | Vision/Strategy for the entire PM function. Influences CEO/Board. | Strategic. Creates org structure; quarterly planning. | Masterful communicator shaping company narrative. | Competitive advantage via execution. Exec team development. | Partners with CTO/CPO on company-wide tech strategy. | Organizational design expert. Translates strategy into principles. |
About GitLab
GitLab is an open core software company that develops the most comprehensive AI-powered DevSecOps Platform, used by more than 100,000 organizations. Our mission is to enable everyone to contribute to and co-create the software that powers our world. When everyone can contribute, consumers become contributors, significantly accelerating the rate of human progress. This mission is integral to our culture, influencing how we hire, build products, and lead our industry. We make this possible at GitLab by running our operations on our product and staying aligned with our values. Learn more about Life at GitLab. Thanks to products like Duo Enterprise, and Duo Workflow, customers get the benefit of AI at every stage of the SDLC. The same principles built into our products are reflected in how our team works: we embrace AI as a core productivity multiplier. All team members are encouraged and expected to incorporate AI into their daily workflows to drive efficiency, innovation, and impact across our global organisation.See our culture page for more!
Work remotely from anywhere in the world. Curious to see what that looks like? Check out our remote manifesto and guides.
cd4f2d3d)
