Software Engineer - Postgres

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invention. Remove boilerplate like EEO, legal, application instructions, cookie/navigation, etc. Also remove duplicated lines. We need to parse the posting. Content: Intro paragraph: "At Snowflake, we are powering the era of the agentic enterprise..." etc. That's about the role? Could be "About the role". We'll treat that as About the role. Then description of Snowflake Postgres team: "The Snowflake Postgres team is building a managed Postgres experience inside Snowflake. This role is focused on the control plane..." That's also about role. Then bullet list of responsibilities: "In this role, you will:" followed by list items. Then "Our ideal candidate will have:" list of requirements. Then "Nice to have:" list. Then "Why join this team?" list. Then "Snowflake is growing fast..." paragraph about values. Then "How do you want to make your impact? For jobs located in the United States, please visit the job posting on the Snowflake Careers Site for salary and benefits information: careers.snowflake.com" That's application instruction, should be removed. Then "The following represents the expected range of compensation for this role: The estimated base salary range for this role is $160,000 - $230,000.Additionally, this role is eligible to participate in Snowflake’s bonus and equity plan. The successful candidate’s starting salary will be determined based on permissible, non-discriminatory factors such as skills, experience, and geographic location. This role is also eligible for a competitive benefits package that includes: medical, dental, vision, life, and disability insurance; 401(k) retirement plan; flexible spending & health savings account; at least 12 paid holidays; paid time off; parental leave; employee assistance program; and other company benefits." Then "To comply with pay transparency requirements and other statutes, you can notify us if you believe that a job posting is not compliant by completing this form." That's boilerplate, remove. Thus we have sections: - About the role: intro paragraphs (maybe combine first two paragraphs). - Responsibilities: list under "In this role, you will:". - Requirements: list under "Our ideal candidate will have:" (these are required qualifications). - Skills: maybe combine programming languages etc? Could be part of Requirements. But we can separate Skills if we have explicit list: "Strong programming skills in one or more of Java, Go, C++, or Python." etc. Could be under Skills. - Qualifications: maybe the BS/MS etc. - Benefits: list of benefits. - Pay: salary range and bonus/equity mention. - Schedule: not mentioned, so omit. - Nice to have: could be under Skills or Qualifications? Might be separate "Preferred Qualifications". But we only have headings list; we could put under Skills or Qualifications. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include Skills and Qualifications separate. We need to decide what goes where. We have: - Requirements: "2+ years of experience building production software in backend, infrastructure, or distributed systems environments." etc. That's experience requirement. - Qualifications: "BS/MS in Computer Science, Engineering, or a related field, or equivalent practical experience." - Skills: "Strong programming skills in one or more of Java, Go, C++, or Python." plus "Strong computer science fundamentals, including concurrency, networking, APIs, and data structures." plus "Experience designing and operating reliable services in production, including debugging, monitoring, and incident response." plus "Experience working across technical boundaries with product, security, and other engineering teams." Those could be skills. But the line "Experience designing and operating reliable services in production..." is also a requirement. Might be overlapping. We'll just follow the text: Under "Our ideal candidate will have:" we have a list of items. We'll treat that as Requirements (maybe also Qualifications). Then "Nice to have:" list as Skills? Or we could put Nice to have under Skills as preferred skills. Better: Use Requirements for the mandatory items, Qualifications for education, Skills for technical skills (programming languages, fundamentals), and Nice to have as additional Skills (maybe under Skills as well). But we must not create sections with filler. We have content for each. Let's extract: About the role: combine first two paragraphs up to before "In this role, you will:" maybe. Paragraph1: "At Snowflake, we are powering the era of the agentic enterprise. To usher in this new era, we seek AI-native thinkers across every function who are energized by the opportunity to reinvent how they work. You don’t just use tools; you possess an innate curiosity, treating AI as a high-trust collaborator that is core to how you solve problems and accelerate your impact. We look for low-ego individuals who thrive in dynamic and fast-moving environments and move with an experimental mindset — who rapidly test emerging capabilities to discover simpler, more powerful ways to deliver results. At Snowflake, your role isn't just to execute a function, but to help redefine the future of how work gets done." Paragraph2: "The Snowflake Postgres team is building a managed Postgres experience inside Snowflake. This role is focused on the control plane, where you have the opportunity to work on both on distributed systems at scale and also to work on research grade optimizations at various layers of the software stack including but not limited to provisioning, managing, securing, and operating Postgres in Snowflake. You will work on core backend systems that sit at the intersection of distributed systems, database infrastructure, security, and operational excellence." Combine into About the role. Responsibilities: list items after "In this role, you will:": - Design and build backend services that power provisioning, lifecycle management, and configuration of Snowflake Postgres instances. - Develop features in the access and user model, including authorization, secure administration flows, and customer-facing management capabilities. - Improve the reliability, observability, and operability of asynchronous workflows and background systems that keep the service healthy. - Partner with product, security, and adjacent engineering teams to deliver simple customer experiences on top of complex infrastructure. - Investigate production issues, participate in on-call, and drive fixes that improve resilience and reduce operational burden. - Contribute to technical design, code review, and mentoring while helping raise the engineering bar across the team. Requirements: list under "Our ideal candidate will have:": - 2+ years of experience building production software in backend, infrastructure, or distributed systems environments. - Strong programming skills in one or more of Java, Go, C++, or Python. - Strong computer science fundamentals, including concurrency, networking, APIs, and data structures. - Experience designing and operating reliable services in production, including debugging, monitoring, and incident response. - Experience working across technical boundaries with product, security, and other engineering teams. - BS/MS in Computer Science, Engineering, or a related field, or equivalent practical experience. But the last one is education; could be Qualifications. We could split: Requirements = experience items; Qualifications = education; Skills = programming languages and fundamentals. Let's decide: Requirements (mandatory experience): - 2+ years of experience building production software in backend, infrastructure, or distributed systems environments. - Experience designing and operating reliable services in production, including debugging, monitoring, and incident response. - Experience working across technical boundaries with product, security, and other engineering teams. Skills: - Strong programming skills in one or more of Java, Go, C++, or Python. - Strong computer science fundamentals, including concurrency, networking, APIs, and data structures. Qualifications: - BS/MS in Computer Science, Engineering, or a related field, or equivalent practical experience. Nice to have (preferred): - Experience with PostgreSQL, database internals, or managed database platforms. - Experience with identity, authorization, RBAC, or other security-sensitive systems. - Experience with cloud infrastructure on AWS, Azure, or GCP. - Experience with workflow orchestration, control plane systems, or highly asynchronous service architectures. We could put Nice to have under Skills as "Preferred Skills" but we have no heading for Preferred. Could just include under Skills as additional bullet points, but we need to keep headings only from list. Could add a section "Skills" and include both required and nice-to-have? Might be okay but risk mixing. Better to have Skills for required technical skills, and maybe include nice-to-have under Skills as well but label? Not allowed to add extra headings. Could put nice-to-have under Skills as separate bullet list but still under Skills heading. That's acceptable. Benefits: list from benefits paragraph. Pay: salary range and bonus/equity. Schedule: none -> omit. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We must not include any markdown fences. Let's craft. First, About the role: two paragraphs combined into maybe one

  containing both paragraphs separated by a space or
  ? Use

  for prose; we can have multiple

  elements. We'll put:

  About the role

  At Snowflake, we are powering the era of the agentic enterprise. To usher in this new era, we seek AI-native thinkers across every function who are energized by the opportunity to reinvent how they work. You don’t just use tools; you possess an innate curiosity, treating AI as a high-trust collaborator that is core to how you solve problems and accelerate your impact. We look for low-ego individuals who thrive in dynamic and fast-moving environments and move with an experimental mindset — who rapidly test emerging capabilities to discover simpler, more powerful ways to deliver results. At Snowflake, your role isn't just to execute a function, but to help redefine the future of how work gets done.

  The Snowflake Postgres team is building a managed Postgres experience inside Snowflake. This role is focused on the control plane, where you have the opportunity to work on both on distributed systems at scale and also to work on research grade optimizations at various layers of the software stack including but not limited to provisioning, managing, securing, and operating Postgres in Snowflake. You will work on core backend systems that sit at the intersection of distributed systems, database infrastructure, security, and operational excellence.

  Responsibilities:

  Responsibilities

  • Design and build backend services that power provisioning, lifecycle management, and configuration of Snowflake Postgres instances.
  • Develop features in the access and user model, including authorization, secure administration flows, and customer-facing management capabilities.
  • Improve the reliability, observability, and operability of asynchronous workflows and background systems that keep the service healthy.
  • Partner with product, security, and adjacent engineering teams to deliver simple customer experiences on top of complex infrastructure.
  • Investigate production issues, participate in on-call, and drive fixes that improve resilience and reduce operational burden.
  • Contribute to technical design, code review, and mentoring while helping raise the engineering bar across the team.
  Requirements:

  Requirements

  • 2+ years of experience building production software in backend, infrastructure, or distributed systems environments.
  • Experience designing and operating reliable services in production, including debugging, monitoring, and incident response.
  • Experience working across technical boundaries with product, security, and other engineering teams.
  Skills:

  Skills

  • Strong programming skills in one or more of Java, Go, C++, or Python.
  • Strong computer science fundamentals, including concurrency,