Vice President, GTM Strategic Programs & Operations
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to decide which sections to include based on content.
Content includes:
- Who are we? (company description) Could be "About the role"? Actually "Who are we?" is about company, not role. Could be "About the role"? Not exactly. But we could treat as "About the role" maybe not. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings where appropriate.
We have:
- Job Summary: description of role responsibilities (some overlapping with responsibilities). Could be part of About the role or Responsibilities.
- Responsibilities: detailed list.
- Qualifications: knowledge & experience.
- Skills & Attributes: skills.
- Pay: targeted pay range.
- Benefits: Equinix Benefits description.
- Schedule: not mentioned.
Thus we should include sections: About the role (maybe from Job Summary), Responsibilities, Qualifications, Skills, Pay, Benefits.
We must not include schedule.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include the details from each section.
We must use
for each section heading.
Inside sections, we need to use
for prose, and
- for any list of duties/requirements/benefits.
We need to extract lists.
Let's parse:
Who are we? (company description) maybe we can put under About the role? But it's about company not role. However we could still include as About the role? Might be okay. But maybe better to treat as About the role (since it's about the role context). The instruction says "About the role" is an example heading; we can use it for role overview.
Job Summary: "The VP, GTM Strategic Programs & Operations is the single accountable business owner for the Lead-to-Cash (LTC) program and the primary CRO-side counterpart to the CDIO program lead. While the CDIO organization owns technology delivery, this role ensures the business is prepared at every stage: that scope decisions reflect CRO priorities, that design sign-offs are grounded in requirements, that testing is thorough, and that go-live decisions are made with full visibility into business risk. The role reports to the SVP of GTM Ops within the CRO organization and owns the CRO-side program budget, including headcount and vendor resources."
That's prose.
Responsibilities: multiple bullet-like paragraphs but not bullet list. It includes sections: Team Leadership and Program Governance, Scope, Sequencing, and Prioritization, Solution Design and Sign-Off, Business Readiness and Testing, Business Continuity and Risk Management. Each has sentences. We could treat each as a list item? The instruction says use
- for any list of duties/requirements/benefits. The responsibilities are not explicitly bullet list but we can still treat each major duty as a list item. However we need to preserve all substantive information; we could keep them as paragraphs under Responsibilities heading, but then we wouldn't be using
- . The instruction says use
- for any list of duties/requirements/benefits. If we don't have explicit list, we could still use
. But to be safe, we can convert each duty into
- . That would be a list.
Let's extract duties:
From Responsibilities section:
- Team Leadership and Program Governance:
- Lead a dedicated team: Technical Program Manager, Business Architecture & Scope Lead, Business Readiness Lead, Solution Design Lead, and Continuity/Change Lead
- Indirectly manage Business Context Experts allocated 25-30% of their time to the program, representing Marketing & Lead Generation, Pipe & Forecast Management, Renewal Management, Quote Management, Order Management, Service Delivery (CSM/SM), Customer Support, Account & Territory Management, and Sales Compensation
- Own the CRO-side program budget, covering headcount, dedicated resources, and vendor allocations
- Serve as the single CRO counterpart and CROLT proxy to the CDIO program lead and the escalation path for cross-priority conflicts that cannot be resolved at the team level
- Scope, Sequencing, and Prioritization:
- Convene business stakeholders across CRO domains to determine scope by functional area, ensure business logic and requirements are documented, and resolve conflicts when domain priorities compete
- Drive sequencing and prioritization decisions across the nine functional areas, balancing business need with organizational capacity
- Prevent premature scope expansion by coordinating resolution of open scope questions before design advances
- Solution Design and Sign-Off:
- Ensure Business Context Experts and the Solution Design Lead are engaged at each design stage, with formal business signoff secured before designs are finalized
- Flag design drift early and maintain traceability between business requirements and solution decisions
- Business Readiness and Testing:
- Define success metrics and readiness criteria by domain, working with the Business Readiness Lead and functional experts
- Ensure testing plans are adequately scoped and resourced across all CRO domains; confirm defects are resolved to business standards before go-live is considered
- Lead senior stakeholder alignment on go/no-go decisions and align the organization on execution once a decision is made
- Drive organizational alignment before, during, and after go-live so the transformation is adopted as a business change, not simply a technology deployment
- Business Continuity and Risk Management:
- Surface business risk across domains, maintain workable co-existence strategies and fallback plans, and facilitate risk-based reprioritization when program conditions change
- Represent the CRO organization's risk posture in joint program governance with the CDIO organization and executive leadership
We can list each bullet as
- .
Qualifications: "Knowledge & Experience" bullet list:
- Deep program or project management experience, with at least 5 years leading cross-functional programs at a senior level
- Proven experience leading the business side of a major systems transformation or implementation, with accountability for scope, readiness, and organizational adoption rather than technology delivery
- Track record managing revenue operations programs that span multiple CRO functions, such as sales, marketing, renewals, customer success, order management, or billing
- Experience building and leading a dedicated program team while coordinating matrixed contributors who carry competing day-job responsibilities
- Budget ownership experience, including headcount planning and vendor management at the program level
- Track record facilitating executive-level prioritization decisions, managing escalations, and maintaining stakeholder alignment through extended program complexity
We can list as
- .
Skills & Attributes: list:
- Ability to operate in high-ambiguity environments where scope, timelines, and resource constraints shift
- Executive presence and credibility with senior stakeholders, able to frame trade-offs crisply and drive go/no-go decisions without escalation becoming the default
- Structured decision-making under pressure, with the judgment to distinguish a genuine business risk from a delivery inconvenience
- Fluency in translating between business requirements and technical solution design, conversant enough with system architecture to challenge design decisions, without owning delivery
- Facilitation and conflict resolution skills across competing functional priorities, driving to a decision rather than a compromise that satisfies no one
Pay: targeted pay range details: three locations with same range: United States - Redwood City Office GHQ : 248,000 - 372,000 USD / Annual; United States - Dallas Infomart Office DAI : 248,000 - 372,000 USD / Annual; United States - Seattle Office SEO : 248,000 - 372,000 USD / Annual. Also note about pay range etc. We need to preserve all substantive information. So we should include that paragraph.
Benefits: Equinix Benefits description includes several paragraphs. We need to preserve all substantive information. Could be a
with the text. Also there is a list of US Benefits: Insurance, Retirement, Paid Time Off (PTO) and Paid Holidays. That's a list. So we should use
- for that list.
We must remove boilerplate: EEO, accommodation, AI, etc. Also remove duplicated lines. Also remove "Our pay ranges reflect..." etc? That is substantive? It's about pay range determination; we should keep as it's part of Pay section. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we keep that explanation.
We also need to remove "Equinix Benefits As an employee, you become important to Equinix’s success..." etc. That's substantive; keep.
We need to remove the EEO paragraph and the accommodation request, AI, etc.
Also remove "This posting is a new position within our organization." maybe not substantive? It's minor; could drop.
Now construct HTML.
We'll have sections:
About the role
Who are we? Equinix is the world’s digital infrastructure company®, shortening the path to connectivity to enable the innovations that enrich our work, life and planet. A place where bold ideas are welcomed, human connection is valued, and everyone has the opportunity to shape their future. A career at Equinix means being at the center of shaping what comes next and amplifying customer value through innovation and impact. You’ll work across teams, influence key decisions, and help shape the path forward. You’ll find belonging, purpose, and a team that welcomes you—because when you feel valued, you’re empowered to do your best work.
The VP, GTM Strategic Programs & Operations is the single accountable business owner for the Lead-to-Cash (LTC) program and the primary CRO-side counterpart to the CDIO program lead. While the CDIO organization owns technology delivery, this role ensures the business is prepared at every stage: that scope decisions reflect CRO priorities, that design sign-offs are grounded in requirements, that testing is thorough, and that go-live decisions are made with full visibility into business risk. The role reports to the SVP of GTM Ops within the CRO organization and owns the CRO-side program budget, including headcount and vendor resources.
But note we duplicated "Who are we?" maybe we should keep as part of About the role. That's fine.
Next:
Responsibilities
- Lead a dedicated team: Technical Program Manager, Business Architecture & Scope Lead, Business Readiness Lead, Solution Design Lead, and Continuity/Change Lead
- Indirectly manage Business Context Experts allocated 25-30% of their time to the program, representing Marketing & Lead Generation, Pipe & Forecast Management, Renewal Management, Quote Management, Order Management, Service Delivery (CSM/SM), Customer Support, Account & Territory Management, and Sales Compensation
- Own the CRO-side program budget, covering headcount, dedicated resources, and vendor allocations
- Serve as the single CRO counterpart and C
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include based on content. Content includes: - Who are we? (company description) Could be "About the role"? Actually "Who are we?" is about company, not role. Could be "About the role"? Not exactly. But we could treat as "About the role" maybe not. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings where appropriate. We have: - Job Summary: description of role responsibilities (some overlapping with responsibilities). Could be part of About the role or Responsibilities. - Responsibilities: detailed list. - Qualifications: knowledge & experience. - Skills & Attributes: skills. - Pay: targeted pay range. - Benefits: Equinix Benefits description. - Schedule: not mentioned. Thus we should include sections: About the role (maybe from Job Summary), Responsibilities, Qualifications, Skills, Pay, Benefits. We must not include schedule. We need to preserve all substantive information, not invent or summarize away detail. So we need to include the details from each section. We must use
for each section heading. Inside sections, we need to use
for prose, and
- for any list of duties/requirements/benefits.
We need to extract lists.
Let's parse:
Who are we? (company description) maybe we can put under About the role? But it's about company not role. However we could still include as About the role? Might be okay. But maybe better to treat as About the role (since it's about the role context). The instruction says "About the role" is an example heading; we can use it for role overview.
Job Summary: "The VP, GTM Strategic Programs & Operations is the single accountable business owner for the Lead-to-Cash (LTC) program and the primary CRO-side counterpart to the CDIO program lead. While the CDIO organization owns technology delivery, this role ensures the business is prepared at every stage: that scope decisions reflect CRO priorities, that design sign-offs are grounded in requirements, that testing is thorough, and that go-live decisions are made with full visibility into business risk. The role reports to the SVP of GTM Ops within the CRO organization and owns the CRO-side program budget, including headcount and vendor resources."
That's prose.
Responsibilities: multiple bullet-like paragraphs but not bullet list. It includes sections: Team Leadership and Program Governance, Scope, Sequencing, and Prioritization, Solution Design and Sign-Off, Business Readiness and Testing, Business Continuity and Risk Management. Each has sentences. We could treat each as a list item? The instruction says use
- for any list of duties/requirements/benefits. The responsibilities are not explicitly bullet list but we can still treat each major duty as a list item. However we need to preserve all substantive information; we could keep them as paragraphs under Responsibilities heading, but then we wouldn't be using
- . The instruction says use
- for any list of duties/requirements/benefits. If we don't have explicit list, we could still use
. But to be safe, we can convert each duty into
- . That would be a list. Let's extract duties: From Responsibilities section: - Team Leadership and Program Governance: - Lead a dedicated team: Technical Program Manager, Business Architecture & Scope Lead, Business Readiness Lead, Solution Design Lead, and Continuity/Change Lead - Indirectly manage Business Context Experts allocated 25-30% of their time to the program, representing Marketing & Lead Generation, Pipe & Forecast Management, Renewal Management, Quote Management, Order Management, Service Delivery (CSM/SM), Customer Support, Account & Territory Management, and Sales Compensation - Own the CRO-side program budget, covering headcount, dedicated resources, and vendor allocations - Serve as the single CRO counterpart and CROLT proxy to the CDIO program lead and the escalation path for cross-priority conflicts that cannot be resolved at the team level - Scope, Sequencing, and Prioritization: - Convene business stakeholders across CRO domains to determine scope by functional area, ensure business logic and requirements are documented, and resolve conflicts when domain priorities compete - Drive sequencing and prioritization decisions across the nine functional areas, balancing business need with organizational capacity - Prevent premature scope expansion by coordinating resolution of open scope questions before design advances - Solution Design and Sign-Off: - Ensure Business Context Experts and the Solution Design Lead are engaged at each design stage, with formal business signoff secured before designs are finalized - Flag design drift early and maintain traceability between business requirements and solution decisions - Business Readiness and Testing: - Define success metrics and readiness criteria by domain, working with the Business Readiness Lead and functional experts - Ensure testing plans are adequately scoped and resourced across all CRO domains; confirm defects are resolved to business standards before go-live is considered - Lead senior stakeholder alignment on go/no-go decisions and align the organization on execution once a decision is made - Drive organizational alignment before, during, and after go-live so the transformation is adopted as a business change, not simply a technology deployment - Business Continuity and Risk Management: - Surface business risk across domains, maintain workable co-existence strategies and fallback plans, and facilitate risk-based reprioritization when program conditions change - Represent the CRO organization's risk posture in joint program governance with the CDIO organization and executive leadership We can list each bullet as
- .
Qualifications: "Knowledge & Experience" bullet list:
- Deep program or project management experience, with at least 5 years leading cross-functional programs at a senior level
- Proven experience leading the business side of a major systems transformation or implementation, with accountability for scope, readiness, and organizational adoption rather than technology delivery
- Track record managing revenue operations programs that span multiple CRO functions, such as sales, marketing, renewals, customer success, order management, or billing
- Experience building and leading a dedicated program team while coordinating matrixed contributors who carry competing day-job responsibilities
- Budget ownership experience, including headcount planning and vendor management at the program level
- Track record facilitating executive-level prioritization decisions, managing escalations, and maintaining stakeholder alignment through extended program complexity
We can list as
- .
Skills & Attributes: list:
- Ability to operate in high-ambiguity environments where scope, timelines, and resource constraints shift
- Executive presence and credibility with senior stakeholders, able to frame trade-offs crisply and drive go/no-go decisions without escalation becoming the default
- Structured decision-making under pressure, with the judgment to distinguish a genuine business risk from a delivery inconvenience
- Fluency in translating between business requirements and technical solution design, conversant enough with system architecture to challenge design decisions, without owning delivery
- Facilitation and conflict resolution skills across competing functional priorities, driving to a decision rather than a compromise that satisfies no one
Pay: targeted pay range details: three locations with same range: United States - Redwood City Office GHQ : 248,000 - 372,000 USD / Annual; United States - Dallas Infomart Office DAI : 248,000 - 372,000 USD / Annual; United States - Seattle Office SEO : 248,000 - 372,000 USD / Annual. Also note about pay range etc. We need to preserve all substantive information. So we should include that paragraph.
Benefits: Equinix Benefits description includes several paragraphs. We need to preserve all substantive information. Could be a
with the text. Also there is a list of US Benefits: Insurance, Retirement, Paid Time Off (PTO) and Paid Holidays. That's a list. So we should use
- for that list.
We must remove boilerplate: EEO, accommodation, AI, etc. Also remove duplicated lines. Also remove "Our pay ranges reflect..." etc? That is substantive? It's about pay range determination; we should keep as it's part of Pay section. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we keep that explanation.
We also need to remove "Equinix Benefits As an employee, you become important to Equinix’s success..." etc. That's substantive; keep.
We need to remove the EEO paragraph and the accommodation request, AI, etc.
Also remove "This posting is a new position within our organization." maybe not substantive? It's minor; could drop.
Now construct HTML.
We'll have sections:
About the role
Who are we? Equinix is the world’s digital infrastructure company®, shortening the path to connectivity to enable the innovations that enrich our work, life and planet. A place where bold ideas are welcomed, human connection is valued, and everyone has the opportunity to shape their future. A career at Equinix means being at the center of shaping what comes next and amplifying customer value through innovation and impact. You’ll work across teams, influence key decisions, and help shape the path forward. You’ll find belonging, purpose, and a team that welcomes you—because when you feel valued, you’re empowered to do your best work.
The VP, GTM Strategic Programs & Operations is the single accountable business owner for the Lead-to-Cash (LTC) program and the primary CRO-side counterpart to the CDIO program lead. While the CDIO organization owns technology delivery, this role ensures the business is prepared at every stage: that scope decisions reflect CRO priorities, that design sign-offs are grounded in requirements, that testing is thorough, and that go-live decisions are made with full visibility into business risk. The role reports to the SVP of GTM Ops within the CRO organization and owns the CRO-side program budget, including headcount and vendor resources.
But note we duplicated "Who are we?" maybe we should keep as part of About the role. That's fine. Next:Responsibilities
- Lead a dedicated team: Technical Program Manager, Business Architecture & Scope Lead, Business Readiness Lead, Solution Design Lead, and Continuity/Change Lead
- Indirectly manage Business Context Experts allocated 25-30% of their time to the program, representing Marketing & Lead Generation, Pipe & Forecast Management, Renewal Management, Quote Management, Order Management, Service Delivery (CSM/SM), Customer Support, Account & Territory Management, and Sales Compensation
- Own the CRO-side program budget, covering headcount, dedicated resources, and vendor allocations
- Serve as the single CRO counterpart and C
- for that list.
We must remove boilerplate: EEO, accommodation, AI, etc. Also remove duplicated lines. Also remove "Our pay ranges reflect..." etc? That is substantive? It's about pay range determination; we should keep as it's part of Pay section. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we keep that explanation.
We also need to remove "Equinix Benefits As an employee, you become important to Equinix’s success..." etc. That's substantive; keep.
We need to remove the EEO paragraph and the accommodation request, AI, etc.
Also remove "This posting is a new position within our organization." maybe not substantive? It's minor; could drop.
Now construct HTML.
We'll have sections:
- .
Skills & Attributes: list:
- Ability to operate in high-ambiguity environments where scope, timelines, and resource constraints shift
- Executive presence and credibility with senior stakeholders, able to frame trade-offs crisply and drive go/no-go decisions without escalation becoming the default
- Structured decision-making under pressure, with the judgment to distinguish a genuine business risk from a delivery inconvenience
- Fluency in translating between business requirements and technical solution design, conversant enough with system architecture to challenge design decisions, without owning delivery
- Facilitation and conflict resolution skills across competing functional priorities, driving to a decision rather than a compromise that satisfies no one
Pay: targeted pay range details: three locations with same range: United States - Redwood City Office GHQ : 248,000 - 372,000 USD / Annual; United States - Dallas Infomart Office DAI : 248,000 - 372,000 USD / Annual; United States - Seattle Office SEO : 248,000 - 372,000 USD / Annual. Also note about pay range etc. We need to preserve all substantive information. So we should include that paragraph.
Benefits: Equinix Benefits description includes several paragraphs. We need to preserve all substantive information. Could be a
- for any list of duties/requirements/benefits. If we don't have explicit list, we could still use
- . The instruction says use
- for any list of duties/requirements/benefits. The responsibilities are not explicitly bullet list but we can still treat each major duty as a list item. However we need to preserve all substantive information; we could keep them as paragraphs under Responsibilities heading, but then we wouldn't be using