Infrastructure Engineer ll
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content.
We have:
- About the role: description of role (first paragraph after About the Job). Could be "About the role".
- Responsibilities: The Day-to-Day bullet list.
- Requirements/Qualifications/Skills: The "Is this you?" list includes experience, tech, degree, communication, problem solving. Could split into Requirements (experience, degree) and Skills (tech, communication). But we can combine into Requirements and Skills sections if content.
- Benefits: list of benefits (onsite childcare, dining center, game room, dry cleaning, laundry, carwash, gym, vacation, parental leave, 401k, medical/dental, discounts, free food, swag). Also mention "Hybrid work schedule and year-round flex day Friday" maybe under Schedule.
- Pay: Salary range $88,500 to $104,400 annually + bonus eligibility + benefits.
- Schedule: Hybrid work schedule and year-round flex day Friday. Also mention rotational on call during Night and Weekend hours as needed (1 week per month) from responsibilities? Actually that is in The Day-to-Day: "Be available for rotational on call during Night and Weekend hours as needed for critical issues (1 week per month)". That could be part of Schedule or Responsibilities. Probably schedule.
We must not create sections with filler like "commensurate with experience". We have actual content.
We must not include boilerplate like EEO etc. Remove that.
We must not include application instructions.
We must preserve all substantive info.
We need to output only HTML fragment, no html/body tags, no markdown fences.
We'll produce something like:
About the role
...
Responsibilities
- ... ...
Requirements
- At least 2 years SQL experience... ... maybe also degree.
Skills
- Proficient working with technologies: AWS (Lambda, EventBridge, Cloudwatch, DynamoDB), Grafana, Python, REST APIs, GraphQL, Postman ... etc.
Benefits
- Onsite childcare through Bright Horizons ... etc.
Pay
Salary range $88,500 to $104,400 annually + bonus eligibility + benefits.
Schedule
Hybrid work schedule with year‑round flex day Friday; rotational on‑call one week per month during night and weekend hours as needed.
Make sure we preserve all details: mention "Be available for rotational on call during Night and Weekend hours as needed for critical issues (1 week per month)". Also mention "Hybrid work schedule and year-round flex day Friday". Also mention "Onsite dining center and game room (yes, there is a Taco Bell inside the building)". Also "Onsite dry cleaning, laundry services, carwash". Also "Onsite gym with fitness classes and personal trainer sessions". Also "Up to 4 weeks of vacation per year plus holidays and time off for volunteering". Also "Generous parental leave for all new parents and adoption assistance program". Also "401(k) with a 6% matching contribution from Yum! Brands with immediate vesting". Also "Comprehensive medical & dental including prescription drug benefits and 100% preventive care". Also "Discounts, free food, swag and… honestly, too many good benefits to name". Also mention "Salary Range $88,500 to $104,400 annually + bonus eligibility + benefits." Also mention "The above represents the expected salary range for this job requisition. Ultimately, in determining your pay, we'll consider your location, experience, and other job-related factors." Might be considered filler? It's substantive about pay determination. We can include in Pay section. We must not repeat job title. Not include "Who is Taco Bell?" etc. That's company description; maybe we could include as About the role? Actually the initial paragraph about Taco Bell is company overview, not role. The instruction: "Preserve ALL substantive information". Should we include that company overview? It's substantive about the company. The user gave that as part of job posting. Should we include? The instruction: "Reformat a job posting into clean, well-structured semantic HTML." So we should include all substantive info from the posting, including company overview. However we must not repeat the job title as heading. The company overview is not a heading; we can put it in abefore sections. Probably include as an introductory paragraph. Thus output: introductory paragraph about Taco Bell (the first paragraph up to "Learn more about the career below." maybe we can include that). Then sections. We must not include "Learn more about the career below." maybe it's fluff but it's part of posting. Could keep. We must not include cookie/navigation/legal/EEO etc. Remove the EEO paragraph at end. Let's craft. Intro: "Taco Bell was born and raised in California and has been around since 1962. We went from selling everyone’s favorite Crunchy Tacos on the West Coast to a global brand with 8,200+ restaurants, 350 franchise organizations, that serve 42+ million fans each week around the globe. We’re not only the largest Mexican-inspired quick service brand (QSR) in the world, we’re also part of the biggest restaurant group in the world: Yum! Brands. Much of our fan love and authentic connection with our communities are rooted in being rebels with a cause. From ensuring we use high quality, sustainable ingredients to elevating restaurant technology in ways that hasn’t been done before… we will continue to be inclusive, bold, challenge the status quo and push industry boundaries. We’re a company that celebrates and advocates for different, has bold self-expression, strives for a better future, and brings the fun while we’re at it. We fuel our culture with real people who bring unique experiences. We inspire and enable our teams and the world to Live Más. At Taco Bell, we’re Cultural Rebels. Want to join in on the passion-fueled fun? Learn more about the career below." Then About the role: "Taco Bell’s In Store Serverless team is seeking an Infrastructure Engineer II to support a suite of AWS-hosted middleware platforms responsible for the enterprise-scale routing of business critical data between Front of House, Back of House, and Above Store systems across Taco Bell restaurants. This role is focused on applying Agile software development methodology to build out our monitoring, alerting, and operational support infrastructure, ensuring the availability, reliability, and integrity of data powering Taco Bell’s interconnected technology ecosystem." Responsibilities: list items from The Day-to-Day. Let's extract each bullet: - Monitor, troubleshoot, and support enterprise middleware platforms responsible for routing critical business data between restaurant and cloud infrastructure - Interface with the product development team, providing detailed root cause analysis to ensure system stability and reduce defect leakage - Construct and enhance internal tools and applications to bolster the In Store Serverless platform suite by leveraging systems including AWS Lambda, Retool, Claude Code, and Cursor. This role involves creating and refining software solutions that support and optimize operational workflows, platform visibility, and support team effectiveness. - Leverage our bespoke observability solutions to proactively identify and rapidly resolve production issues impacting platform stability and data integrity - Work closely with Development and QA teams across the Restaurant Data Router, Back of House Data Router, and HR Middleware platforms to support requirement gathering, testing, validation, troubleshooting, and phased production releases - Work with L1/L2 IT Support Teams to resolve escalated production incidents and operational issues affecting restaurant technology systems - Develop and maintain operational documentation, alerting standards, and support procedures to improve incident response and platform resiliency - Follow Software Development Life Cycle and Taco Bell’s Change Management procedures (Agile) - Be available for rotational on call during Night and Weekend hours as needed for critical issues (1 week per month) We'll put each as
Requirements
- At least 2 years SQL experience with an emphasis on building queries, joining tables and running/creating stored procedures & SQL templates.
- At least 3 years of experience working with programming languages to build scripts/programs (Python, JavaScript, C# preferred)
- Experience building monitoring, alerting, and observability solutions in cloud-native environments
- Bachelor’s degree required, Computer Science or related field preferred
Skills
- Proficient working with technologies: AWS (Lambda, EventBridge, Cloudwatch, DynamoDB), Grafana, Python, REST APIs, GraphQL, Postman
- Excellent written and verbal communication skills are essential for this role, as Infrastructure Engineers often need to communicate with technical and non-technical stakeholders
- Strong problem-solving, prioritization and multitasking skills for identifying and resolving issues in a production environment
- Result focused and proactive mindset with ability to build process and documentation to diagnose problems and follow through to resolution