Staff Engineer

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 need to parse the posting. First, job title: Impact As a Staff SRE at Shipt... but we should not repeat job title as heading. We need to extract sections: - About the role: The first paragraph(s) describing impact, responsibilities? The posting starts: "Impact As a Staff SRE at Shipt, you will serve as a technical leader across our engineering organization. In this role, you won’t just put out fires—you will architect system resilience, pioneer modern observability, and eliminate systemic friction across our distributed microservices. You’ll work closely with domain product teams (Checkout, Logistics, Catalog, Search, and Shopper Experience) to establish SLO-driven engineering, improve incident response workflows, and drive our multi-cloud and Kubernetes infrastructure strategy forward. In this role you will be responsible for building automated tooling and self-service infrastructure to empower product engineers to deploy safely, monitor effectively, and manage their own service reliability. A core component of this work will also be acting as a technical escalation point during critical incidents while driving a blameless post-mortem culture focused on root-cause elimination, long-term remediations, and automated recovery." That's about the role/responsibilities. Could be "About the role" or "Responsibilities". We need to decide which headings to use. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content. We have content about responsibilities: building tooling, SLO-driven engineering, incident response, etc. Could be "Responsibilities". Also "About the role" could be a brief description. But we should not duplicate. Probably combine into one section "Responsibilities". Or we could have "About the role" as a short paragraph then "Responsibilities" as list. But we need to avoid thin sections. Prefer few substantive sections. We also have "What You’ll Need to Be Successful": list of requirements: 8+ years engineering experience, 5+ years running complex microservices at scale on Kubernetes within cloud environments (AWS and/or GCP), fluent in at least one modern language used for system tooling and backend services, IaC: Advanced experience with Terraform, Helm, and GitOps workflows (e.g., ArgoCD, Flux), Observability Expertise: Hands-on experience with modern observability stacks such as Datadog, Prometheus, Grafana, OpenTelemetry, and central logging platforms, Networking & Edge Security: Strong understanding of TCP/IP, HTTP/2, gRPC, service meshes (e.g., Istio, Linkerd), CDN routing (e.g., Cloudflare, Fastly), and API gateways. That's requirements/qualifications. Could be "Requirements" or "Qualifications". We'll choose "Requirements". Then "Skills & Education": list includes key skills used in this job but is not inclusive of all skills needed for the role. Please see any required education below. Incident Response, Kubernetes, Microservices Architecture, Site Reliability Engineering, Terraform (Software) Bachelor's Degree or equivalent experience | Required That's skills and education. Could be "Skills". We'll include "Skills". Then "Pay Range $95,800-$185,000". That's pay. So include "Pay" section. Then "Work Arrangement": hybrid expectations. That's schedule? Could be "Schedule". It describes in-office expectations. So we can include "Schedule". Then "About Shipt": description of company. Could be "About the role"? Actually that's about company. Could be "About the company" but not in list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put company description under "About the role"? Not ideal. Maybe we can omit because not required? But we must preserve ALL substantive information; cannot omit. We need to include it somewhere. Could treat as "About the role" (though it's about company). Or we could create a section not in list? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples, but we should likely stick to those. However we could also add other headings if needed? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are the allowed headings. It says "include a section ONLY when the posting has real, specific content for it". So we should only use those headings. So we need to map content to those headings. We have: - About the role: could include the impact description and maybe also about Shipt? But "About the role" is about the role, not company. The company description could be placed under "About the role"? Might be a stretch but maybe acceptable. However we also have responsibilities content. Could split: "About the role" for brief overview, "Responsibilities" for detailed duties. We have "About Shipt" paragraph describing company. Could be considered "About the role"? Not really. But maybe we can treat as "About the role" includes both role and company context. The instruction says "About the role" is an example; we could also use "About the company" but not listed. Safer to put company description under "About the role" as it's still about the role context. Alternatively we could omit company description? But we must preserve ALL substantive information. So we need to include it. Thus we will have sections: - About the role: includes the impact paragraph and the About Shipt paragraph. - Responsibilities: maybe we can extract bullet list of duties? The impact paragraph already covers responsibilities; we could keep responsibilities as list derived from that paragraph. But we might duplicate. Better to have About the role as overview, Responsibilities as bullet list of specific duties: building automated tooling, self-service infrastructure, establishing SLO-driven engineering, improving incident response workflows, driving multi-cloud/K8s strategy, acting as technical escalation point, driving blameless post-mortem culture, etc. We can extract those as list items. - Requirements: the "What You’ll Need to Be Successful" bullet points. - Skills: the "Skills & Education" list: Incident Response, Kubernetes, Microservices Architecture, Site Reliability Engineering, Terraform (Software), Bachelor's Degree or equivalent experience. - Pay: the pay range. - Schedule: the work arrangement hybrid expectations. - Benefits: we have benefits mentioned later: "Employees (and eligible family members) are covered by medical, dental, vision and more. Employees may enroll in our company’s 401k plan. Employees will also be eligible to receive discretionary vacation for exempt team members, paid holidays throughout the calendar year and paid sick leave. Other compensation includes eligibility for an annual bonus and the potential for restricted stock units based on role." That's benefits. So we need a Benefits section. Thus we will have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. We should not include Qualifications if we used Requirements; but we could also include Qualifications separate. However we have both Requirements and Skills; Qualifications could be education. But we already included education in Skills. Might be okay to omit Qualifications. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The posting includes EEO statement, accommodation, etc. We must remove those. Thus final HTML fragment:

About the role

Impact As a Staff SRE at Shipt, you will serve as a technical leader across our engineering organization. In this role, you won’t just put out fires—you will architect system resilience, pioneer modern observability, and eliminate systemic friction across our distributed microservices. You’ll work closely with domain product teams (Checkout, Logistics, Catalog, Search, and Shopper Experience) to establish SLO-driven engineering, improve incident response workflows, and drive our multi-cloud and Kubernetes infrastructure strategy forward. In this role you will be responsible for building automated tooling and self-service infrastructure to empower product engineers to deploy safely, monitor effectively, and manage their own service reliability. A core component of this work will also be acting as a technical escalation point during critical incidents while driving a blameless post-mortem culture focused on root-cause elimination, long-term remediations, and automated recovery.

Shipt is a retail tech company that connects people to reliable, high-quality delivery with a personal touch. Shipt connects customers to the things they want from the stores they love, retail businesses to more satisfied customers, and workers to new earning opportunities. At Shipt, we aim to put our team first to boost a sense of belonging, spark opportunities for growth, provide unique benefits and commit to giving back to our communities in ways that make life better, both personally and professionally. We understand that our service, our culture, and our connection to our communities are only made better by every single person who shows up to work here every day. Learn More. Shipt is an independently operated, wholly owned subsidiary of Target Corporation and available in more than 5,000 U.S. cities. Shipt was founded and is headquartered in Birmingham, Alabama.

Responsibilities

• Architect system resilience and pioneer modern observability.
• Eliminate systemic friction across distributed microservices.
• Work with domain product teams (Checkout, Logistics, Catalog, Search, Shopper Experience) to establish SLO-driven engineering.
• Improve incident response workflows.
• Drive multi-cloud and Kubernetes infrastructure strategy.
• Build automated tooling and self-service infrastructure to empower product engineers to deploy safely, monitor effectively, and manage service reliability.
• Act as a technical escalation point during critical incidents.
• Drive a blameless post-mortem culture focused on root-cause elimination, long-term remediations, and automated recovery.

Requirements

• 8+ years of engineering experience.
• 5+ years running complex microservices at scale on Kubernetes within cloud environments (AWS and/or GCP).
• Fluent in at least one modern language used for system tooling and backend services.
• Advanced experience with Infrastructure as Code (IaC): Terraform, Helm, and GitOps workflows (e.g., ArgoCD, Flux).
• Hands‑on experience with modern observability stacks such as Datadog, Prometheus, Grafana, OpenTelemetry, and central logging platforms.
• Strong understanding of TCP/IP, HTTP/2, gRPC, service meshes (e.g., Istio, Linkerd), CDN routing (e.g., Cloudflare, Fastly), and API gateways.

Skills

• Incident Response
• Kubernetes
• Microservices Architecture
• Site Reliability Engineering
• Terraform (Software)
• Bachelor's Degree or equivalent experience

Benefits

• Medical, dental, vision coverage (and more) for employees and eligible family members.
• 401k plan enrollment.
• Discretionary vacation for exempt team members.
• Paid holidays throughout the calendar year.
• Paid sick leave.
• Eligibility for an annual bonus.
• Potential for restricted stock units based on