Sr Site Reliability Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can decide to include "About the role" heading with description paragraph(s). Must not repeat job title as heading. The job title is Sr. Site Reliability Engineer. Not to repeat. - Responsibilities: bullet list. - Education and Work Experience: could be under Requirements or Qualifications. The posting has "Education and Work Experience:" with required and preferred items. Also "Knowledge, Skills and Abilities:" with required list. Also "Licenses and Certifications:" with preferred. We need to map to sections: Possibly "Requirements" for education/experience, "Qualifications" for knowledge/skills/abilities, "Skills" maybe for specific skills list, "Benefits" for benefits description, "Pay" for pay range, "Schedule" maybe not present (no schedule info). So we should not include Schedule if no content. We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, scam warning, application instructions, etc. Also remove duplicated lines. We need to output only HTML fragment, no /, no markdown fences. Let's extract substantive content: Intro paragraph(s): "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!" We need to keep that as description under About the role. Then "Responsibilities:" list: - 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 We need to keep all. Then "Education and Work Experience:": - 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) - 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) Note: The text "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)" appears concatenated without spaces. We need to separate them as separate bullet points. We'll treat each as separate bullet. Then "Knowledge, Skills and Abilities:" Required list: - 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 We need to keep all. Then "Licenses and Certifications:" Preferred: - AWS Certified DevOps Engineer (description) - Certified Kubernetes Administrator (description) - Google Cloud Certified - Professional DevOps Engineer (description) Also there are some generic requirements: At least 18 years of age, Legally authorized to work in the United States, Travel: Travel Required (Yes/No): No, DOT Regulated: DOT Regulated Position (Yes/No): No, Safety Sensitive Position (Yes/No): No. These are minor metadata; we can fold into a short paragraph or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short paragraph for those. Then Pay section: The posting includes pay range details: - Total Target Cash Earnings Opportunity: $123,395 - $222,525 - National Base Pay Range: $107,300 - $193,500 - Explanation about target cash earnings, base pay range, actual pay varies, link to pay lookup. We need to include Pay section with that info. Must not include placeholder like "commensurate with experience". This is specific numbers, so include. Benefits section: The posting includes a paragraph about benefits: "At T-Mobile, employees in regular, non-temporary roles are eligible for an annual bonus or periodic sales incentive or bonus, based on their role. Corporate employees are eligible for a year-end bonus based on individual and/or company performance and which is set at a percentage of the employee’s eligible earnings in the prior year. Certain positions in Customer Care are eligible for monthly bonuses based on individual and/or team performance. The incentive component included in the Total Target Cash Earnings Opportunity reflects target performance. Actual earnings included in the Total Target Cash Earnings Opportunity reflect target performance; actual payouts may vary. At T-Mobile, our benefits exemplify the spirit of One Team, Together! A big part of how we care for one another is working to ensure our benefits evolve to meet the needs of our team members. Full and part-time employees have access to the same benefits when eligible. We cover all of the bases, offering medical, dental and vision insurance, a flexible spending account, 401(k), employee stock grants, employee stock purchase plan, paid time off and up to 12 paid holidays - which total about 4 weeks for new full-time employees and about 2.5 weeks for new part-time employees annually - paid parental and family leave, family building benefits, back-up care, enhanced family support, childcare subsidy, tuition assistance, college coaching, short- and long-term disability, voluntary AD&D coverage, voluntary accident coverage, voluntary life insurance, voluntary disability insurance, and voluntary long-term care insurance. We don't stop there - eligible employees can also receive mobile service & home internet discounts, pet insurance, and access to commuter and transit programs! To learn about T-Mobile’s amazing benefits, check out www.t-mobilebenefits.com." Also earlier there was mention of Total Rewards Package etc. But we can combine benefits description. We should not include the earlier "Total Rewards Package" paragraph? That is part of intro but could be considered benefits. However we already have About the role describing total rewards. Might be duplication. We'll keep the benefits section as the detailed benefits paragraph after the pay section. We also have a paragraph about "Never stop growing! As part of the T-Mobile team..." That's more about career growth; could be part of About the role or maybe a separate section like "Growth Opportunities". But not in allowed headings; we could incorporate into About the role. We must remove boilerplate: EEO, accommodation contact, etc. Also remove the line "T-Mobile USA, Inc. is an Equal Opportunity Employer..." etc. Also remove the accommodation contact line. Also remove the "Please note, this contact channel is not a means to apply..." etc. Also remove the "At T-Mobile, employees in regular, non-temporary roles are eligible for an annual bonus..." Actually that is part of benefits/incentive description; we kept it. We also need to remove duplicated lines: The paragraph about Total Target Cash Earnings Opportunity appears twice? It appears in pay section and also earlier in benefits? Actually we saw it earlier in benefits paragraph: "The incentive component included in the Total Target Cash Earnings Opportunity reflects target performance. Actual earnings included in the Total Target Cash Earnings Opportunity reflect target performance; actual payouts may vary." That's duplicated from pay section explanation. We should keep only once? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we need to deduplicate. We'll keep the pay section explanation and maybe not repeat in benefits. But the benefits paragraph includes that sentence; we could remove that sentence from benefits to avoid duplication. However we need to preserve substantive information; if we remove it, we lose that info. But it's already present in pay section; we can keep it there and omit duplicate. That seems acceptable. Similarly, the sentence about "At T-Mobile, employees in regular, non-temporary roles are eligible for an annual bonus..." appears only once; keep. Now we need to format. We'll produce:
About the role
Intro paragraph(s) (maybe two paragraphs). We'll combine into one
with the description. Then
Responsibilities
- ... each bullet.
Then
Requirements
(for Education and Work Experience). Could also be "Qualifications". But we have both Education/Experience and Knowledge/Skills. We could make Requirements for education/experience, Qualifications for knowledge/skills/abilities, Skills for maybe specific tech stack? But we have many skills already in Knowledge, Skills and Abilities. To avoid thin sections, we could combine Knowledge, Skills and Abilities into Qualifications. And maybe Skills not needed. But we have a separate "Skills" heading allowed; we could put the specific technical skills (like AWS, Python, Bash, CI/CD, Kubernetes, etc.) as Skills. However the Knowledge, Skills and Abilities list already includes those. To avoid duplication, we could make Qualifications for education/experience, and Skills for the list of technical skills. But the instruction: Prefer a few substantive sections over many thin ones. So maybe better to have just Requirements (education/experience) and Qualifications (knowledge/skills/abilities). Benefits and Pay separate. Thus:Requirements
- for education/experience items.
Qualifications
- for Knowledge, Skills and Abilities required list.
Optionally we could also include Licenses and Certifications under Qualifications or a separate section like "Certifications". But