Site Reliability Engineer II

We need to output HTML fragment with sections: About the team? Actually headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We have content: About The Team (maybe treat as About the role? Actually "About The Team" is description of team; could be "About the role"? The posting includes "About The Team" and "About The Role". We need headings: About the role (maybe combine both? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: - About The Team: description of team. Could be placed under "About the role"? Or maybe we treat as "About the role" (since it's about the role/team). We'll put that content under

About the role

. - About The Role: description of role, day-to-day, etc. Could be under "Responsibilities". Actually responsibilities are listed in "The Day-to-Day". So we can put responsibilities there. - Requirements: list of requirements. - Qualifications: maybe same as requirements? But we have "Requirements" and "Preferred Skills". Could treat "Qualifications" as the required qualifications (Bachelor's etc). And "Skills" as preferred skills. - Benefits: list of benefits. - Pay: salary range. - Schedule: work schedule (Hybrid work schedule and year-round flex day Friday (half day)). Also mention onsite childcare etc but those are benefits. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, equal opportunity, accommodation, visa sponsorship, Know Your Rights, etc. Also remove application instructions (like "Click here"). We must preserve all substantive information. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. About The Team paragraph: "The Digital Site Reliability Engineering (SRE) team supports one of the fastest-growing lines of business at one of the hottest Quick Service Restaurants as part of the largest group of restaurants in the world. We support both internal and external customers by ensuring that our digital systems, including mobile and web ordering, operate as smoothly and seamlessly as possible. As part of the SRE team, Site Reliability Engineers work closely with Software Developers, Platform Engineering teams, and other stakeholders to help ensure our digital systems are available and performing as expected. Our goal is to deploy and maintain observability, reduce toil through automation, identify and remediate defects, and continuously improve both the environment and our own capabilities. We also ensure we have, or build, the tools necessary to identify root causes and answer questions we had not yet anticipated. Many team members are remote/distributed across the US, while others reside near our Irvine campus Headquarters, and come into the office on a hybrid schedule." That's substantive. About The Role paragraph: "We’re looking for someone who can own a problem from start to finish — someone who is comfortable digging into the code, identifying the issue, and proposing a fix. This person will become a subject matter expert within the Taco Bell Digital space. Fundamentally, we’re looking for someone who lives and breathes observability and automation, and who is passionate about continuously raising the bar. We want someone who listens well, communicates clearly and effectively, drives alignment, and helps engineering teams improve their processes. As a fierce advocate for the customer, your job would take you into troubleshooting issues and incidents, building out new dashboards and alerts, finding out the answers to help us get to the root cause of problems, and ultimately fixing them for good." Then "The Day-to-Day" list: - Create, update, or automate internal business processes or tools to reduce toil and improve team productivity. - Understand and monitor the Taco Bell Digital ecosystem for performance, availability, and accuracy of transactional data. - Communicate and collaborate with both technical and non-technical stakeholders on issues, upcoming changes, and updates to system health. - Perform final validation tests on various mobile and web-based applications, reporting on, and offering feedback on areas for improvement. - Build expertise in serverless infrastructure and initiatives while also learning aspects of modern SRE practices and terms, such as SLIs, SLOs, Observability, toil, and incident response with blameless postmortems. - Work with and adopt Agile practices while participating in a 24/7 on-call rotation. - Collaborate within the team and with cross-functional partners on high-impact business issues that affect revenue and brand reputation. That's responsibilities. Requirements list (bulleted): - Bachelor’s degree in computer science, engineering, OR a related field, OR equivalent work experience. - At least 2+ years of experience in the SRE space, with a focus on observability and automation - Familiarity with SRE core principles (e.g. SLO, SLA, SLI, Error Budget, etc.) - Hands-on experience creating monitors, dashboards, SLOs, and other observability capabilities - Experience with logging solutions or platforms such as DataDog, CloudWatch log insights, etc. - Understanding of incident management practices, including leading bridge calls, conducting RCAs, and facilitating postmortems - Familiarity with modern observability practices and tools, such as distributed tracing, APM, OpenTelemetry, and RUM - Excellent communication and collaboration skills, with the ability to work effectively in a fast-paced environment as a member of a team - A fundamentally complete understanding of Observability principles (not just monitoring) + experience using tools like DataDog, Lumigo, CloudWatch, Incident.io, PagerDuty or similar - General level understanding of Agile methods such as Kanban, Scrum, etc. - Advanced troubleshooting skills - A curious mindset and the desire to always keep learning - Proactive self-starter capable of operating autonomously - Ability to participate in an on-call rotation - Proficiency with SQL (intermediate) - Intermediate understanding of JavaScript, Python, Go, or TypeScript - Fundamental knowledge of AWS services commonly used in serverless and cloud-native environments, including Lambda, API Gateway, Fargate, S3, DynamoDB, and EventBridge Preferred Skills list: - Surrounding software development (Git, CI/CD, reading and writing code) - preferably in JavaScript/TypeScript and/or Python and with tools like VS Code, Gitlab CI/CD or GitHub Actions - Experience with building automations for internal business processes, including AI-embedded workflows - Comfort and familiarity with common Unix-like shells (bash, zsh, etc) - Experience with Retool - Experience with data and observability platforms: FullStory, Amplitude, Embrace - Familiarity with AI agentic tools like Claude Code, Codex, Cursor, etc. - Prior use of issue tracking systems such as Jira - High proficiency with AWS serverless services, including Lambda, API Gateway, Fargate, S3, DynamoDB, and EventBridge. - Experience with Infrastructure as Code (IaC) tools such as Terraform, Pulumi, or CloudFormation - Knowledge of Akamai tools, processes, and SOCC engagement - Proficiency with deploying AI via AWS Bedrock or Agentcore Benefits list (paragraph style but we can convert to list): - Work-Hard, Play-Hard Hybrid work schedule and year-round flex day Friday (half day) - Onsite childcare through Bright Horizons - Onsite dining center and game room (yes, there is a Taco Bell inside the building) - Onsite dry cleaning, laundry services, carwash - Onsite gym with fitness classes and personal trainer sessions - Up to 4 weeks of vacation per year plus holidays and time off for volunteering - Tuition reimbursement and education benefits - Generous parental leave for all new parents and adoption assistance program - 401(k) with a 6% matching contribution from Yum! Brands with immediate vesting - Comprehensive medical & dental including prescription drug benefits and 100% preventive care - Discounts, free food, swag and… honestly, too many good benefits to name Pay: Salary Range $--105,000 to $132,200 annually + bonus eligibility + equity (if applicable) + benefits Note: there is a double dash? "$--105,000". Probably a typo; we keep as is. Schedule: The hybrid schedule and flex day Friday half day is also a benefit but we can put under Schedule. We need to avoid duplication: The hybrid schedule appears both in Benefits and Schedule. We'll keep it under Schedule maybe, and not duplicate in Benefits? But we must preserve all substantive information; we can include it in both sections if it's mentioned multiple times, but better to avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but we should not repeat same content unnecessarily? It says remove duplicated lines. So we should not duplicate identical lines. The hybrid schedule appears in Benefits list and also in Schedule mention. We'll keep it under Schedule and maybe not repeat in Benefits? But the Benefits list includes "Work-Hard, Play-Hard Hybrid work schedule and year-round flex day Friday (half day)" as a bullet. If we remove it from Benefits, we lose that benefit mention. However the schedule is also a benefit. We could keep it under Benefits and also mention Schedule separately but that would duplicate. Better to keep it under Benefits and not have a separate Schedule section if it's same content. But we need a Schedule section only if posting has real specific content for it. The posting mentions "Work-Hard, Play-Hard Hybrid work schedule and year-round flex day Friday (half day)" under benefits. Also earlier: "Many team members are remote/distributed across the US, while others reside near our Irvine campus Headquarters, and come into the office on a hybrid schedule." That's schedule info. So we have schedule info: hybrid schedule, flex day Friday half day. We can put that under Schedule section, and not duplicate in Benefits. However the Benefits list also includes that line; we could keep it there as part of benefits but then we would have duplication if we also list under Schedule. To avoid duplication, we could keep the hybrid schedule info under Schedule and not list it under Benefits. But then we lose the benefit mention? However the benefit mention is essentially the same as schedule; it's still a benefit. The instruction: "Preserve ALL substantive information". If we omit that line from Benefits, we are not preserving that specific phrase as a benefit. But we could keep it under Benefits and also mention schedule separately but rephrase to avoid duplication? Might be okay to keep both as they are slightly different context: one is a benefit, one is schedule. But they are same content. The instruction says remove duplicated lines. So we should not have identical lines duplicated. We can keep the benefit list without that line, and keep schedule section with that line (or similar). That preserves the information (the schedule info) but not as a benefit line. However the benefit list originally included that line; removing it might be considered losing a benefit mention. But the schedule section conveys the same info, so the information is preserved. I think it's acceptable. Thus Benefits section will exclude the hybrid schedule line. Now we need to format. We'll produce:

About the role

... (About The Team)

Responsibilities

• ... each day-to-day item

Requirements

• ... each requirement

Qualifications

Maybe we can treat Qualifications as same as Requirements? But we already have Requirements. Could combine? The instruction says prefer few substantive sections over many thin ones. We could merge Requirements and Qualifications into one section called Requirements? But we need to follow headings list; we can omit Qualifications if no distinct content. However we have "Preferred Skills" which could be Skills section