Software Engineer III - Platform 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 if posting has real specific content. We need to parse job description. Content: - Intro: "This position focuses on production support and governance for operational excellence, including: ..." then bullet list of responsibilities. List items: Production support, observability, and production governance/management Designing operating models and process controls Participating in audits and compliance activities Designing dashboards and views Proficient use of Copilot to improve day-to-day efficiency Providing production stability metrics and insights to management Acting as a gatekeeper for GBP production processes and standards Leading meetings, driving decisions, and coordinating cross-functional stakeholders That's responsibilities. Then "Key Technical Skills Required" list: AWS Logging and monitoring tools: Splunk, Dynatrace, Datadog, CloudWatch ServiceNow Kafka API design/integration and troubleshooting Incident, problem, and change management (ITIL-aligned) SRE/operations metrics (availability, reliability, MTTR, SLA/SLO reporting) Root cause analysis and post-incident governance SQL and data analysis for operational reporting CI/CD awareness and release governance Strong communication, stakeholder management, and documentation skills Then "Required Experience And Skills" list: 6+ years of IT troubleshooting, resolution, and maintenance experience. Experience with large-scale on-premises and public-cloud environments, preferably AWS. Strong observability and monitoring knowledge, including Grafana, Dynatrace, Prometheus, Datadog, and Splunk. Familiarity with CI/CD and infrastructure tools such as Jenkins, GitLab, and Terraform. Familiarity with EKS, Kubernetes, Docker, and common networking issues. A proactive approach to learning and recommending new technologies Then "ABOUT US" description: Chase is a leading financial services firm... includes benefits description: "We offer a competitive total rewards package including base salary determined based on the role, experience, skill set and location. Those in eligible roles may receive commission-based pay and/or discretionary incentive compensation, paid in the form of cash and/or forfeitable equity, awarded in recognition of individual achievements and contributions. We also offer a range of benefits and programs to meet employee needs, based on eligibility. These benefits include comprehensive health care coverage, on-site health and wellness centers, a retirement savings plan, backup childcare, tuition reimbursement, mental health support, financial coaching and more. Additional details about total compensation and benefits will be provided during the hiring process." Then EEO boilerplate (remove). Then "About The Team" description. We need to produce sections: maybe "About the role" (intro paragraph), "Responsibilities" (list), "Skills" (technical skills), "Requirements" (experience and skills), "Benefits" (benefits description), maybe "About the company" (About US) but not required heading list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include sections that have content. We have: - About the role: could be the introductory paragraph about position focus. - Responsibilities: bullet list of duties. - Skills: technical skills list. - Requirements: experience and skills list. - Benefits: benefits description. - Pay: maybe mention base salary determined based on role, experience, skill set and location; also commission-based pay etc. That's pay info. So we can include Pay section with that sentence. - Schedule: not mentioned, so omit. - Qualifications: maybe not separate; we have Requirements covering experience/skills; we could treat Requirements as qualifications. But we have both Requirements and Qualifications headings allowed; we can choose to include Requirements only. We must not repeat job title as heading. We must not include boilerplate like EEO, equal opportunity, scam warning, navigation, cookie, legal. We must preserve all substantive info. We need to output HTML fragment only, no /, no markdown fences. Thus produce something like:

About the role

This position focuses on production support and governance for operational excellence, including: ...

But we need to keep the list after colon? The intro includes a colon then list. Could keep as paragraph with colon then maybe we separate responsibilities list. Better: About the role paragraph: "This position focuses on production support and governance for operational excellence." Then responsibilities list separate. We must preserve all substantive info; we can split. Thus:

About the role

This position focuses on production support and governance for operational excellence.

Responsibilities

• Production support, observability, and production governance/management
• Designing operating models and process controls
• Participating in audits and compliance activities
• Designing dashboards and views
• Proficient use of Copilot to improve day-to-day efficiency
• Providing production stability metrics and insights to management
• Acting as a gatekeeper for GBP production processes and standards
• Leading meetings, driving decisions, and coordinating cross-functional stakeholders

Skills

• AWS Logging and monitoring tools: Splunk, Dynatrace, Datadog, CloudWatch
• ServiceNow
• Kafka
• API design/integration and troubleshooting
• Incident, problem, and change management (ITIL-aligned)
• SRE/operations metrics (availability, reliability, MTTR, SLA/SLO reporting)
• Root cause analysis and post-incident governance
• SQL and data analysis for operational reporting
• CI/CD awareness and release governance
• Strong communication, stakeholder management, and documentation skills

Requirements

• 6+ years of IT troubleshooting, resolution, and maintenance experience.
• Experience with large-scale on-premises and public-cloud environments, preferably AWS.
• Strong observability and monitoring knowledge, including Grafana, Dynatrace, Prometheus, Datadog, and Splunk.
• Familiarity with CI/CD and infrastructure tools such as Jenkins, GitLab, and Terraform.
• Familiarity with EKS, Kubernetes, Docker, and common networking issues.
• A proactive approach to learning and recommending new technologies

Benefits

We offer a competitive total rewards package including base salary determined based on the role, experience, skill set and location. Those in eligible roles may receive commission-based pay and/or discretionary incentive compensation, paid in the form of cash and/or forfeitable equity, awarded in recognition of individual achievements and contributions. We also offer a range of benefits and programs to meet employee needs, based on eligibility. These benefits include comprehensive health care coverage, on-site health and wellness centers, a retirement savings plan, backup childcare, tuition reimbursement, mental health support, financial coaching and more. Additional details about total compensation and benefits will be provided during the hiring process.

Pay

Base salary is determined based on the role, experience, skill set and location. Eligible roles may receive commission-based pay and/or discretionary incentive compensation, paid in the form of cash and/or forfeitable equity.

But note we repeated base salary sentence already in Benefits; but we can keep Pay separate focusing on compensation details. However we must not duplicate content? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is okay if it's in original? The original had that sentence in Benefits paragraph. It didn't have a separate Pay sentence. So creating a Pay section with that sentence might be considered summarizing? It's extracting part of the benefits paragraph. Might be okay as it's still substantive info. But we could avoid Pay section if we think it's not explicitly separate; but the posting does mention base salary etc. It's part of benefits paragraph. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state base salary etc. So we can include Pay section with that content. However we must not duplicate the same info in Benefits and Pay; but we could keep Benefits as described (including health etc.) and Pay as just the base salary/commission sentence. That's okay; we are not inventing, just splitting. But we need to ensure we don't omit any substantive info. The benefits paragraph includes base salary sentence; we keep that sentence in Pay section; we still keep benefits paragraph but we might remove the base salary sentence from benefits to avoid duplication? The instruction says preserve ALL substantive information; duplication is not prohibited but might be considered redundant. Safer to keep the base salary sentence only in Pay and keep other benefits in Benefits without that sentence. Let's extract: Benefits paragraph original: "We offer a competitive total rewards package including base salary determined based on the role, experience, skill set and location. Those in eligible roles may receive commission-based pay and/or discretionary incentive compensation, paid in the form of cash and/or forfeitable equity, awarded in recognition of individual achievements and contributions. We also offer a range of benefits and programs to meet employee needs, based on eligibility. These benefits include comprehensive health care coverage, on-site health and wellness centers, a retirement savings plan, backup childcare, tuition reimbursement, mental health support, financial coaching and more. Additional details about total compensation and benefits will be provided during the hiring process." We can split: Pay: "Base salary determined based on the role, experience, skill set and location. Those in eligible roles may receive commission-based pay and/or discretionary incentive compensation, paid in the form of cash and/or forfeitable equity, awarded in recognition of individual achievements and contributions." Benefits: "We also offer a range of benefits and programs to meet employee needs, based on eligibility. These benefits include comprehensive health care coverage, on-site health and wellness centers, a retirement savings plan, backup childcare, tuition reimbursement, mental health support, financial coaching and more. Additional details about total compensation and benefits will be provided during the hiring process." That preserves all info. Now About US: we could include as "About the company" but not in allowed headings list. Could we include as a section? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not About the company. So we should not create a heading for About US. However we need to preserve that substantive info. Where to put it? Could incorporate into About the role? But that would be mixing. Perhaps we can include as a paragraph without heading? The instruction: "Output ONLY the HTML fragment". It didn't forbid extra paragraphs without heading. It said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. It didn't say we cannot have prose outside headings. But likely they expect sections only. However we could include About US as a paragraph under a heading like "About the role"? Might be misrepresenting. Better to include as a paragraph without heading? The instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot have other headings, but they gave examples. It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are the allowed headings. So we should not add other headings. So we need to incorporate About US info somewhere else, maybe as a paragraph under About the role? But About the role