Senior Software Engineer, Site Reliability

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We have content: About Us (company description) but not needed as heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we need sections based on content. We have "About The Role" heading in posting. That's about the role description. Could map to "About the role". We'll include that. Responsibilities: The bullet list under "What You'll Be Doing". That's responsibilities. Requirements: The list under "What (we Think) You'll Need To Do It". That's requirements/qualifications. Qualifications: Might be same as requirements; but we can separate maybe "Qualifications" for nice-to-haves? Actually "Nice To Haves" could be qualifications or skills. We could put "Qualifications" for required, and "Skills" for nice-to-haves? But we need to avoid thin sections. Let's see. We have Salary Range: $180,000 - $200,000. That's Pay. Benefits: mention equity and premium health and wellness benefits. That's Benefits. Schedule: mention hybrid team and work out of NYC or SF office ~3 days a week. That's Schedule. We also have "About Us" but not needed as heading; maybe we could include as a paragraph before sections? The instruction: Output ONLY the HTML fragment. We can include a

for About Us description as intro? Not required but we can include as prose. It says preserve ALL substantive information; do not invent or summarize away detail. So we should include the About Us paragraph as a

before sections. We must not include boilerplate like cookie/navigation/legal/EEO etc. There's none. We must not repeat job title as heading. Not needed. We must not put Job ID/requisition numbers as headings. We must use

for section headings. We must use

• for any list of duties/requirements/benefits. We must use

  for prose. We must not emit a heading followed by filler/placeholder text. We need to ensure we include all substantive info. Let's extract: About Us paragraph: "Parabola is a workflow builder that makes it easy to organize and transform messy data from anywhere—even PDFs, emails, and spreadsheets—so that forward-thinking teams can automate the work they thought would always be manual. Teams at fast-moving companies like Brooklinen, On Running, and Flexport use Parabola to save hundreds of hours and finally take on the projects that used to feel out of reach. Whether it’s reconciling inventory across multiple 3PLs, auditing invoices, or manually exporting the same report every Monday, Parabola gives teams the power to automate it—all without needing engineering support. Parabola is backed by OpenView Partners, Matrix Partners, Thrive Capital and more." That's prose. About the role: The paragraph after "About The Role": "As a Senior Site Reliability Engineer on our rapidly growing team, you’ll measure how well our software is working, and from that baseline propel us towards high impact improvements that our customers value. Given our small team, your work might span performance, developer experience, security & compliance, and foundational architecture work. You’ll also be on-call and will improve our technical operations, learning as we go." That's prose. Responsibilities: bullet list under "What You'll Be Doing". Let's capture each sentence separated by periods? The text: - Monitoring our core business-logic software, both via on-call and in non-urgent situations: describing its existing behavior and defining SLOs or SLAs that get us (you and we) to respond. - Extending and monitoring our infrastructure stack. Because we are B2B, we have fewer raw users, but their usage is often business-critical and we need the infrastructure for that. - Maintaining both a mental and a reified model of our systems: from this model, estimating risk, planning projects, and debugging efficiently. - Collaborating with our engineering team and company leadership from your unique lens on site reliability — being vocal and clear in your expertise in this specialization - Working on our core orchestration logic that determines how to efficiently run tens of thousands of workflows at the same time - we recently rebuilt our orchestrator on top of Temporal and we love it! - Advising many parallel major backend engineering projects, both early in planning and through release. Join such projects for building from time-to-time. - Optimizing our services for scalability, stability, and observability as our customer base grows and our product becomes more sophisticated. - Improving our developer experience in tactical ways, and improving our overall engineering processes and practices more broadly, especially given the opportunities & pressures of LLM coding agents. We'll put each as

• . Requirements: list under "What (we Think) You'll Need To Do It". Items: - 5+ years of SRE, DevOps, or Platform engineering experience - A proven record of building efficient, performant, and easy to extend systems. - Has maintained quantitative metrics of site reliability, while also demonstrating judgment about appropriate strictness for SLOs & SLAs. - Given our team size, the expectations are somewhat less formal and mature than many SRE teams have; you will both strengthen our approach, but also navigate tradeoffs. - Familiarity with containerization and orchestration tools (e.g., Docker, Kubernetes) and how they interact with backend services, and with Linux - Experience implementing and managing AWS infrastructure - You’re not afraid to ask for help, and you’re happy to give it, too. - You’re an enthusiastic communicator and you like working with a team that provides both mutual support and thoughtful critique. - You're excited to join a hybrid team and work out of our NYC or SF office ~3 days a week. Note: The last item about hybrid team is also schedule; but we might treat schedule separately. However it's also a requirement? We'll keep it in requirements maybe but also schedule section. To avoid duplication, we could keep schedule separate and not duplicate. The instruction: preserve ALL substantive information; we can include it in both sections? Might be duplication but okay. Better to put schedule in its own section and not repeat in requirements. So we should remove that item from requirements list. Thus requirements list excludes the hybrid team item. Qualifications: maybe we can treat "Nice To Haves" as Qualifications or Skills. Let's decide: We'll have a section "Qualifications" for required? Actually we already have Requirements. Could have "Qualifications" for nice-to-haves. Or "Skills" for nice-to-haves. Let's follow typical: Requirements = mandatory, Qualifications = preferred. We'll put nice-to-haves under Qualifications. Nice To Haves list: - Experience with Temporal. - Experience building AI platforms, or the tooling and systems behind AI products. - Familiarity with Kubernetes/Helm (we use Amazon EKS). - Experience implementing and deploying infrastructure-as-a-service (IaaS) tools to manage production cloud environments - Experience managing CI/CD pipeline for multiple environments, and developer experience more broadly - Experience building cloud storage or data modeling products. - Experience working at early stage startups. We'll put each as
• under Qualifications. Skills: maybe we could combine some technical skills but we already have requirements and qualifications. Could skip Skills section to avoid thin. Pay: Salary Range: $180,000 - $200,000 plus description. We'll put in

  . Benefits: "Our base salary is one component of Parabola’s competitive total package, which also includes equity and premium health and wellness benefits." We'll put as

  . Schedule: "You're excited to join a hybrid team and work out of our NYC or SF office ~3 days a week." We'll put as

  . Now ensure we don't include filler like "commensurate with experience". Not present. Now produce HTML fragment. Structure:

  About Us paragraph

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Pay

  Salary Range: $180,000 - $200,000 ...

  Benefits

  Our base salary is one component of Parabola’s competitive total package, which also includes equity and premium health and wellness benefits.

  Schedule

  You're excited to join a hybrid team and work out of our NYC or SF office ~3 days a week.

  Check for any missing info: The About Us paragraph includes backing investors. Good. Check that we didn't miss any responsibilities: we captured all. Check that we didn't miss any requirements: we omitted hybrid team item; but we have schedule section covering that. Good. Check that we didn't miss any nice-to-haves: we captured all. Check that we didn't miss any other info like "Given our team size, the expectations are somewhat less formal and mature than many SRE teams have; you will both strengthen our approach, but also navigate tradeoffs." That's included as a requirement item. Check that we didn't miss "You’re not afraid to ask for help, and you’re happy to give it, too." included. Check that we didn't miss "You’re an enthusiastic communicator and you like working with a team that provides both mutual support and thoughtful critique." included. Check that we didn't miss "Experience implementing and managing AWS infrastructure" included. Check that we didn't miss "Familiarity with containerization and orchestration tools (e.g., Docker, Kubernetes) and how they interact with backend services, and with Linux" included. Check that we didn't miss "Has maintained quantitative metrics of site reliability, while also demonstrating judgment about appropriate strictness for SLOs & SLAs." included. Check that we didn't miss "A proven record of building efficient, performant, and easy to extend systems." included. Check that we didn't miss "5+ years of SRE, DevOps, or Platform engineering experience" included. Now ensure we didn't inadvertently include any boilerplate like "This salary range represents the minimum and maximum for this role based in San Francisco and New York. The salary given for this position is dependent on multiple factors, including years of experience, interview performance and anticipated responsibilities of the role." That's part of Pay description; we should include that as prose in Pay section. So Pay section can have a

  with that whole sentence. Thus Pay section:

  Salary Range: $180,000 - $200,000 This salary range represents the minimum and maximum for this role based in San Francisco and New York. The salary given for this position is dependent on multiple factors, including years of experience, interview performance and anticipated responsibilities of the role. Our base salary is one component of Parabola’s competitive total package, which also includes equity and premium health and wellness benefits.

  Wait but we already have Benefits separate; we might combine benefits with Pay? But we have separate Benefits section for equity and premium health. The sentence about base salary being component of total package includes equity and benefits; we could keep that in Benefits. To avoid duplication, we can put the salary range description in Pay, and the benefits sentence in Benefits. Thus Pay:

  Salary Range: $180,000 - $200,000 This salary range represents the minimum and maximum for this role based in San Francisco and New York. The salary given for this position is dependent on multiple factors, including years of experience, interview performance and