GTM Product Operations Specialist II

We need to output HTML fragment with sections only if real content. No job title heading. No metadata like Job ID. Remove boilerplate: EEO, equal-opportunity, scam warning, application instructions, cookie/navigation/legal. Also remove duplicated lines. Keep substantive info. We need to parse the posting. Content: Intro: "Are you a dreamer, innovator, thinker and a do-er who believes in contributing to something that makes difference? Make an impact. Join PMI. How will you make a difference to PMI? PMI is seeking a GTM Product Operations Specialist II who supports the operational execution of PMI’s product launch and update processes. This role focuses on documentation, deliverable coordination, asset trafficking, and cross-functional support to ensure accurate, timely, and consistent GTM execution across PMI’s product portfolio. Specialists write concise operational copy (not strategic messaging), maintain GTM materials, manage approvals, and support readiness steps once the GTM Product Marketing Strategy team has defined positioning, messaging, and value propositions. This role is foundational to keep GTM workflows moving and ensuring organizational readiness for every product change." Then "What You’ll Bring To The Role" with subheadings: GTM Workflow Execution, Operational Copywriting & Documentation, Cross-Functional Coordination, Enablement & Readiness Support, Operational Reporting & Process Support. Then "Role Qualifications" bullet list. Then "What you can expect from us" paragraph: includes inclusive environment, health safety, etc. Then bullet list: Join Us And You’ll Get an excellent total package, with compensation and benefits based upon your geographic location. skill development opportunities, to help you grow now and into the future. access to a global network, to enrich your professional experience. flexible options to help balance work time and your time award and bonus opportunities. The salary offer will be based on several factors, including the candidate’s demonstrated skills, qualifications and relevant experience. Then "Let’s help make the world work better for everyone. Apply today!" (application instruction - remove). Then EEO statement (remove). Also "Project Management Institute, Inc. is committed to providing equal employment opportunities..." remove. Also "Some travel, possibly up to 15%, conditions permitting." appears in Qualifications? Actually after Qualifications list: "Proficiency in the business language for PMI (English).Some travel, possibly up to 15%, conditions permitting." Then "Requirements include ability to travel nationally and globally and may occur over weekends or holidays". That's travel requirement. We need to keep travel info maybe under Qualifications or Requirements? It's part of qualifications. We'll keep as part of Qualifications. We need sections: maybe About the role (intro), Responsibilities (the What You’ll Bring To The Role subpoints), Qualifications (Role Qualifications + travel), Benefits (What you can expect from us). Pay and Schedule: not explicitly stated; we should not create them unless present. There's mention of compensation and benefits based on geographic location, but no specific salary. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does mention compensation and benefits based on location, but not specific numbers. Is that enough to create Benefits section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "compensation and benefits based upon your geographic location." That's a statement about benefits existing. So we can include a Benefits section with that info. However also they list skill development opportunities, global network, flexible options, award and bonus opportunities. Those are benefits. So we can create Benefits section. Pay: not specific salary; they say "The salary offer will be based on several factors..." That's a statement about pay but not specific. Should we create Pay section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state that salary offer will be based on factors. That's a statement about pay. So we could include Pay section with that statement. However they also said "compensation and benefits based upon your geographic location." That's also pay/benefits. I'd include a Pay section with that statement, and Benefits section with the list. Schedule: not mentioned; no schedule info. So omit Schedule. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which headings to use. We have About the role (intro). Responsibilities (the What You’ll Bring To The Role). Qualifications (Role Qualifications). Benefits (What you can expect from us). Pay (salary statement). Possibly Skills? Not separate; qualifications include skills. Could combine Skills into Qualifications. But we could have a Skills section if we want, but better to keep few substantive sections. The instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Qualifications, Benefits, Pay. That's five sections. We must not repeat job title as heading. Good. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities we have bullet points under each subheading? The original had headings: GTM Workflow Execution, Operational Copywriting & Documentation, Cross-Functional Coordination, Enablement & Readiness Support, Operational Reporting & Process Support. Each with a paragraph. We could treat each as a list item under Responsibilities? Or we could keep subheadings as

  ? But only allowed headings are

  for section headings. We could still use

  for each responsibility subheading? That would be many sections. Better to keep Responsibilities as a section with a

  • list summarizing each duty. But we must preserve ALL substantive information; do not invent or summarize away detail. Summarizing may lose detail. We need to keep the detail but can we keep the subheadings as

    ? Not allowed per instruction: only

    for section headings. It didn't forbid other headings like

    , but said use

    for section headings (e.g. About the role, Responsibilities...). It didn't say we cannot use other heading levels. However to be safe, we can use

    for main sections and within them use

    for prose and

    • for lists. For the responsibilities we could keep the subheadings as or just as part of list items. But we need to preserve the detail; we can include the subheading text inside the list item as a bold phrase. Thus Responsibilities section:
      • GTM Workflow Execution: Execute assigned GTM tasks across launches, updates, and product lifecycle workflows. Maintain timelines, trackers, and dependency logs; escalate risks as needed. Ensure deliverables follow established templates and standards. Support launch readiness checkpoints by preparing materials and summaries.
      ... etc. Similarly for each. Qualifications: we have bullet list. We'll make
      • each. Benefits: list from "Join Us And You’ll Get ..." plus skill development opportunities etc. We'll make
        • . Pay: statement about salary offer based on factors. We'll put in

          . We need to remove boilerplate: EEO, application instructions, etc. Let's craft HTML. Start with maybe not needed; just output fragment. We'll do:

          About the role

          ... intro paragraph(s) ...

          Responsibilities

          • GTM Workflow Execution: Execute assigned GTM tasks across launches, updates, and product lifecycle workflows. Maintain timelines, trackers, and dependency logs; escalate risks as needed. Ensure deliverables follow established templates and standards. Support launch readiness checkpoints by preparing materials and summaries.
          • Operational Copywriting & Documentation: Write concise, structured operational documentation, including: release notes, product update summaries, internal FAQs, readiness checklists, basic product descriptions aligned to approved messaging. Ensure accuracy, clarity, and alignment with the messaging hierarchy prepared by the GTM Strategy team. Maintain up-to-date documentation libraries and version control.
          • Cross-Functional Coordination: Coordinate with Brand, Product, CX, and Regional Marketing to gather required inputs. Manage asset trafficking, routing materials through review and approval cycles. Support meeting preparation, including agendas, notes, decisions, and action items.
          • Enablement & Readiness Support: Prepare internal enablement materials and documentation for downstream teams. Assist with distributing updates, training materials, or communications. Ensure relevant stakeholders understand changes, timelines, and deliverables.
          • Operational Reporting & Process Support: Update dashboards, GTM trackers, and reporting tools. Maintain accurate records of tasks, progress, and status updates. Support process improvements by capturing bottlenecks or inefficiencies.

          Qualifications

          • Bachelor’s degree in Marketing, Communications, Business, or related field preferred.
          • 3+ years of experience in product marketing, marketing operations, PMO, or related roles.
          • Experience in documentation, project coordination, or workflow management is a plus.
          • Exposure to product marketing or GTM concepts helpful but not required.
          • Writing: Skilled at concise, structured operational copy (not strategic content).
          • Organization: Highly detail-oriented with strong task and time management.
          • Project Coordination: Ability to manage multiple deliverables and follow structured workflows.
          • Communication: Clear, consistent communicator; strong listening and documentation skills.
          • Tool Proficiency: Comfortable with project management tools, documentation systems, and collaboration platforms.
          • Process Discipline: Ability to follow templates, frameworks, and operational guidelines.
          • Cross-Functional Collaboration: Works well with Product, Brand, and Region teams.
          • Quality Orientation: Ensures accuracy, consistency, and adherence to standards.
          • Proficiency in the business language for PMI (English).
          • Some travel, possibly up to 15%, conditions permitting.
          • Ability to travel nationally and globally, possibly over weekends or holidays.

          Benefits

          • Excellent total package, with compensation and benefits based upon your geographic location.
          • Skill development opportunities, to help you grow now and into the future.
          • Access to a global network, to enrich your professional experience.
          • Flexible options to help balance work time and your time.
          • Award and bonus opportunities.

          Pay

          The salary offer will be based on several factors, including the candidate’s demonstrated skills, qualifications and relevant experience.

          Check for any leftover boilerplate: removed EEO, apply today, etc. Also removed "Let’s help make the world work better for everyone. Apply today!" Good. Check for duplicated lines: none. Check for any mention of "Project Management Institute, Inc." - that's boilerplate? It's the company name; could be considered part of the posting but not required. It's not EEO. Might be okay to keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company name is not boilerplate; it's fine to keep but we didn't include it. It's okay. Check for any mention of "We value and nurture an environment of inclusivity and diversity, and a culture of communication and collaboration. Your health, safety and well-being come first, and we believe that you should have time for your work, but you should also have time for you.." That's part of benefits? Could be included in Benefits section as a bullet. We omitted it. Should we include? It's substantive about culture. Could be added as a bullet under Benefits. Let