Senior Engagement Manager

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. First paragraph: description of role. Could be "About the role". Then "What you’ll do at MongoDB" is responsibilities. Then "An ideal candidate will have" is requirements/qualifications/skills. Then "About MongoDB" maybe not needed? It's company description; maybe not needed as a section? Could be omitted if not requested. The instructions: include a section ONLY when posting has real, specific content for it. The sections we can use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (first paragraph). Responsibilities (the bullet list under "What you’ll do at MongoDB"). Requirements/Qualifications/Skills: The "An ideal candidate will have" list includes experience, degree, years, etc. Could split into Requirements (experience, degree, years) and Skills (knowledge, abilities). But we can combine if needed. However we need to follow instruction: prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements (which includes qualifications and skills), Benefits, Pay. Schedule not mentioned, so omit. Benefits: The paragraph after salary range lists benefits: equity, participation in 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 these are for US-based candidates. So we can include Benefits section. Pay: The salary range: $109,000—$215,000 USD. Also note that compensation unique etc. We can include Pay section with that range. Schedule: Not mentioned, so omit. We must not include boilerplate like EEO, accommodations, etc. Remove those lines. Also remove "Req ID: 3273537296". Remove "To learn more about the Services Seller Engagement Management role, check out these insightful blog posts: Meet a Current Engagement Manager and How Engagement Managers Help Customers Succeed." That's maybe not substantive? It's a link suggestion; could be considered boilerplate? Probably remove as it's not core duty. Also remove "This role can be based in New York City or Atlanta for our hybrid working model." That's location info; could be considered part of About the role? Might be relevant but not a section heading. Could be included in About the role paragraph? It's location/hybrid. Might keep as part of About the role? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep location/hybrid info. Where to put? Could be in About the role paragraph. Also "MongoDB’s base salary range for this role is posted below." That's intro to Pay. We need to output only HTML fragment, no markdown fences. Let's craft:

About the role

MongoDB Engagement Managers are quota-carrying Professional Services sales leaders responsible for discovering customer business initiatives, developing services strategies, scoping and negotiating engagements, and driving Professional Services bookings that accelerate customer outcomes and MongoDB adoption. As a Services Seller Engagement Manager, you will be a key leader within the PS team, work cross-functionally with the Sales, Professional Services, and Customer Success organizations to shape how we will help our customers achieve their MongoDB vision. This role can be based in New York City or Atlanta for our hybrid working model.

Responsibilities

• Understand customer application portfolios and identify opportunities to design delivery programs related to modernization, cloud adoption, AI enablement, and data platform transformation
• Lead discovery, solutioning, estimation, and commercial negotiations to convert customer business initiatives into Professional Services bookings
• Collaborate as part of a larger team alongside cloud partners, strategic partners, and your MongoDB account teams to develop and execute customer success and Professional Services growth strategies
• Maintain a strong sense of ownership, driving all deals or technical scopings from inception to closure
• Manage the Professional Services pipeline for bookings and revenue forecasts for your region
• Expertly articulate the business value of professional services, speaking knowledgeably and credibly about service delivery issues, challenges, strategies, approaches, and risk mitigation
• Work with our practice team to propagate internal skills and experience through the development of repeatable assets (estimates, proposals, SOWs, templates, tools, case studies etc.)
• Work with the delivery team to transition any agreed upon project scope and customer expectations to ensure successful project delivery
• Proactively seek opportunities to support and mentor other team members and share best practices
• Have situational awareness and react appropriately in group settings

Requirements

• Experience in Professional Services sales, consulting sales, solution consulting, or quota-carrying technology roles
• A BS degree in Computer Science, Mathematics, Engineering or equivalent professional experience
• A minimum of 5 years experience in the sale of Professional Services and/or technology solutions at an enterprise software company
• Experience as an architect, consultant, project manager, or Professional Services manager
• Experience internally positioning and selling professional services
• General knowledge of databases (RDBMS, SQL, NoSQL)
• Experience and knowledge of the software development lifecycle and associated development methodologies (e.g. Agile, Waterfall)
• Knowledge of software architecture including both cloud and on-premise technologies e.g. AWS, GCP, Kubernetes, Open Shift
• The ability to collaborate as a part of a larger account team to build and execute complex account strategies and sales plays
• An ability to scope and estimate projects
• Strong presentation skills: Showing the value, capabilities, and differentiators of complex service solutions using methodologies and service offerings
• Willingness to travel for key engagements and team offsites

We could also have a Skills section but we already included many skills in Requirements. To avoid thin sections, we can keep just Requirements.

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: $109,000—$215,000 USD

We should not include Schedule. Check for any leftover boilerplate: removed EEO, accommodations, etc. Also removed "Learn more about what it’s like to work at MongoDB, and help us make an impact on the world!" etc. Also removed "MongoDB is committed to providing any necessary accommodations..." etc. Also removed "Req ID". Also removed "To learn more about the Services Seller Engagement Management role, check out these insightful blog posts..." etc. Make sure we didn't miss any substantive info: The description about MongoDB's platform etc. That's company description; not required but could be considered substantive. However the instruction: include a section only when posting has real, specific content for it. The company description is not under any of the allowed headings; we could put it under About the role? But About the role already has role description. Could we add a paragraph about MongoDB under About the role? It might be okay but could be considered not about the role. However the instruction says preserve ALL substantive information; do not invent or summarize away detail. If we omit the company description, we are losing substantive info. But we could incorporate it into About the role as a brief description of the company. However the About the role section is supposed to be about the role, not the company. But we could add a separate section like "About MongoDB" but that's not in allowed headings. The allowed headings list does not include "About MongoDB". So we cannot create a heading not in list. We could incorporate that info into the About the role paragraph as a sentence, but that might be mixing. However the instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not add other headings. We could put company description in a

without a heading? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't forbid stray paragraphs without heading. But earlier: "Use

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." So we can have prose paragraphs not under a heading? It says use

  for prose. So we could have a

  about MongoDB without a heading. However the instruction also: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid having prose without heading. So we could add a

  about MongoDB after the About the role heading or before. But to keep structure, maybe we add a

  under About the role? Actually About the role heading expects prose about the role. We could add two paragraphs under About the role: first about role, second about company. That would preserve info. Thus:

  About the role

  MongoDB Engagement Managers are quota-carrying Professional Services sales leaders responsible for discovering customer business initiatives, developing services strategies, scoping and negotiating engagements, and driving Professional Services bookings that accelerate customer outcomes and MongoDB adoption. As a Services Seller Engagement Manager, you will be a key leader within the PS team, work cross-functionally with the Sales, Professional Services, and Customer Success organizations to shape how we will help our customers achieve their MongoDB vision. This role can be based in New York City or Atlanta for our hybrid working model.

  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 AI-native startups and approximately 75% of the Fortune 100, relying on MongoDB for their most important applications, we’re powering the next era of software.

  That preserves company description. Now check if any other substantive info: "Our compass at MongoDB is our Leadership Commitment, guiding how and why we make decisions, show up