Head of Executive Operations - Office of CEO
MongoDB · San Francisco, CA · 1 mo ago
Management$162k–$318k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "The Role" description, then "What You’ll Do", "What You’ll Bring", "About MongoDB", then compensation. We need to use for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real specific content. We have content for responsibilities (What You’ll Do), requirements/qualifications (What You’ll Bring), maybe About MongoDB as company overview (could be "About the role"? Actually "About the role" is the initial paragraph describing role; we can put that under a heading "About the role". Then responsibilities under "Responsibilities". Then qualifications under "Requirements" or "Qualifications". We have both experience and skills; we could combine into "Requirements". Benefits: they list benefits paragraph; we can include Benefits section. Pay: they give salary range; we can include Pay section. Schedule: not mentioned (travel up to 50% but not schedule). So we omit Schedule.
We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, accommodations, etc. Also remove "Learn more about what it’s like to work at MongoDB, and help us make an impact on the world!" maybe considered boilerplate? It's promotional but still substantive? Might be considered fluff but it's about culture; we could keep as part of About MongoDB? But we might drop as it's generic. Safer to keep only substantive info: description of MongoDB's platform, customers, etc. The equal opportunity line etc should be removed.
We need to preserve all substantive information; not invent or summarize away detail. So we need to keep the bullet points? They are in prose sentences; we can convert to
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real specific content. We have content for responsibilities (What You’ll Do), requirements/qualifications (What You’ll Bring), maybe About MongoDB as company overview (could be "About the role"? Actually "About the role" is the initial paragraph describing role; we can put that under a heading "About the role". Then responsibilities under "Responsibilities". Then qualifications under "Requirements" or "Qualifications". We have both experience and skills; we could combine into "Requirements". Benefits: they list benefits paragraph; we can include Benefits section. Pay: they give salary range; we can include Pay section. Schedule: not mentioned (travel up to 50% but not schedule). So we omit Schedule.
We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, accommodations, etc. Also remove "Learn more about what it’s like to work at MongoDB, and help us make an impact on the world!" maybe considered boilerplate? It's promotional but still substantive? Might be considered fluff but it's about culture; we could keep as part of About MongoDB? But we might drop as it's generic. Safer to keep only substantive info: description of MongoDB's platform, customers, etc. The equal opportunity line etc should be removed.
We need to preserve all substantive information; not invent or summarize away detail. So we need to keep the bullet points? They are in prose sentences; we can convert to - for list of duties/requirements/benefits. The posting uses sentences separated by line breaks; we can treat each as list item.
We need to output only HTML fragment, no markdown fences.
Let's extract sections:
About the role: The first paragraph: "We are seeking an exceptional Head of Executive Operations reporting to the CEO to serve as a high-impact force multiplier, strategic thought partner, and execution engine for our Chief Executive Officer. The core mandate of this role is to create significant operating leverage for the CEO. Positioned at the center of the enterprise, you will elevate the pace and impact of executive decision-making, streamline business operations, lead high-stakes executive communications, and align senior leaders across Product, Engineering, Go-To-Market (GTM), Finance, and Marketing to drive our next phase of company growth. This position holds enterprise-wide visibility. You will translate global strategy into operational execution, own the narrative for the CEO’s highest-stakes market moments, and step in to lead cross-functional transformation initiatives that shape the future of the company. This role can be based out of our San Francisco, Palo Alto, or New York City offices."
That's substantive.
Responsibilities: "What You’ll Do" list items:
- Create leverage for the CEO by designing and running the enterprise operating rhythm, including weekly leadership team meetings, Monthly & Quarterly Business Reviews, leadership offsites, and Board of Director meetings
- Produce the first draft of the quarterly earnings script and supporting market communications, taking primary ownership of setting the direction for a resonant public market story
- Own the narrative and content for the CEO’s keynotes and participation across marquee events, including our annual Investor Day, tier-1 regional flagship customer conferences (e.g., .locals), internal leadership summits, and company All Hands
- Synthesize complex business issues, financial models, and operational data into clear options, trade-offs, and actionable recommendations to accelerate CEO and leadership team decision velocity
- Act as a connective, cross-functional partner across functions (e.g., Product & Technology, Go-to-Market, G&A.) to break down organizational silos, resolve friction, and track strategic commitments
- Serve as a trusted proxy and delegate for the CEO in key strategic forums and working groups, consistently raising the bar for execution standards and operational rigor across the company
- Lead a team of Customer Advocates who serve as trusted partners to the CEO on all high-priority customer engagements, ensuring executive relationships are handled with the right level of preparation, follow-through, and strategic intent — while coordinating cross-functionally to drive resolution on escalations, commitments, and account-level priorities
- Lead high-priority special projects directly for the CEO, rapidly diagnosing and resolving emerging operational bottlenecks, market opportunities, or organizational realignments
We'll put each as
- .
Requirements/Qualifications: "What You’ll Bring" list:
- 10+ years of total professional experience demonstrating rapid career progression and high-impact delivery in fast-paced software environments
- Hybrid Skillset:
- Management Consulting: 3+ years at a premier management consulting firm (e.g., McKinsey, Bain, BCG) with expertise in structured problem solving, executive storytelling, business transformation, and financial analysis
- High-Growth Enterprise software: 4+ years of operational leadership, strategy, or business operations experience within a high-growth, enterprise B2B software organization ($1B+ ARR scale strongly preferred)
- Direct experience advising or supporting C-suite executives, with demonstrated success driving executive velocity, strategic planning, and operational alignment
- Strong command of core software performance drivers, business metrics, product-led and enterprise sales motions, and cloud infrastructure ecosystems
- Exceptional written and oral communication skills; proven ability to turn complex strategy and data into compelling, board-ready presentations and communications
- Exceptional emotional intelligence, diplomatic skill, and low ego; Demonstrated ability to build trust quickly, challenge senior executives constructively, and drive alignment across matrixed organizations
- Ability to travel up to 50% of the time
We could split into sublists but okay.
Benefits: paragraph: "Other benefits for eligible employees may include: equity, participation in the employee stock purchase program, flexible paid time off, 20 weeks fully-paid gender-neutral parental leave, fertility and adoption assistance, 401(k) plan, mental health counseling, access to transgender-inclusive health insurance coverage, and health benefits offerings."
Also note: "MongoDB’s base salary range for this role is posted below." That's pay.
Pay: "MongoDB’s base salary range for this role in the U.S. is: $162,000—$318,000 USD"
Also note: "Compensation at the time of offer is unique to each candidate and based on a variety of factors such as skill set, experience, qualifications, and work location. Salary is one part of MongoDB’s total compensation and benefits package." That's also pay info but we can include as prose.
We should not include "Please note, the base salary range listed below and the benefits in this paragraph are only applicable to U.S.-based candidates." That's still relevant to pay/benefits; we can keep as note.
We must not include boilerplate like EEO, accommodations, etc. Also remove "Req ID: 426364". Also remove "MongoDB is committed to providing any necessary accommodations..." etc.
Also remove "Learn more about what it’s like to work at MongoDB, and help us make an impact on the world!" maybe keep as part of About MongoDB? It's fluff; better to drop.
We need to include About MongoDB section? The heading "About the role" already used; we could have "About MongoDB" as a section but not in prescribed headings list. The prescribed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About MongoDB". So we should not create a heading not in list. We could incorporate MongoDB description into "About the role" or maybe under "About the role" we already have role description; we could add a separate paragraph about company under same heading? But the instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we could also use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. It doesn't forbid other headings, but better to stick to those. So we can put company info under "About the role" or maybe under "Responsibilities"? Not ideal. Could create a section "About the role" that includes both role description and company overview. That's acceptable.
Thus final HTML:
About the role
We are seeking an exceptional Head of Executive Operations reporting to the CEO to serve as a high-impact force multiplier, strategic thought partner, and execution engine for our Chief Executive Officer. The core mandate of this role is to create significant operating leverage for the CEO. Positioned at the center of the enterprise, you will elevate the pace and impact of executive decision-making, streamline business operations, lead high-stakes executive communications, and align senior leaders across Product, Engineering, Go-To-Market (GTM), Finance, and Marketing to drive our next phase of company growth. This position holds enterprise-wide visibility. You will translate global strategy into operational execution, own the narrative for the CEO’s highest-stakes market moments, and step in to lead cross-functional transformation initiatives that shape the future of the company. This role can be based out of our San Francisco, Palo Alto, or New York City offices.
MongoDB is built for change, empowering our customers and our people to innovate at the speed of the market. We have redefined the data platform for the AI era, enabling builders to create, transform, and disrupt industries with software. MongoDB’s unified data platform, the most widely available, globally distributed data platform on the market, helps organizations modernize legacy workloads, embrace innovation, and unleash AI. Our cloud-native platform, MongoDB Atlas, is the only globally distributed, multi-cloud data platform and is available across AWS, Google Cloud, and Microsoft Azure. With offices worldwide and over 67,000 customers, including 75% of the Fortune 100 and AI-native startups, relying on MongoDB for their most important applications, we’re powering the next era of software.
Then Responsibilities:
Responsibilities
- Create leverage for the CEO by designing and running the enterprise operating rhythm, including weekly leadership team meetings, Monthly & Quarterly Business Reviews, leadership offsites, and Board of Director meetings
- Produce the first draft of the quarterly earnings script and supporting market communications, taking primary ownership of setting the direction for a resonant public market story
- Own the narrative and content for the CEO’s keynotes and participation across marquee events, including our annual Investor Day, tier-1 regional flagship customer conferences (e.g., .locals), internal leadership summits, and company All Hands
- Synthesize complex business issues, financial models, and operational data into clear options, trade-offs, and actionable recommendations to accelerate CEO and leadership team decision velocity
- Act as a connective, cross-functional partner across functions (e.g., Product & Technology, Go-to-Market, G&A.) to break down organizational silos, resolve friction, and track strategic commitments
- Serve as a trusted proxy and delegate for the CEO in key strategic forums and working groups, consistently raising the bar for execution standards and operational rigor across the company
- Lead a team of Customer Advocates who serve as trusted partners to the CEO on all high-priority customer engagements, ensuring executive relationships are handled with the right level of preparation, follow-through, and strategic intent — while coordinating cross-functionally to drive resolution on escalations, commitments, and account-level priorities
- Lead high-priority special projects directly for the CEO, rapidly diagnosing and resolving emerging operational bottlenecks, market opportunities,
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we could also use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. It doesn't forbid other headings, but better to stick to those. So we can put company info under "About the role" or maybe under "Responsibilities"? Not ideal. Could create a section "About the role" that includes both role description and company overview. That's acceptable.
Thus final HTML:
About the role
About the role
We are seeking an exceptional Head of Executive Operations reporting to the CEO to serve as a high-impact force multiplier, strategic thought partner, and execution engine for our Chief Executive Officer. The core mandate of this role is to create significant operating leverage for the CEO. Positioned at the center of the enterprise, you will elevate the pace and impact of executive decision-making, streamline business operations, lead high-stakes executive communications, and align senior leaders across Product, Engineering, Go-To-Market (GTM), Finance, and Marketing to drive our next phase of company growth. This position holds enterprise-wide visibility. You will translate global strategy into operational execution, own the narrative for the CEO’s highest-stakes market moments, and step in to lead cross-functional transformation initiatives that shape the future of the company. This role can be based out of our San Francisco, Palo Alto, or New York City offices.
MongoDB is built for change, empowering our customers and our people to innovate at the speed of the market. We have redefined the data platform for the AI era, enabling builders to create, transform, and disrupt industries with software. MongoDB’s unified data platform, the most widely available, globally distributed data platform on the market, helps organizations modernize legacy workloads, embrace innovation, and unleash AI. Our cloud-native platform, MongoDB Atlas, is the only globally distributed, multi-cloud data platform and is available across AWS, Google Cloud, and Microsoft Azure. With offices worldwide and over 67,000 customers, including 75% of the Fortune 100 and AI-native startups, relying on MongoDB for their most important applications, we’re powering the next era of software.
Then Responsibilities:Responsibilities
- Create leverage for the CEO by designing and running the enterprise operating rhythm, including weekly leadership team meetings, Monthly & Quarterly Business Reviews, leadership offsites, and Board of Director meetings
- Produce the first draft of the quarterly earnings script and supporting market communications, taking primary ownership of setting the direction for a resonant public market story
- Own the narrative and content for the CEO’s keynotes and participation across marquee events, including our annual Investor Day, tier-1 regional flagship customer conferences (e.g., .locals), internal leadership summits, and company All Hands
- Synthesize complex business issues, financial models, and operational data into clear options, trade-offs, and actionable recommendations to accelerate CEO and leadership team decision velocity
- Act as a connective, cross-functional partner across functions (e.g., Product & Technology, Go-to-Market, G&A.) to break down organizational silos, resolve friction, and track strategic commitments
- Serve as a trusted proxy and delegate for the CEO in key strategic forums and working groups, consistently raising the bar for execution standards and operational rigor across the company
- Lead a team of Customer Advocates who serve as trusted partners to the CEO on all high-priority customer engagements, ensuring executive relationships are handled with the right level of preparation, follow-through, and strategic intent — while coordinating cross-functionally to drive resolution on escalations, commitments, and account-level priorities
- Lead high-priority special projects directly for the CEO, rapidly diagnosing and resolving emerging operational bottlenecks, market opportunities,