Sr Site Reliability 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 must not repeat job title. Remove boilerplate, navigation, EEO, etc. Keep substantive info. We need to parse the posting. Key sections: - Intro paragraph about T-Mobile investing, total rewards, etc. That could be "About the role" or maybe "About T-Mobile"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. We have a description: "At T-Mobile, we invest in YOU! Our Total Rewards Package ensures that employees get the same big love we give our customers. All team members receive a competitive base salary and compensation package - this is Total Rewards. Employees enjoy multiple wealth-building opportunities through our annual stock grant, employee stock purchase plan, 401(k), and access to free, year-round money coaches. That’s how we’re UNSTOPPABLE for our employees! Ready grow your career as part of the Uncarrier journey at T-Mobile? Our team is searching for our next Sr. Site Reliability Engineer to strengthen the reliability and resilience of the systems powering T-Mobile's payment platforms, enabling faster, safer software delivery. You'll apply your expertise to reduce manual effort and prevent operational incidents across systems where uptime and trust are non-negotiable. Your skills in programming and scripting, incident response, and modern tooling will keep our payment systems adaptable, secure, and efficient. Through continuous learning, you'll help drive innovation as payments technology evolves. Our team's expertise and partnerships are central to the stability and performance of T-Mobile's payments infrastructure. We pride ourselves on encouraging a culture of innovation, advocating for agile methodologies, and promoting transparency in all that we do. Join us in embodying the spirit of the 'Un-carrier' and make a tangible impact! Our team is dynamic where no day is the same, and we are diverse and inclusive passionate about growth and transformation. If you're up to the challenge, apply today!" That's basically the "About the role" or overview. We'll put under

About the role

with paragraphs. Then "Responsibilities:" list bullet points. We'll put

Responsibilities

with

• each. Then "Education and Work Experience:" includes required and preferred. That could be under "Requirements" or "Qualifications". The instruction includes Requirements and Qualifications headings. We need to decide. Usually Requirements = required qualifications; Qualifications = preferred? But we can combine. We have Education and Work Experience (Required) and Preferred items. Also Knowledge, Skills and Abilities (Required) and Licenses and Certifications (Preferred). Also age, work authorization, travel, DOT etc (these are minor metadata, we can fold into short p or drop). We'll not create separate sections for those unless they have real content. We need to include Pay section: they gave pay range details. So we need

  Pay

  with paragraphs. Benefits: they described benefits extensively. So

  Benefits

  with paragraphs. Schedule: not mentioned; no schedule info. So we omit Schedule. We should not include sections with filler like "commensurate with experience". Not present. We need to preserve all substantive info, not invent or summarize away detail. So we need to include the details: e.g., list of responsibilities exactly as given. Also education and work experience details: Bachelor's Degree plus 3 years... OR advanced degree with 1 year... OR combination... Acceptable areas of study include Computer Science, Engineering or related field (Required). 4-7 years Working in operations or develops environments (Preferred) etc. We need to keep those bullet points? They are not in a list but sentences. We can format as
  • each line. Similarly Knowledge, Skills and Abilities: Required: list of items (AWS, Application Monitoring, Automation Bash, CI/CD, Cloud Infrastructure, Capacity Planning, Emotional Resilience, Incident Management, IaC, Kubernetes, Mentorship, Python, Scripting, System Reliability). We need to keep them as list. Licenses and Certifications: Preferred: list three certifications with descriptions. We'll keep. Also age, work authorization, travel, DOT etc: we can fold into a short p under maybe "Additional Information" but we shouldn't create a heading unless we have real content. Could add a

    with that info. But instruction: "fold minor metadata into a short

    or drop it." So we can include a short paragraph after maybe under a generic heading? But we shouldn't create a heading for minor metadata. Could just add a

    after the Benefits section maybe. But better to include a short paragraph under maybe "Additional Information" but that would be a heading not in allowed list. Safer to just drop them? But they said fold minor metadata into a short

    or drop it. So we can include a

    with that info without a heading. Where to place? Probably after Benefits or before Pay. We'll just add a

    after Benefits containing: "Must be at least 18 years of age, legally authorized to work in the United States. Travel not required. Not a DOT-regulated or safety-sensitive position." Now ensure we don't repeat job title. No headings for Job ID etc. We must output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

    About the role

    ... (the intro paragraph(s) maybe split into multiple paragraphs for readability). We'll keep as one or two paragraphs.

    Responsibilities

    • Enhance system reliability and resilience by identifying issues and implementing preventive measures to reduce downtime
    • Apply hands-on experience with Cassandra, other NoSQL databases, and SQL databases to strengthen the reliability and scalability of distributed payment systems.
    • Automate processes to accelerate software development and deployment while minimizing manual interventions
    • Conduct root cause analysis and collaborate with problem management to prevent incident recurrence and improve system operations
    • Apply problem-solving and analytical skills to prevent operational incidents and maintain system stability
    • Leverage programming, scripting, and incident response expertise to improve system robustness and efficiency
    • Continuously learn new skills and technologies to adapt to changing environments and drive innovation
    • Also responsible for other duties/projects as assigned by business management as needed

    Requirements

    Maybe combine Education and Work Experience and Knowledge, Skills and Abilities? But we have separate headings: Requirements, Qualifications, Skills. The instruction list includes Requirements, Qualifications, Skills. We could put Education and Work Experience under Requirements, Knowledge, Skills and Abilities under Skills, and Licenses and Certifications under Qualifications? Or we could put all under Requirements. But better to follow allowed headings: we can use Requirements for mandatory education/experience, Qualifications for preferred experience, Skills for KSAs, Benefits, Pay. However we have both required and preferred items in Education and Work Experience. Could split: Required education/experience under Requirements, Preferred under Qualifications. Then Knowledge, Skills and Abilities (Required) under Skills. Licenses and Certifications (Preferred) could also go under Qualifications or maybe under Skills? But they are certifications, could be Qualifications. We'll decide. Let's map: - Requirements: Education and Work Experience (Required) bullet: Bachelor's Degree plus 3 years... OR advanced degree with 1 year... OR combination... Acceptable areas of study include Computer Science, Engineering or related field (Required). - Qualifications: Preferred experience items: 4-7 years Working in operations or develops environments (Preferred); 4-7 years Troubleshooting customer related issues and managing customer relationships (Preferred); 4-7 years Developing software solutions using Python or similar programming languages (Preferred). Also Licenses and Certifications (Preferred) maybe also under Qualifications. - Skills: Knowledge, Skills and Abilities (Required) list. But we also have Licenses and Certifications (Preferred) with descriptions. Could put under Qualifications as well. We must not create headings with filler. All have content. Thus:

    Requirements

    • Bachelor's Degree plus 3 years of related work experience OR advanced degree with 1 year of related work experience OR combination of education and experience deemed equivalent (Required)
    • Acceptable areas of study include Computer Science, Engineering or related field (Required)

    Qualifications

    • 4-7 years Working in operations or develops environments (Preferred)
    • 4-7 years Troubleshooting customer related issues and managing customer relationships (Preferred)
    • 4-7 years Developing software solutions using Python or similar programming languages (Preferred)
    • AWS Certified DevOps Engineer (Preferred) – validates technical expertise in provisioning, operating, and managing distributed application systems on the AWS platform.
    • Certified Kubernetes Administrator (Preferred) – validates the skills required for day-to-day administration of Kubernetes environments.
    • Google Cloud Certified - Professional DevOps Engineer (Preferred) – validates the ability to efficiently develop and deploy applications using Google Cloud technologies and to manage operations.

    Skills

    • AWS
    • Application Monitoring
    • Automation
    • Bash (Programming Language)
    • CI/CD (Required)
    • Cloud Infrastructure
    • Capacity Planning
    • Emotional Resilience
    • Incident Management
    • IaC (Infrastructure as Code)
    • Kubernetes
    • Mentorship
    • Python (Programming Language)
    • Scripting
    • System Reliability
    Now Benefits: we need to include the benefits paragraph. Could break into multiple

    but we can just one

    with the list. However it's long; we could keep as

    but it's okay. Pay: include the pay range details. We'll put

    Pay

    with paragraphs. We also need to include the short metadata paragraph about age, work auth, travel, DOT. We'll add after Benefits maybe as a

    . Now ensure we don't include any boilerplate like EEO, etc. We removed. Check for any repeated content: The intro paragraph includes "At T-Mobile, we invest in YOU! ..." We'll keep that. Now produce HTML. Let's craft the About the role paragraph(s). Could split into two paragraphs for readability but not required. We'll output:

    About the role

    At T-Mobile, we invest in YOU! Our Total Rewards Package ensures that employees get the same big love we give our customers. All team members receive a competitive base salary and compensation package - this is Total Rewards. Employees enjoy multiple wealth-building opportunities through our annual stock grant, employee stock purchase plan, 401(k), and access to free, year-round money coaches. That’s how we’re UNSTOPPABLE for our employees!

    Ready to grow your career as part of the Uncarrier journey at T-Mobile? Our team is searching for our next Sr. Site Reliability Engineer to strengthen the reliability and resilience of the systems powering T-Mobile's payment platforms, enabling faster, safer software delivery. You'll apply your expertise to reduce manual effort and prevent operational incidents across systems where uptime and trust are non-negotiable. Your skills in programming and scripting, incident response, and modern tooling will keep our payment systems adaptable, secure, and efficient. Through continuous learning, you'll help drive innovation as payments technology evolves. Our team's expertise and partnerships are central to the stability and performance of T-M