Senior Enterprise Account Executive, Growth

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes description of role, responsibilities, requirements, qualifications, skills, benefits, pay (salary range), schedule (hybrid working model, in-office presence 3+ days per week). Also location requirement. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, accommodations, etc. Also remove application instructions, navigation, cookie, legal. Also remove duplicated lines. We need to preserve all substantive info. Let's extract: About the role: The first paragraph(s) describing role: "MongoDB is looking for a highly accomplished, results-oriented individual with exceptional energy, intellectual curiosity, and entrepreneurial initiative to significantly expand our presence within the startup ecosystem in the San Francisco Bay Area. This AI Natives EAE role is critical for proactively identifying and cultivating strategic, net-new relationships with high-potential startup founders and executive decision-makers, while concurrently forging deep, impactful partnerships across the AI landscape, and expertly guiding complex sales cycles within an assigned territory. This role is deeply connected to MongoDB’s vision to become the Data Platform for AI, and you’ll be at the forefront of that mission. You will be focused on winning the fastest-growing organizations in the world’s most concentrated AI hub. We're looking to speak with candidate based in the San Francisco Bay Area for our hybrid working model." That's about the role. Responsibilities: bullet list under "What you will be doing": Serve as a pivotal leader within MongoDB GTM, working cross-functionally with Marketing and Product Leadership directly influencing and driving MongoDB’s market penetration within the VC and startup ecosystem; Architect and execute highly sophisticated, data-driven go-to-market strategies for the assigned AI Native territory, identifying key market segments and opportunities for exponential growth; Drive executive-level engagement and influence within the startup community, with a particular focus on C-suite technical decision makers, visionary founders, and strategic investors; Cultivate and maintain profound, long-term relationships with founders, VCs, key developers, and technical architects to (1) secure net-new logos within the startup ecosystem, (2) identify, establish, and mature strategic product and go-to-market partnerships, and (3) consistently exceed top-line revenue targets; Develop and evangelize a comprehensive, expert-level understanding of MongoDB products, the competitive landscape, and partner technologies, positioning MongoDB as a thought leader. Requirements: maybe "Who You Are" section: 8+ years of consistent quota-carrying field experience in highly competitive and rapidly evolving markets, with a proven track record of selling technically complex enterprise solutions at scale; Exceptional intellectual curiosity and a demonstrated commitment to continuous learning and professional development; A profound history of identifying, building, and nurturing executive-level champions within your customer-base, and successfully navigating highly complex, multi-stakeholder sales processes; Mastery in translating intricate technical concepts and nuanced technical challenges into compelling, quantifiable business value and strategic outcomes for customers; Possess an inherent drive, intense competitiveness, and an insatiable desire to achieve extraordinary success and exceed expectations; Must reside within the assigned territory and be willing to maintain a significant in-office presence (3+ days per week) to foster collaboration and team cohesion. Qualifications: maybe overlapping with requirements. Could treat "Who You Are" as qualifications. But we have separate sections: Requirements, Qualifications, Skills. We need to decide what goes where. The posting doesn't explicitly separate them; we can map: Requirements = experience, etc. Qualifications = maybe education? Not present. Skills = maybe technical understanding, ability to translate technical concepts, etc. But we should not invent. Better to combine: Use Requirements for the bullet list under "Who You Are". Use Skills for the bullet list under "Things we love" maybe? Actually "Things we love" includes: A passionate commitment to continuous learning and a strong aspiration to lead and define your career trajectory; A proven ability to contribute significantly to building something truly special and scaling a high-growth business unit; Deep familiarity with advanced software development concepts, emerging technologies, and a nuanced understanding of diverse developer and technical personas; Extensive experience and a strong preference for selling to highly technical buyers and engineering leadership. That seems like skills/qualities. Benefits: paragraph after "MongoDB’s base salary range for this role is posted below." includes: 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 that base salary range and benefits only applicable to U.S.-based candidates. Pay: base salary range: $160,000—$160,000 USD (so fixed). That's specific. Schedule: hybrid working model, candidate based in San Francisco Bay Area, significant in-office presence (3+ days per week). Also location requirement. We should not include boilerplate like EEO, accommodations, etc. We need to output only HTML fragment, using

for section headings,

• for lists,

  for prose. We must not repeat job title as heading. No markdown. Let's craft sections:

  About the role

  MongoDB is looking for a highly accomplished, results-oriented individual with exceptional energy, intellectual curiosity, and entrepreneurial initiative to significantly expand our presence within the startup ecosystem in the San Francisco Bay Area. This AI Natives EAE role is critical for proactively identifying and cultivating strategic, net-new relationships with high-potential startup founders and executive decision-makers, while concurrently forging deep, impactful partnerships across the AI landscape, and expertly guiding complex sales cycles within an assigned territory. This role is deeply connected to MongoDB’s vision to become the Data Platform for AI, and you’ll be at the forefront of that mission. You will be focused on winning the fastest-growing organizations in the world’s most concentrated AI hub. We're looking to speak with candidate based in the San Francisco Bay Area for our hybrid working model.

  Responsibilities

  • Serve as a pivotal leader within MongoDB GTM, working cross-functionally with Marketing and Product Leadership directly influencing and driving MongoDB’s market penetration within the VC and startup ecosystem.
  • Architect and execute highly sophisticated, data-driven go-to-market strategies for the assigned AI Native territory, identifying key market segments and opportunities for exponential growth.
  • Drive executive-level engagement and influence within the startup community, with a particular focus on C-suite technical decision makers, visionary founders, and strategic investors.
  • Cultivate and maintain profound, long-term relationships with founders, VCs, key developers, and technical architects to (1) secure net-new logos within the startup ecosystem, (2) identify, establish, and mature strategic product and go-to-market partnerships, and (3) consistently exceed top-line revenue targets.
  • Develop and evangelize a comprehensive, expert-level understanding of MongoDB products, the competitive landscape, and partner technologies, positioning MongoDB as a thought leader.

  Requirements

  • 8+ years of consistent quota-carrying field experience in highly competitive and rapidly evolving markets, with a proven track record of selling technically complex enterprise solutions at scale.
  • Exceptional intellectual curiosity and a demonstrated commitment to continuous learning and professional development.
  • A profound history of identifying, building, and nurturing executive-level champions within your customer-base, and successfully navigating highly complex, multi-stakeholder sales processes.
  • Mastery in translating intricate technical concepts and nuanced technical challenges into compelling, quantifiable business value and strategic outcomes for customers.
  • Possess an inherent drive, intense competitiveness, and an insatiable desire to achieve extraordinary success and exceed expectations.
  • Must reside within the assigned territory and be willing to maintain a significant in-office presence (3+ days per week) to foster collaboration and team cohesion.

  Skills

  • A passionate commitment to continuous learning and a strong aspiration to lead and define your career trajectory.
  • A proven ability to contribute significantly to building something truly special and scaling a high-growth business unit.
  • Deep familiarity with advanced software development concepts, emerging technologies, and a nuanced understanding of diverse developer and technical personas.
  • Extensive experience and a strong preference for selling to highly technical buyers and engineering leadership.

  Benefits

  • 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
  • Health benefits offerings

  Pay

  MongoDB’s base salary range for this role in the U.S. is: $160,000—$160,000 USD.

  Schedule

  Hybrid working model with a requirement to be based in the San Francisco Bay Area and maintain a significant in-office presence (3+ days per week).

  Check for any repeated content: We included location in About the role and Schedule; that's okay. We must not include any boilerplate like "Learn more about what it’s like to work at MongoDB, and help us make an impact on the world!" That's promotional but maybe considered substantive? It's more marketing; but it's not a requirement. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Learn more..." is not boilerplate but could be considered fluff. However it's part of the "About MongoDB" section. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "Learn more..." is not substantive for the job; it's more generic. Might be considered boilerplate? It's not EEO or legal. It's a call to learn more about culture. Could be considered filler but not explicitly prohibited. Safer to keep? The instruction: "Prefer a few substantive sections over many thin ones." The "About MongoDB" paragraph includes details about MongoDB's platform, customers, etc. That is substantive about the company. We could include that as a separate section maybe "About MongoDB". But we only have predefined headings list; we could add a section "About MongoDB" if we want, but the instruction says use headings for those specific headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't forbid other headings, but says use

  for section headings (e.g. About the role, Responsibilities...). It implies we should use those headings for those sections; we could add other headings but not required. Safer to stick to those. Thus we omitted the "About MongoDB" paragraph. Is that substantive? It describes MongoDB's platform, customers, etc. Might be considered relevant but not required for the role. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we omit that paragraph, we are losing substantive info about the company. However the instruction also says "Prefer a few substantive sections over many thin ones." Could be okay to omit if it's not directly about the role. But it's still substantive about the employer. The instruction didn't say we must include everything; it says preserve ALL substantive information. That suggests we should keep it. But we don't have a heading for it; we could include it under About the role as additional paragraph. That would be okay: we can add more prose to About the role. Let's incorporate the MongoDB description into About the role paragraph. Thus