Jobs · Engineering · Ohio

Senior Solutions Architect (Pre-Sales)

MongoDB · Cincinnati, OH · 1 mo ago
Engineering$104k–$204k/yrFull-time
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 that have real specific content. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove req ID? It says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can drop the Req ID line. We need to preserve all substantive information. We need to include Pay section only if posting actually states them. It does: "MongoDB’s base salary range for this role in the U.S. is: $104,000—$204,000 USD". Also earlier: "MongoDB’s base salary range for this role is posted below." So we can include Pay section with that range. Benefits: The posting mentions benefits: "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 earlier: "From employee affinity groups, to fertility assistance and a generous parental leave policy, we value our employees’ wellbeing..." So we can include Benefits section. Schedule: Not explicitly mentioned. There's hybrid working model: "We are looking to speak to candidates who are based in Minneapolis for our hybrid working model." That's schedule? It's location/hybrid. Not explicit schedule like full-time/part-time. Probably not include Schedule. Qualifications vs Requirements vs Skills: We need to decide sections. The posting includes "As an ideal candidate, you will have" list of experience requirements. Also "You may also have" list of nice-to-have. Also "What you will learn" sections. Also "What you do at MongoDB" responsibilities. We need to map to headings: About the role (maybe overview), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. The page already shows it. We need to include only sections with real content. Let's extract: About the role: The first paragraph: "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." That's about the role. Responsibilities: The "What you do at MongoDB In this role, you will work on complex opportunities..." bullet list (though not bullet but sentences). We can convert to

  • . Requirements: The "As an ideal candidate, you will have" 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. Qualifications: Could be the "You may also have" list: 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. Skills: Could be overlapping but maybe we can treat "What you will learn" as Skills? Actually "What you will learn" includes MongoDB Product Suite Mastery, Market-Relevant Technologies, Modern Architecture Design, Sales Techniques and Soft Skills, Industry Insights. That's more like learning outcomes/training. Could be Skills section. But we need to avoid thin sections. Perhaps combine some. We have to follow instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (including qualifications?), Benefits, Pay. Maybe we can incorporate Qualifications and Skills into Requirements or separate if substantive. Let's see content volume: Requirements list is fairly detailed (8 items). Qualifications list also detailed (7 items). Skills list (What you will learn) also detailed. We could have three sections: Requirements (mandatory), Preferred Qualifications (nice-to-have), Skills & Development (what you will learn). That seems reasonable. But headings must be from the list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use Requirements, Qualifications, Skills. Thus we will have:

    About the role

    with paragraph.

    Responsibilities

    with
    • items.

      Requirements

      with
      • items (mandatory).

        Qualifications

        with
        • items (nice-to-have).

          Skills

          with
          • items (what you will learn).

            Benefits

            with
            • items (benefits list).

              Pay

              with

              salary range. We should not include Schedule. We need to preserve all substantive information. Ensure we don't lose any details. Let's extract each piece precisely. About the role paragraph: We'll combine the sentences into a paragraph. Responsibilities: The bullet points from "What you do at MongoDB 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 list: - 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'll turn each into

            • . Requirements: The list after "As an ideal candidate, you will have". Let's extract each bullet: - 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 We'll put each as
            • . Qualifications: "You may also have" list: - 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 Skills: "What you will learn" sections: There are headings within that paragraph: MongoDB Product Suite Mastery, Market-Relevant Technologies, Modern Architecture Design, Sales Techniques and Soft Skills, Industry Insights. Under each there are bullet-like sentences. We need to capture all specifics. Let's extract: MongoDB Product Suite Mastery: - Core Database Server: Master the fundamentals and advanced features of MongoDB's core database - Atlas and Advanced Services: Gain expertise in Atlas (fully managed cloud database service), Atlas Stream Processing, Atlas Data Lake, Atlas Full-Text Search, Atlas Vector Search, and Charts - Relational Migrator: Learn to migrate from relational databases seamlessly Market-Relevant Technologies: - Hyperscaler Ecosystem: Gain expertise in designing complex systems utilizing cloud services on hyperscaler platforms - Complementary Technologies: Enhance your skills with partner and complementary technologies such as Apache Kafka and Kubernetes Modern Architecture Design: - Design Patterns and Methodologies: Embrace best practices in microservices, DevOps, cloud, and security - Cutting Edge RAG and AI Architectures: Help customers on their generative AI journeys and working with industry leading partners in the space Sales Techniques and Soft Skills: - Effective Communication: Master presentations, demonstrations, and whiteboarding - Client Interaction: Develop strategies for discovery and objection handling Industry Insights: - Diverse Market Verticals: Gain exposure to a broad spectrum of interesting use cases across various industries We'll turn each bullet into
            • under Skills. Benefits: The 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 earlier: "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." We'll combine. We'll create
              • items: 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

Similar jobs