Product Manager

Product Managers at GitLab have a unique opportunity to define the future of the entire DevOps lifecycle

Product Management is a leadership role. Product managers make decisions and are accountable for identifying where an organization should invest its time and owning the outcomes of those investments. In product-led development, the product manager is given a crucial resource: engineering and design capacity. How this time is utilized influences the growth of the business.

PMs are not backlog groomers. They are not just facilitators. They are strategic operators with a clear point of view of what value we should build for our customers and why. Their value lies in their ability to:

Synthesize qualitative and quantitative inputs into a strategy
Define product direction that drives customer and business value
Make tradeoffs on behalf of the company, not just the team
Drive alignment across stakeholders
Ensure the right product gets built, not just the product that was asked for
Engage with customers. Frequently.

What PMs Own

PMs own the ‘what’ problems to solve and why they matter, while engineering owns the ‘how’ it’s built and when it can be delivered, and design owns the experience direction and how users interact with the solution.

PMs are responsible for:

Strategy & Direction: Forming a clear, evidence-based product strategy grounded in customer needs, competitive landscape, and company goals
Problem Framing: Understanding the customer journey, defining the jobs to be done, and identifying high-leverage opportunities
Outcomes: Tracking the impact of decisions through metrics, adoption, and business results
Cross-functional Leadership: Aligning engineering, design, marketing, sales, and customer success around a unified vision

Cross-Functional Decision-Making

While PMs make strategic product decisions, the best outcomes emerge from collaborative decision-making where each discipline leads within its domain:

UX Research and Design provides the evidence foundation, leads experience direction, and ensures solutions are user-centered
PM synthesizes inputs across domains and makes final strategic product calls
Engineering leads technical architecture decisions and validates feasibility

How does a PM ensure they are solving a problem for our users?

PMs should spend a significant amount of time understanding the problems our users face. Deeply understanding the problem is the foundation for all other activities PMs take on; understanding the problem enables the PM to define the vision and prioritize effectively.

In order for a PM to deeply understand the problems our users are facing and determine which are the important problems to solve, they can do the following:

Have a deep knowledge of each category’s problem space
Regularly talk with users and customers
Enagage with analysts in the market
Regularly complete competitive analysis
Communicate with users on issues and epics
Work with Pre-Sales and Post-Sales to connect with customers and prospects
Uncover insights through UX Research
Use other sensing mechanisms. It is through user interactions that we can begin to understand what problems our users are facing and identify how we could make product improvements to help eliminate the pain points. These user interactions can present themselves in many different ways.

How does a PM ensure we build lovable products?

Producing a lovable product requires more than a deep understanding of the problem. At GitLab, we build lovable products by adhering to our values. PMs are expected to be the ambassador of the GitLab values by:

Focusing on results.
Embracing iteration. This is the secret to GitLab moving fast, as we get constant feedback and maintain forward momentum toward GitLab’s huge vision. PMs play a large role in unlocking iteration as a competency.
Being transparent. This will enable both our development group to contribute and just as important, enable the wider GitLab community to contribute.
Being efficient. PMs should advocate for the boring solution, optimize for the right group, be the manager of one, always write things down, so they can help their groups also be efficient.
Being collaborative. PMs ultimately don’t ship anything on their own. PMs need to be a great teammate so that the development group can produce great work.
Being someone who helps make GitLab a work place of diversity, inclusion, and belonging, so that everyone can come to GitLab and do their best work.

Career paths

The job families are the single-source-of-truth (SSoT) for our job responsibilities related to career paths.

At A Glance

	PM (P3)	Senior PM (P4)	Staff PM (P5)	Principal PM (P6)
Scope	Single group, focused feature set	End-to-end product area, 1–2 teams	Cross-team domain, 3–5 teams	Company-level platforms or business lines, 5+ teams
Time Horizon	1–2 quarters	2–4 quarters	12–18 months	18–24 months
Strategy	Executes direction with a clear point of view	Shapes area strategy with minimal guidance	Defines portfolio direction across teams	Sets long-range company vision; shapes investment allocation
Customer & Market	Regular customer meetings; field-connected	Owns escalations; validates major bets	Strategic relationships across field leadership; competitive depth	Analyst relationships; market intelligence across domains
Outcomes	Launches with defined metrics; iterates	Material improvements in acquisition, adoption, or retention	Significant business impact within the stage	Durable competitive advantage; ARR or margin expansion
Data	Uses data to drive decisions	Owns north star and input metrics	Defines portfolio-level leading indicators; experimental rigor	Validates new business models; company-level measurement standards
Cross-Functional	Daily partnership with Eng & UX	SME recognized by peers; exec-ready narratives	Aligns senior Eng leaders; secures resources across teams	Trusted advisor to executives; aligns company priorities and GTM
Execution	Consistent delivery rhythm within the group	Orchestrates across teams; manages dependencies	Planning frameworks that scale across teams	Transformations that change how the org ships
Leadership	Seeks coaching; grows craft	Mentors junior PMs; models GitLab values	Coaches Seniors toward Staff readiness; sets craft standards	Develops multiple Staff PMs; fosters values org-wide

Product Manager

Job Grade: P3

Product Managers are decision-makers accountable for identifying where their group should invest engineering and design capacity, and owning the outcomes of those investments. They own the problems to solve and why they matter.

Scope: A focused feature set within one product area for a single group.

Time Horizon: 1–2 quarters with a 6–12 month roadmap horizon.

Product Strategy & Ownership

Maintains a clear, up-to-date strategy document for their group with GPM approval
Synthesizes customer, market, and engineering inputs into a prioritized direction
Articulates the “why” behind roadmap decisions with a clear point of view

Customer Insight & Engagement

Conducts regular customer meetings each quarter with actionable insights documented and tied to roadmap decisions
Partners with Sales, CS, and Support to stay field-connected
Validates solutions with customers before and during development

Outcome-Driven

Launches features with defined success metrics and demonstrates ability to pivot or stop low-value work
Measured by adoption and business outcomes, not feature volume
Monitors post-launch performance and iterates based on results

Data & Insights

Uses data to drive decisions, not justify them post-hoc
Partners with Analytics to define and validate success metrics
Can articulate leading indicators for their group’s key bets

Cross-Functional Leadership & Collaboration

Works daily with Engineering and UX as co-owners of outcomes
Supports Sales, CS, and escalations within their product area
Communicates group direction clearly to immediate counterparts

Operational Excellence

Produces clear, well-reasoned requirements that give engineers context and autonomy
Drives a consistent delivery rhythm; manages dependencies within the group
Escalates blockers cleanly and in a timely manner
Uses AI to increase their day-to-day efficiency

Innovation & Thought Leadership

Demonstrates learning velocity and continuously improving product judgment
Develops domain expertise in their product area
Actively seeks feedback and coaching from Senior PMs and their GPM; applies it to strengthen product judgment and craft
Demonstrates and applies GitLab values in day-to-day work and cross-functional collaboration

Senior Product Manager

Job Grade: P4

Senior Product Managers craft roadmaps that tell a clear story of where we’re heading and why. They move beyond features to drive material business impact through strategic decisions.

Scope: An end-to-end product area or platform capability across 1–2 teams.

Time Horizon: 2–4 quarters with a 12-month strategic horizon.

Product Strategy & Ownership

Maintains a signed-off strategy document with cross-functional alignment
Shapes the direction of their product area with minimal guidance; anticipates tradeoffs across adjacent groups
Identifies step-change opportunities beyond the current roadmap

Customer Insight & Engagement

Point-of-contact for escalated accounts; resolves the majority of escalations at their level
Builds direct relationships with key customers and internal field teams within their product area
Leads validation efforts for major bets within their group

Outcome-Driven

Delivers material improvements in acquisition, adoption/activation, or retention
Defines success metrics pre-launch and conducts post-launch retrospectives
Demonstrates ability to stop low-value work and reallocate investment

Data & Insights

Owns north star and input metrics for their area; maintains deep expertise in usage data
Identifies leading indicators and uses them to course-correct before lagging metrics move
Designs and runs experiments to validate strategic bets

Cross-Functional Leadership & Collaboration

Recognized by peers and counterparts as a subject matter expert in their domain
Creates exec-ready narratives; represents their area in stage-level planning
Mentors junior PMs informally and develops frameworks adopted by peers

Operational Excellence

Orchestrates delivery across teams; manages dependencies and risks proactively
Contributes to stage-level planning with well-reasoned investment cases
Models “right level of detail” — deep enough to surface risks, not lost in noise

Innovation & Thought Leadership

Develops frameworks or models adopted by peers
Coaches and mentors junior PMs; raises the bar for craft within the stage
Models GitLab values in cross-functional work; influences peers and partners through example
Engages externally (community, conferences) as a developing voice in their domain

Staff Product Manager

Job Grade: P5

Staff Product Managers are strategic operators with a clear point of view on what value we should build and why. They make trade-offs across sections, not just within the team, and ensure the right product is built, not just the one requested.

Scope: Complex cross-team domains or multi-surface journeys spanning 3–5 teams.

Time Horizon: 12–18 months with a 2–3 year strategic vision.

Product Strategy & Ownership

Develops and maintains a 12–18 month strategic direction connecting to the stage and company strategy
Shapes portfolio direction; identifies step-change opportunities with clear business cases and ROI projections
Explores partnership and acquisition opportunities; contributes to acquisition business cases

Customer Insight & Engagement

Cultivates strategic relationships with key customers, field leadership, and internal stakeholders across multiple teams
Develops a deep understanding of the closest competitors through technical docs, trials, and user discussions
Leads domain-specific validation efforts across stages

Outcome-Driven

Makes significant business impact (revenue, usage) within the stage
New feature launches meet success criteria post-launch within a defined time horizon; drives course-correction when they don’t
Demonstrates ability to pivot or stop low-value work and reallocate investment across the portfolio

Data & Insights

Defines leading indicators for the portfolio and ensures experimental rigor
Synthesizes signals at scale; designs experiment programs and measurement frameworks
Regularly conducts experiments in major feature areas; shares learnings to raise the bar across the stage

Cross-Functional Leadership & Collaboration

Aligns senior engineering leaders and cross-functional senior managers; secures resources across teams
Delivers persuasive storytelling to executives and key customers
Works across teams within the stage to drive alignment on roadmap priorities

Operational Excellence

Operational excellence in annual, quarterly, and monthly planning
Establishes principles and prioritization/sequencing frameworks that scale across teams
Leads user journey mapping initiatives that surface cross-team opportunities and inform portfolio decisions

Innovation & Thought Leadership

Sets craft standards; runs programs that elevate the PM organization or working groups to define new standards
Coaches and mentors Senior PMs toward Staff readiness
Capable of speaking at internal and external events; domain-specific conferences

Principal Product Manager

Job Grade: P6

Principal Product Managers drive alignment across stakeholders at the highest level, ensuring the organization invests in the right problems. Their value lies in their ability to synthesize inputs across the entire business into a company-level strategy.

Scope: Company-level problems — multi-product platforms, ecosystems, or new business lines across 5+ teams.

Time Horizon: 18–36 months with a durable vision and portfolio of bets.

Product Strategy & Ownership

Develops and communicates a 2–3 year strategic vision influencing section or company-level direction
Defines long-range strategy; anticipates market shifts; shapes investment allocation
Leads evaluation and recommendation of major strategic investments and partnerships
Establishes decision architecture — frameworks that help others make consistent, high-quality decisions
Champions platform-level initiatives that enhance GitLab’s competitive position

Customer Insight & Engagement

Establishes strategic relationships with key industry analysts and thought leaders
Synthesizes market intelligence across multiple product domains to identify emerging opportunities
Leads competitive intelligence efforts, informing strategic decisions
Builds systematic approaches to customer insight gathering that scale across teams
Represents Product in strategic conversations with key enterprise customers

Outcome-Driven

Drives durable competitive advantage and meaningful ARR or margin expansion
Makes investment recommendations balancing across multiple product areas for optimal business impact
Owns the company’s critical outcomes and external benchmarks

Data & Insights

Validates category creation or new business models with market and financial proof
Identifies and validates new market opportunities, driving significant business expansion
Establishes company-level measurement standards; defines the frameworks others use to design experiments and evaluate success

Cross-Functional Leadership & Collaboration

Trusted advisor to executives; aligns cross-company priorities and GTM narratives
Leads cross-functional initiatives requiring alignment across product, engineering, sales, and marketing
Resolves complex organizational challenges spanning multiple functional areas
Mentors and develops multiple Staff PMs with measurable impact

Operational Excellence

Leads transformations or broad initiatives that change how the organization ships
Establishes frameworks and processes to improve product organization effectiveness

Innovation & Thought Leadership

Serves as external spokesperson for GitLab’s product vision at industry events
Influences industry direction through thought leadership, publications, and strategic partnerships
Leads product narrative development for major launches and strategic initiatives
Champions and leads M&A research, evaluation, and recommendation efforts
Elevates culture and talent; builds succession for strategic domains
Fosters decision-making and problem-solving aligned with GitLab values across the product organization

Moving from Product Management

Within their role, Product Managers are empowered to interact and learn more about functions they are interested in. Whether that be Marketing, Customer Success, Support, Finance or Engineering - Product Managers are encouraged (and often required) to understand other functions as part of their daily responsibilities. As such there is plenty of room for Product Managers to transition to roles outside of the Product Management team. Some of those include:

Engineering Leadership: Product Managers often find a desire to dive deeper into Engineering problems, or grow mentor and lead engineering teams.
Product Marketing: Product Managers often gravitate to how we target, message and deliver value to our customers. Product Marketing roles are an excellent way to further that expertise.
Customer Success: Few people know our products as well as Product Managers, and product managers who enjoy directly solving customers problems on a daily basis make great fits for Customer Success roles.
General Management: As a result of their exposure to a wide variety of functions, Product Managers often make a transition from Product Management to General Management.

Interview process

Interview Process

Recruiter Screen with one of our global recruiters. Expect to discuss your background, your experience in relation to the role, your core PM comptencies, compensation expectations and a time for your questions at the end. Typically 30-45 minutes.
Hiring Manager Interview - This interview will touch on a number of topics to determine product management, company and values fit for the PM team at GitLab. 45 minutes.
Deep Dive Interview - The goal of this interview is to understand your ability to communicate a long term vision as well as short term MVC, both verbally during the interview itself, and written via a couple of follow up issues. The PM interviewer will provide feedback and see how you respond to that feedback. This mimics the way we operate at GitLab. 45 minutes + a couple of follow ups.
Engineering Manager and Product Design Interview - You will meet with stable-counterparts in Engineering and UX where we will be assessing your collaboration, soft skills, and development group fit. 45 minutes.
Leadership Interview - The final interview will focus on two main areas, your product thinking as well as a case interview to determine your business skills. 60 minutes.

Relevant links

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.

Last modified April 9, 2026: Remove trailing spaces (edd8c656)

View page source - Edit this page - please contribute.