Senior Software Engineer, SQL Engines

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content. Need to extract content from posting. Let's parse. The posting includes: - Intro paragraph about team and role: "The SQL Engines team is working to make MongoDB the first choice... This is an opportunity to make a significant impact..." That's about the role. - Then "This role can be based out of our Austin, New York City, Palo Alto, San Francisco office or remotely in the USA region." That's location, maybe part of About the role. - Then "Successful candidates will have the following qualities Technical Expertise 5+ years of professional experience in software engineering, with a strong emphasis on backend systems and database technologies Proficiency in at least one compiled language, and interest in working with Rust, Java and Go Solid computer science fundamentals, with strong competencies in data structures, algorithms, and software design/architecture Interest in the theory and practice of database query engines. Professional experience or M.Sc./Ph.D in the domain is preferred Familiarity with SQL query execution, optimization, and relational database systems Familiarity with MongoDB or other non-relational databases is a plus but not mandatory Problem-Solving & Collaboration Proven ability to break down complex problems into manageable pieces and deliver solutions Strong verbal and written communication skills with the ability to collaborate across teams, advocate for technical improvements, and articulate ideas clearly Passion for Data A keen interest in empowering users to interact with and analyze data A drive to deliver tools that enable seamless integration between MongoDB and SQL-based workflows Position Expectations Innovate at the intersection of traditional relational databases and modern flexible-schema databases to design, build, and optimize tools to enhance the SQL experience with MongoDB Collaborate with product managers and customer experience teams to evaluate user needs and build features that provide an intuitive and delightful experience to customers Monitor and improve performance, scalability, and reliability of the SQL interface to ensure smooth experiences for users working with large datasets and complex queries Stay updated on emerging trends in the database and cloud industry, bringing innovative ideas to the team Advocate for technical excellence while helping the team balance trade-offs between feature delivery and system quality Success Measures In three months you’ll be familiar with our codebase and tools, have contributed to the development of a new feature, as well as fixed a few bugs in our existing products In six months, you'll be contributing to our ongoing projects and are involved in implementation of a major new feature In twelve months, you’ll be hitting your stride contributing to our roadmap and leading the team's key projects About MongoDB ..." Then benefits: "MongoDB is committed to providing any necessary accommodations... MongoDB, Inc. provides equal employment opportunities..." That's EEO boilerplate, we should remove. Then "MongoDB’s base salary range for this role is posted below. Compensation at the time of offer is unique to each candidate and based on a variety of factors such as skill set, experience, qualifications, and work location. Salary is one part of MongoDB’s total compensation and benefits package. 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. Please note, the base salary range listed below and the benefits in this paragraph are only applicable to U.S.-based candidates. MongoDB’s base salary range for this role in the U.S. is: $126,000—$248,000 USD" Thus we have Pay (salary range) and Benefits (list). Also location maybe part of About the role. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have no explicit Responsibilities list, but there are Position Expectations which could be responsibilities. Also Success Measures maybe responsibilities? The posting includes "Position Expectations" bullet list: Innovate..., Collaborate..., Monitor..., Stay updated..., Advocate... Those are responsibilities. Also "Technical Expertise" etc are qualifications/requirements. "Problem-Solving & Collaboration" and "Passion for Data" maybe skills or qualities. We need to map content to sections, preserving all substantive info. We should not invent sections with placeholder. So we need to decide which sections have content. Let's extract: About the role: Intro paragraph + location sentence. Responsibilities: Position Expectations list (maybe also Success Measures? but those are expectations over time; could be responsibilities as well). We'll treat Position Expectations as responsibilities. Requirements: maybe "Technical Expertise" bullet list (5+ years experience, proficiency in compiled language, CS fundamentals, interest in query engines, professional experience or MSc/PhD preferred, familiarity with SQL execution, familiarity with MongoDB plus). That's requirements. Qualifications: maybe overlapping; but we could treat "Technical Expertise" as qualifications. However we need to avoid duplication. The instruction: Use sections only when posting has real, specific content for it. We can decide to have Requirements and Qualifications separate if content distinct. But we have only one block of qualifications. Could split: Requirements = mandatory (5+ years, proficiency, CS fundamentals, interest in query engines, SQL execution familiarity). Qualifications = preferred (MSc/PhD, MongoDB familiarity). But the posting lumps them together. Might be okay to have only Requirements and not Qualifications, or combine. Skills: Problem-Solving & Collaboration and Passion for Data could be skills. Benefits: list of equity, etc. Pay: salary range. Schedule: none given (no mention of work hours, remote etc). There's location remote USA but not schedule. So we should not include Schedule section. Thus output sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We need to use

for each section heading. Use

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

  for prose. We must not repeat job title as heading. Not include Job ID. We must remove boilerplate: EEO, accommodation request, etc. We must preserve all substantive info. Let's craft. About the role: combine intro paragraph and location. Intro: "The SQL Engines team is working to make MongoDB the first choice of application developers, business analysts and data scientists everywhere by providing a seamless experience for using SQL and BI Tools to natively access data in MongoDB. Our team is responsible for a broad portfolio of analytics products, including JDBC and ODBC drivers, Tableau and PowerBI native connectors and a SQL-to-MQL translation engine. We’re seeking an experienced and passionate Senior Engineer to join our team and help us build the future of the MongoDB SQL Interface — bridging MongoDB's powerful document data model with SQL-based tools and interfaces. This is an opportunity to make a significant impact by enabling our users to query, analyze, and visualize MongoDB data using the world's most widely understood query language: SQL. If you like working on query languages and database systems, and want to help build products that expose the power of MongoDB’s document database to developers and analysts, this team is the place for you!" Location: "This role can be based out of our Austin, New York City, Palo Alto, San Francisco office or remotely in the USA region." We can combine into one

  maybe two paragraphs. Responsibilities: list from Position Expectations. Items: - Innovate at the intersection of traditional relational databases and modern flexible-schema databases to design, build, and optimize tools to enhance the SQL experience with MongoDB - Collaborate with product managers and customer experience teams to evaluate user needs and build features that provide an intuitive and delightful experience to customers - Monitor and improve performance, scalability, and reliability of the SQL interface to ensure smooth experiences for users working with large datasets and complex queries - Stay updated on emerging trends in the database and cloud industry, bringing innovative ideas to the team - Advocate for technical excellence while helping the team balance trade-offs between feature delivery and system quality We could also include Success Measures as responsibilities? But they are expectations over time; maybe we could add as separate list under Responsibilities? However they are not duties but milestones. Might be okay to include as responsibilities as they describe what you'll do. But to avoid duplication, we could add them as part of Responsibilities as well. However the instruction: preserve ALL substantive information. So we should include Success Measures somewhere. Could be under Responsibilities as additional bullet points. Success Measures: - In three months you’ll be familiar with our codebase and tools, have contributed to the development of a new feature, as well as fixed a few bugs in our existing products - In six months, you'll be contributing to our ongoing projects and are involved in implementation of a major new feature - In twelve months, you’ll be hitting your stride contributing to our roadmap and leading the team's key projects These are more like expectations; could be placed under Responsibilities or maybe a separate section like "Expectations". But we only have predefined headings; we could put them under Responsibilities as they are responsibilities over time. Thus Responsibilities list will combine both sets. Requirements: list of technical expertise mandatory items. Let's extract mandatory: - 5+ years of professional experience in software engineering, with a strong emphasis on backend systems and database technologies - Proficiency in at least one compiled language, and interest in working with Rust, Java and Go - Solid computer science fundamentals, with strong competencies in data structures, algorithms, and software design/architecture - Interest in the theory and practice of database query engines - Familiarity with SQL query execution, optimization, and relational database systems (Professional experience or M.Sc./Ph.D in the domain is preferred) -> that's preferred, not mandatory. - Familiarity with MongoDB or other non-relational databases is a plus but not mandatory -> also preferred. Thus Requirements list includes the first five. Qualifications: maybe we could include preferred items as Qualifications: MSc/PhD, MongoDB familiarity. But we have no separate Qualifications section; we could add Qualifications section with those. Skills: Problem-Solving & Collaboration and Passion for Data. List: - Proven ability to break down complex problems into manageable pieces and deliver solutions - Strong verbal and written communication skills with the ability to collaborate across teams, advocate for technical improvements, and articulate ideas clearly - A keen interest in empowering users to interact with and analyze data - A drive to deliver tools that enable seamless integration between MongoDB and SQL-based workflows Benefits: list: - 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: salary range: $126,000—$248,000 USD. We should not include note about US-based only? Might be considered substantive but it's a note. Could include as a

  after Pay. But instruction: Preserve ALL substantive information. So we should include that note. Thus Pay section:

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

  plus maybe a note: "Please note, the base salary range listed below and the benefits in this paragraph are only applicable to U.S.-based candidates." That's substantive. We'll include as a

  after the salary. Now ensure we don't include any boilerplate like EEO, accommodation request, equal employment opportunities, etc. We also need to remove duplicated lines. Now construct HTML. We'll have:

  About the role

  ... intro ...

  This role can be based out of our Austin, New York City, Palo Alto, San Francisco office or remotely in the USA region.

  Responsibilities

  • ...
  ...