Senior Solutions Architect (Pre-Sales)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must preserve all substantive info, no boilerplate. Remove cookie/navigation/legal/EEO etc. Also remove duplicated lines and application instructions. Also remove "Apply now" etc. Also remove "Please let MongoDB Australia know you found this job on Job Vista." etc. Also remove "MongoDB is committed to providing any necessary accommodations..." etc. Also remove "MongoDB, Inc. provides equal employment opportunities..." etc. We need to extract content: The posting includes: - About The Job: paragraph about looking for passionate technologists, Pre-Sales organization, responsibilities. - Required Skills & Abilities: bullet list of requirements. - Role: description of responsibilities (Design and Architect, Customer Advising and Value Articulation, Sales Partnership, Demand Generation, Customer Success, Innovation and Improvement, Personal Training and Development). - Then there is a section "MongoDB Product Suite Mastery" with subpoints: Core Database Server, Atlas and Advanced Services, Relational Migrator, Market-Relevant Technologies, etc. This seems like training/skills. - Then "Industry Insights" etc. - Then some company description about MongoDB. - Then "Qualifications Experience: 3 years experience" (but earlier they said 8-11 years etc. There's contradictory; but we must preserve all substantive info. The "Qualifications Experience: 3 years experience" appears near the end maybe a mistake. We'll include it as part of qualifications? Might be a duplicate. We'll include qualifications section with the bullet list of qualifications (maybe from Required Skills & Abilities). Also there is "Experience: 3 years experience" maybe a field. - Pay: "USD 104,000 - 204,000" present. - Schedule: Not explicitly given besides Full Time. Could infer schedule? Not given. So we should not create Schedule section unless posting actually states them. It doesn't state schedule beyond Full Time (which is job type). The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Pay is stated, so we include Pay. Schedule not stated explicitly (just Full Time). Should we include Schedule? Probably not, as they didn't give schedule details like hours. So omit Schedule. - Benefits: Not explicitly stated besides mention of fertility assistance, parental leave policy, employee affinity groups etc. That's in the later paragraph about culture. That could be considered benefits. The posting says: "From employee affinity groups, to fertility assistance and a generous parental leave policy, we value our employees’ wellbeing and want to support them along every step of their professional and personal journeys." That's benefits. So we can include Benefits section with those items. - Also there is "MongoDB Product Suite Mastery" etc which could be considered Skills or Requirements. We'll treat as Skills. We need to avoid repeating job title as heading. The job title is likely "Pre-Sales Solution Architect" (maybe). Not to repeat. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details as they appear, but we can format them into lists. We must not include boilerplate like "Apply now", "Please let MongoDB Australia know you found this job on Job Vista.", "MongoDB is committed to providing any necessary accommodations...", "MongoDB, Inc. provides equal employment opportunities...". Also remove duplicated lines. We need to decide sections: About the role (maybe About the role), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. But we must avoid thin sections. Let's see content: - About the role: The first paragraph after "About The Job": "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 custom..." (cut off). That's prose. - Responsibilities: The "Role" section with bullet-like items: Design and Architect, Customer Advising and Value Articulation, Sales Partnership, Demand Generation, Customer Success, Innovation and Improvement, Personal Training and Development. Each has sub-bullets. We can make a

  with each main responsibility as
  • and maybe nested
    for subpoints. - Requirements: The "Required Skills & Abilities" list: bullet points. We'll make
    . - Qualifications: Could be similar to Requirements? Might be overlapping. The posting also has "Qualifications Experience: 3 years experience". That seems like a qualification. But we already have experience in Required Skills & Abilities (8-11 years). There's inconsistency. We'll keep both as given. Perhaps we treat "Qualifications" as the short line "Experience: 3 years experience". But that seems too thin. Better to combine qualifications into Requirements? But instruction: Prefer a few substantive sections over many thin ones. So we could have Requirements covering both skill and experience. Qualifications maybe not needed if it's just a repeat. However we must preserve all substantive info; we can include the "Experience: 3 years experience" as a

    under Qualifications if we want to keep it. But that would be a thin section. Maybe we can incorporate it into Requirements as a note. But we must not lose info. We could add a

    under Requirements: "Qualifications: 3 years experience." But the Required Skills & Abilities already says 8-11 years experience. The contradictory 3 years may be a mistake but we must preserve it. We'll include it as a separate

    under Qualifications. - Skills: The "MongoDB Product Suite Mastery" etc could be considered Skills. We'll make a Skills section with subpoints. - Benefits: The paragraph about employee affinity groups, fertility assistance, parental leave policy, etc. We'll make a Benefits

    . - Pay: The salary range. We must not include sections like "About Company" etc unless they have substantive content? The company description about MongoDB is substantive but not a standard heading; we could treat as "About the company" but not in list of allowed headings? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't include About the company. So we should not create a heading for that; we could incorporate that prose into maybe a

    without heading? But instruction: Use

    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. those). Likely we should only use those headings. So we can omit the company description or put it as a

    without heading? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't say we cannot have other headings, but they gave examples. Safer to stick to those headings and omit other content? But we must preserve ALL substantive information. If we omit company description, we lose substantive info. However maybe that company description is considered boilerplate? It's not exactly boilerplate; it's about MongoDB. Could be considered "About the company" which is not in the list but maybe we can treat as

    without heading. The instruction didn't forbid

    without heading. It said 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 anywhere, not necessarily under a heading. So we can include the company description as a

      without a heading. Good. Similarly, the "MongoDB is built for change..." paragraph is also prose; we can include as

      . Thus we will have sections with headings for: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We need to ensure we don't create empty sections. Now let's extract content precisely. First, locate the "About The Job" section: "About The Job 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 custom..." It cuts off at "custom...". The rest maybe continues but we have what we have. We'll keep that as is. Next, "Required Skills & Abilities" 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#) 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 - 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 We'll keep each as

    • . Next, "Role" section: "Role In this role, you will work on complex opportunities where analysis of situations or data requires an in-depth evaluation of various factors. You will:" Then bullet points: - 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