Senior Manager, Technical Program Management

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. First, there's a lot of introductory fluff about GitLab, but we need to preserve substantive info. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, cookie/navigation etc. We need to extract sections: "An Overview Of This Role" maybe corresponds to About the role. Then "What You’ll Do" is Responsibilities. Then "What You’ll Bring" is Requirements/Qualifications/Skills. Then "About The Team" maybe part of About the role? Could be separate but we can include as part of About the role. Then "How GitLab Supports Full-Time Employees Benefits to support your health, finances, and well-being" then bullet list of benefits: Flexible Paid Time Off, Team Member Resource Groups, Equity Compensation & Employee Stock Purchase Plan, Growth and Development Fund, Parental Leave. That's Benefits. Pay and Schedule: Not mentioned. So we should not include Pay or Schedule sections. We also need to include any other sections like maybe "Qualifications" separate from Requirements? The posting includes "What You’ll Bring" which includes prior experience, ability to prioritize, proven track record, etc. That's qualifications/requirements/skills. We can put them under a single section like Requirements or Qualifications. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which to include based on content. Probably include About the role, Responsibilities, Requirements (or Qualifications), Benefits. Could also include Skills if we separate but not needed. We must not repeat the job title as heading. The job title is Sr Manager, Technical Program Management. Not to be used as heading. We must not include Job ID/requisition numbers. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details from the posting. We need to format using

for headings,

• for lists,

  for prose. We need to remove boilerplate: EEO, privacy policy, etc. Also remove duplicated lines. Let's extract substantive content: Intro paragraph about GitLab: "GitLab is the intelligent orchestration platform for DevSecOps. GitLab enables organizations to increase developer productivity, improve operational efficiency, reduce security and compliance risk, and accelerate digital transformation. More than 50 million registered users and more than 50% of the Fortune 100* trust GitLab to ship better, more secure software faster. The same principles built into our products are reflected in how our team works: we embrace AI as a core productivity multiplier, with all team members expected to incorporate AI into their daily workflows to drive efficiency, innovation, and impact. GitLab is where careers accelerate, innovation flourishes, and every voice is valued. Our high-performance culture is driven by our values and continuous knowledge exchange, enabling our team members to reach their full potential while collaborating with industry leaders to solve complex problems. Co-create the future with us as we build technology that transforms how the world develops software." That's substantive about company; we could include as part of About the role? Possibly we could include a brief "About GitLab" but not required headings. The instruction says to use headings for sections like About the role, Responsibilities, etc. The company overview could be part of About the role. We'll include it under About the role. Then "An Overview Of This Role" paragraph: "We're looking for an experienced Sr Manager, Technical Program Management to lead a team of TPMs in our Engineering org. Our R&D PMO is a new team within GitLab Engineering, so this is a great opportunity to help build out a new function and define the future of Program Management at GitLab. This individual will be responsible for leading a team of TPMs of varying levels, all working on different areas of the Product. The Sr. Manager, Technical Program Management will work closely with Product and Engineering leadership to ensure that TPMs are assigned to high priority programs and that they are successfully delivering results for customers. In addition to managing a team, this leadership position will also contribute to the long-term operational success of the R&D organization by partnering with leaders to develop new planning cadences and other improvements to our ways of working." That's About the role. Then "What You’ll Do" responsibilities list: many bullet-like sentences but not formatted as list. We need to convert to

  • . The text: "Responsible for directly GitLab team members performing in the role of Technical Program Manager. Lead and mentor a team of Technical Program Managers, including providing regular feedback to foster their growth and ensure their success. Responsible for staffing requirements for the PMO, in partnership with the Director of Technical Program Management and the Product and engineering Leadership groups. Align TPM team resourcing / assignments with the company’s business objectives. Create and maintain program management standards for elements including program documentation, project plans, status reports, post-mortems as well as a team direction north star; work to continuously improve and iterate on these processes. Create and maintain a long-term strategy and vision for the Program Management function, in alignment with broader company goals. Develop and expand upon the job family, CDF, and long-term hiring and growth objectives for the Technical Program Management function. Build strong relationships with cross-functional stakeholders including Engineering, Product, Security, and GTM teams. Identify and mitigate risks, resolve conflicts, and remove obstacles for the Technical Program Management team to ensure timely program delivery. Establish and track key performance indicators (KPIs) for programs and team members and hold the team accountable for meeting commitments. Lead strategic planning with direct influence over staffing decisions, project timelines, and planning stakeholders. Demonstrate leadership as expected of Managers across GitLab and Embody our CREDIT values in your work" We need to preserve all. We'll make each line a
  • . Then "What You’ll Bring": list of qualifications: "Prior experience as a people manager and as an IC TPM, ideally in a position of seniority Ability to prioritize and delegate work effectively Proven track record of successful collaboration with internal and external stakeholders Experience developing and executing on strategic team development plans Ability to coach others on driving cross functional product-driven initiatives, without direct control of the programs Proven ability to position oneself and the team as trusted partners and thought leaders More information about the Sr Manager Job Family is available in our handbook." We'll make each a
  • under Requirements or Qualifications. Then "About The Team": paragraph: "Our Technical Program Management function is relatively new to GitLab; we are building out a PMO that is centralized within Engineering and looking for strong TPMs that are interested in developing a newly formed PMO and standardizing on best practices for the business. You can learn more about the PMO in our handbook page." We could include under About the role or separate section like About the Team but not a standard heading. Could merge into About the role. Then benefits: "How GitLab Supports Full-Time Employees Benefits to support your health, finances, and well-beingFlexible Paid Time Off Team Member Resource GroupsEquity Compensation & Employee Stock Purchase PlanGrowth and Development FundParental Leave" We need to format as list. The text seems missing punctuation; we can treat each as separate benefit. Thus Benefits section with
    • Flexible Paid Time Off
    etc. We must not include Pay or Schedule. We also need to remove boilerplate like "Please note that we welcome interest from candidates with varying levels of experience; many successful candidates do not meet every single requirement. Additionally, studies have shown that people from underrepresented groups are less likely to apply to a job unless they meet every single qualification. If you're excited about this role, please apply and allow our recruiters to assess your application." That's application instructions? It's encouraging to apply; but instruction says remove application instructions. So we should remove that paragraph. Also remove "Country Hiring Guidelines: ..." etc. Also remove Privacy Policy, EEO statements. Thus final HTML:

    About the role

    GitLab is the intelligent orchestration platform for DevSecOps. GitLab enables organizations to increase developer productivity, improve operational efficiency, reduce security and compliance risk, and accelerate digital transformation. More than 50 million registered users and more than 50% of the Fortune 100* trust GitLab to ship better, more secure software faster. The same principles built into our products are reflected in how our team works: we embrace AI as a core productivity multiplier, with all team members expected to incorporate AI into their daily workflows to drive efficiency, innovation, and impact. GitLab is where careers accelerate, innovation flourishes, and every voice is valued. Our high-performance culture is driven by our values and continuous knowledge exchange, enabling our team members to reach their full potential while collaborating with industry leaders to solve complex problems. Co-create the future with us as we build technology that transforms how the world develops software.

    We're looking for an experienced Sr Manager, Technical Program Management to lead a team of TPMs in our Engineering org. Our R&D PMO is a new team within GitLab Engineering, so this is a great opportunity to help build out a new function and define the future of Program Management at GitLab. This individual will be responsible for leading a team of TPMs of varying levels, all working on different areas of the Product. The Sr. Manager, Technical Program Management will work closely with Product and Engineering leadership to ensure that TPMs are assigned to high priority programs and that they are successfully delivering results for customers. In addition to managing a team, this leadership position will also contribute to the long-term operational success of the R&D organization by partnering with leaders to develop new planning cadences and other improvements to our ways of working.

    Our Technical Program Management function is relatively new to GitLab; we are building out a PMO that is centralized within Engineering and looking for strong TPMs that are interested in developing a newly formed PMO and standardizing on best practices for the business. You can learn more about the PMO in our handbook page.

    Responsibilities

    • Responsible for directly GitLab team members performing in the role of Technical Program Manager.
    • Lead and mentor a team of Technical Program Managers, including providing regular feedback to foster their growth and ensure their success.
    • Responsible for staffing requirements for the PMO, in partnership with the Director of Technical Program Management and the Product and engineering Leadership groups.
    • Align TPM team resourcing / assignments with the company’s business objectives.
    • Create and maintain program management standards for elements including program documentation, project plans, status reports, post-mortems as well as a team direction north star; work to continuously improve and iterate on these processes.
    • Create and maintain a long-term strategy and vision for the Program Management function, in alignment with broader company goals.
    • Develop and expand upon the job family, CDF, and long-term hiring and growth objectives for the Technical Program Management function.
    • Build strong relationships with cross-functional stakeholders including Engineering, Product, Security, and GTM teams.
    • Identify and mitigate risks, resolve conflicts, and remove obstacles for the Technical Program Management team to ensure timely program delivery.
    • Establish and track key performance indicators (KPIs) for programs and team members and hold the team accountable for meeting commitments.
    • Lead strategic planning with direct influence over staffing decisions, project timelines, and planning stakeholders.
    • Demonstrate leadership as expected of Managers across GitLab and Embody our CREDIT values in your work.

    Requirements

    • Prior experience as a people manager and as an IC TPM, ideally in a position of seniority
    • Ability to prioritize and delegate work effectively