Senior Solutions Architect (Pre-Sales)

for prose. We must not include boilerplate like EEO, accommodations, etc. Also remove duplicated lines. Also remove application instructions. Also remove "Req ID: 426379". Also remove "MongoDB’s base salary range for this role is posted below." etc but we need to keep the salary range. We need to keep the 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 that it's only applicable to U.S.-based candidates. Keep that. We need to keep the salary range: "$104,000—$204,000 USD". Also note that compensation at time of offer unique etc. Keep that as prose maybe. We need to keep location: Minneapolis hybrid working model. We need to keep travel up to 25%. We need to keep the "What you will learn" sections? That seems like learning opportunities, could be part of Responsibilities? Might be considered as "What you will learn" maybe under Responsibilities or a separate section like "Learning & Development". Not in allowed headings. Could be placed under Responsibilities as part of role? But it's more about training. Could be placed under "Personal Training and Development" which is already a responsibility bullet. So we can incorporate that bullet under Responsibilities. The "What you will learn" section includes sub-bullets: MongoDB Product Suite Mastery, Market-Relevant Technologies, Modern Architecture Design, Sales Techniques and Soft Skills, Industry Insights. Those are learning objectives. Could be considered as part of Responsibilities or maybe a separate section like "What you will learn". Not in allowed headings; but we could treat as part of Responsibilities (since it's about what you'll do/learn). However the instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; we could also use other headings if needed? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections; we could still add other headings but maybe not needed. Safer to stick to those. Thus we need to map content to those headings. Let's extract: About the role: Intro paragraphs up to location. Responsibilities: The "What you do at MongoDB" bullet list (including Design and Architect, Customer Advising..., Sales Partnership..., Demand Generation..., Customer Success..., Innovation..., Personal Training...). Also maybe the "What you will learn" could be considered responsibilities? But we can keep as part of Responsibilities? Might be better to treat as part of Responsibilities because they describe what you'll do/learn. However the bullet list already includes "Personal Training and Development". The "What you will learn" is more about training topics. Could be placed under Responsibilities as a sub-list? But we need to preserve all substantive info; we could create a separate section "What you will learn" but not allowed heading. Could embed as a

under Responsibilities with a note? Might be okay to add a

describing learning opportunities. But we need to not invent headings. Better: Keep Responsibilities as the bullet list from "What you do at MongoDB". Then we can add a separate section "Skills" for skills like presentation, communication, etc. And "Qualifications" for preferred qualifications (the "You may also have" list). "Requirements" for mandatory requirements (the "As an ideal candidate, you will have" list). Benefits and Pay as sections. Now we need to ensure we don't repeat content. Let's list mandatory requirements: - Ideally 8 to 11 years of related experience in a customer facing role, with 5 to 7 years of experience in pre-sales with enterprise software - Minimum of 3 years experience with modern scripting languages (e.g. Python, Node.js, SQL) and/or popular programming languages (e.g. C/C++, Java, C#) in a professional capacity - Experience designing with scalable and highly available distributed systems in the cloud and on-prem - Demonstrated ability to work with customers to review complex architecture of existing applications, providing guidance on how to improve by leveraging technology - Excellent presentation, communication, and interpersonal skills, with the ability to convey complex technical and business concepts in a clear and compelling manner to technology and business leadership - Ability to strategize with sales teams and provide recommendations on how to drive a multi-threaded account strategy, aligning other MongoDB and ecosystem resources to move towards a mutually beneficial account plan - The ability to travel up to 25% - A Bachelor’s degree or equivalent work experience Also location: Minneapolis hybrid working model (maybe part of About the role). Now preferred qualifications (You may also have): - Experience selling databases and/or deploying applications with any of the major cloud providers - Experience with database programming and data models - Experience in data engineering or AI/ML projects - Experience in transforming legacy systems and platforms into modern, scalable, and efficient technology stacks - Understanding of popular sales methodologies/ frameworks such as MEDDPICC/ Command of the Message - A MongoDB Certification - A Cloud Provider Certification Now skills: Could be extracted from the responsibilities bullet list: Design and Architect, Customer Advising..., Sales Partnership..., Demand Generation..., Customer Success..., Innovation..., Personal Training... But those are more responsibilities. However we could still have a Skills section for soft skills like presentation, communication, interpersonal, strategizing, etc. But those are already in requirements. To avoid duplication, maybe we don't need a separate Skills section if content overlaps. But we need to include a Skills section only if there is real specific content not already covered. The posting does have a list of skills: "Excellent presentation, communication, and interpersonal skills..." etc. That's already in requirements. Could still be placed under Skills but would duplicate. Better to not create Skills section if it would duplicate. However the instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills if its content is covered elsewhere. But we need to ensure we don't lose any substantive info. If we omit Skills, we still have those skills in Requirements (they are listed). So it's fine. Now Benefits: The paragraph about benefits. Pay: Salary range and note about compensation uniqueness. Schedule: Not present; omit. Now About the role: Let's craft a paragraph(s) that includes the introductory description and location/hybrid model. We need to preserve all substantive info: The description about Pre-Sales Solution Architects, guiding customers, team composition, working with sales executives, trusted advisor, location Minneapolis hybrid, etc. We'll produce:

About the role

We are looking for passionate technologists to join our Pre‑Sales organization to ensure that our growth is grounded and guided by strong technical alignment with our platform and the needs of our customers. MongoDB Pre‑Sales Solution Architects are responsible for guiding our customers and users to design and build reliable, scalable systems using our data platform. Our team is made up of seasoned technical sales professionals, software architects, entrepreneurs, and developers who take direct responsibility for customer success, including the design of their software, deployment, and operations. You'll work closely with our sales executives, helping customers solve business problems by leveraging our solutions, playing a key role in winning deals and driving the business forward. You'll be a trusted advisor to a wide range of users from startups to the world's largest enterprise IT organizations. We are looking to speak to candidates who are based in Minneapolis for our hybrid working model.

Now Responsibilities: Use
• for each bullet. We need to capture each bullet from "What you do at MongoDB". Let's list them exactly: - Design and Architect: Design scalable and performant applications, systems and infrastructure for large software projects leveraging MongoDB - Customer Advising and Value Articulation: Guide customers on architecture patterns and optimisation strategies for MongoDB, while clearly communicating its business value to the relevant stakeholders - Sales Partnership: Collaborate with the sales team to drive account success through account planning, opportunity prioritization/qualification and pipeline generation strategy, while taking ownership of the technical aspects (including but not limited to technical discovery, demos, proof of value, presentations, sizing and documentation) - Demand Generation: Proactively generate demand within the sales territory through self-driven technical initiatives, participation in events such as industry trade shows and account-based marketing events - Customer Success: Foster strong customer relationships, build champions and ensure customer success and satisfaction - Innovation and Improvement: Continuously seek opportunities to innovate and improve MongoDB solutions and processes (e.g. by relaying field feedback to the product team), as well as proactively mentor other Solutions Consulting team members - Personal Training and Development: Engage in ongoing training and professional development to stay abreast of MongoDB product suite as well as industry trends We should keep the exact phrasing. Now Requirements: Use
  • for each mandatory requirement. List: - Ideally 8 to 11 years of related experience in a customer facing role, with 5 to 7 years of experience in pre-sales with enterprise software - Minimum of 3 years experience with modern scripting languages (e.g. Python, Node.js, SQL) and/or popular programming languages (e.g. C/C++, Java, C