Sr. Platform Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the job description. The description includes: - Job Description: paragraphs about design, build, operate platform etc. That's responsibilities. - Then "Qualifications" section: bullet list of qualifications. - Then "About Munich Re": description of company. - Then "What Can We Offer You?" includes benefits: insurance, 401k, PTO, bonus, wellness programs, tuition assistance, etc. - Also includes "The base salary range anticipated for this position is $147,000 - 170,000, plus an opportunity for an annual company bonus based upon a percentage of eligible pay." That's Pay. - No explicit schedule info (like full-time, remote). Not present, so we should not create Schedule section. - Also there is mention of "Please note that only candidates who are selected for interview will be contacted directly." That's application instruction; we should remove. - Also EEO statements etc: remove. - Also "At Munich Re US, we see Diversity and Inclusion..." etc: remove as boilerplate. - Also "We are an equal opportunity employer." remove. - Also "Reasonable accommodations may be made..." remove. Thus we need sections: - About the role: maybe a short paragraph summarizing role? The job description starts with "Job Description Design, build, and operate..." That's basically responsibilities. Could treat as About the role? Usually About the role is a brief overview. But we have no separate "About the role" heading in source. However we can create About the role section with the introductory paragraph(s) that describe the role. The responsibilities can be a separate Responsibilities section with bullet list. We need to decide: The instructions: 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. Do NOT repeat the job title as a heading. Prefer a few substantive sections over many thin ones. We have content for: - About the role: maybe a paragraph summarizing the role: "Design, build, and operate a secure and reliable internal platform for running business applications and machine learning workloads at scale." That's a prose. - Responsibilities: list of duties: bullet points from the description after that first sentence? Let's extract. The description after first sentence: "Develop and maintain self-service capabilities (golden paths) for provisioning infrastructure, deploying workloads, and managing the application lifecycle through standardized APIs, templates, and automation. Build and evolve reusable platform primitives such as K8s clusters, ingress, service networking, secrets management, policy controls, and identity integration. Maintain cloud and platform infrastructure using Infrastructure as Code (e.g., Terraform, Pulumi, Crossplane) in a secure, scalable, and reusable manner, including modular design, versioning, policy guardrails, automated validation, and safe rollout practices. Implement and maintain platform-level CI/CD patterns that support multiple teams while enforcing secure and compliant SDLC practices. Provide opinionated reference architectures and reusable building blocks (e.g., Helm charts, Argo CD apps, Terraform modules, scaffolding tools) that enable consistent delivery. Implement guardrails for security and compliance (policy-as-code, least privilege, workload identity, image provenance, runtime controls) while maintaining developer velocity. Own platform observability by establishing monitoring, logging, tracing, alerting, and SLO practices to keep the developer platform stable and measurable. Drive platform reliability and operational excellence through incident response, root cause analysis, postmortems, and continuous improvement to reduce toil. Support daily operations, monitoring, and security functions of the platform stack, including routine maintenance, access and identity workflows, vulnerability remediation, and operational support for internal platform services. Partner closely with application teams and stakeholders to understand friction points, prioritize the platform roadmap, and deliver measurable improvements in developer experience and time-to-production. Lead through influence and consensus, providing technical guidance, reviews, and mentorship to peers and junior engineers. Own your professional development, continuously learning new technologies and domain context to operate as a subject matter expert (SME)." That's a long list; we can turn each sentence into

• . - Requirements: maybe we can combine Qualifications and Skills? The posting has "Qualifications" heading with bullet list of qualifications. Also there is a list of skills/experience within that. Could treat "Qualifications" as the heading for those bullet points. The instructions include Requirements and Qualifications as possible headings. We need to decide which to use. Since the source has "Qualifications" heading, we should use that. Could also have a Requirements section for any mandatory requirements (like degree). But we can just use Qualifications for all qualification bullet points. The instructions: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include Qualifications. - Skills: maybe we could extract skills from qualifications list (like strong experience with K8s, etc.) but those are already in qualifications. Could create a Skills section for technical skills like Go, Python, TypeScript, etc. But we risk duplication. Better to have Qualifications cover all. - Benefits: from "What Can We Offer You?" paragraph. We'll list bullet points. - Pay: from salary range paragraph. - Schedule: none, so omit. - About Munich Re: maybe we could include as About the role? Actually "About Munich Re" is company description, not role. Could be considered "About the role"? Not exactly. But we could include a section "About the company" but not in allowed headings. The allowed headings list does not include "About the company". So we should not create a heading for it. However we need to preserve all substantive information. The instructions: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include the company description somewhere. Where can we put it? Could be part of About the role? But that would be mixing role description with company info. Might be okay if we treat About the role as a combination of role overview and company info. However the instructions say "About the role" is a heading for role overview. But we can still include company description under About the role? Might be considered not strictly role but still substantive. However we could also create a section "About Munich Re" but that's not in the allowed headings list; but the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the expected headings. It might be okay to use other headings if needed, but they gave examples. Safer to stick to those headings. So we need to fit company description somewhere. Perhaps we can include it under "About the role" as a brief paragraph about the company context. That would preserve the info. Thus About the role section will contain two paragraphs: one describing the role (first sentence) and another describing Munich Re (the "About Munich Re" paragraph). We'll keep them as separate

  tags. Now Responsibilities: bullet list from the responsibilities sentences. Qualifications: bullet list from the qualifications section. Benefits: bullet list from benefits. Pay: paragraph with salary range and bonus. We must not include any boilerplate like EEO, navigation, etc. Let's extract qualifications bullet points: From text: "Qualifications Bachelor's degree in Computer Science, Information Technology, Engineering, or a related field. Hands-on experience designing and operating platform services using Infrastructure as Code (Terraform, Pulumi, Crossplane, or CSP-native tooling) with a modular, reusable approach. Strong experience with K8s or OpenShift and core platform components, including networking, ingress, service discovery, storage, RBAC, admission control, and multi-tenancy. Experience implementing and standardizing CI/CD for multi-team environments, ideally with GitHub Actions and Argo CD, including release strategies and deployment automation. Experience with at least one major Cloud Service Provider such as Azure, GCP, or AWS. Strong networking fundamentals, including DNS, TLS, load balancing, routing, and private connectivity. Strong security foundations across identity, application, data, network, and supply-chain security, including scanning, signing, SBOM, secrets handling, and policy enforcement. Strong software engineering fundamentals and experience building internal tooling and automation, ideally in Go, Python, or TypeScript. Experience with containers and container tooling, including Docker, registries, and image build pipelines. Excellent knowledge of Linux operating systems and operational troubleshooting. Proven experience leading incident response, including triage, mitigation, coordination across teams, and driving post-incident improvements. Deep knowledge of observability tooling and practices, such as Prometheus, Grafana, and Datadog. Strong problem-solving and analytical abilities, with excellent communication and cross-functional collaboration skills." We need to turn each sentence into

  . Some sentences are long but okay. Now Benefits bullet points: From "What Can We Offer You?": - Two options for your health insurance plan (PPO or High Deductible). - Prescription drug coverage (included in your health insurance plan). - Vision and dental insurance plans. - Additional insurance coverages provided at no cost to you, such as basic life insurance equal to 1x annual salary and AD&D coverage that is equal to 1x annual salary. - Short and Long-Term Disability coverage. - Supplemental Life and AD&D plans that you can purchase for yourself and dependents (includes Spouse/domestic partner and children). - Voluntary Benefit plans that supplement your health and life insurance plans (Accident, Critical Illness and Hospital Indemnity). - In addition to the above insurance offerings, our employees also enjoy: - A robust 401k plan with up to a 6% employer match - Paid time off that begins with 24 days each year, with more days added when you celebrate milestone service anniversaries. - Eligibility to receive a yearly bonus as a Munich Re employee. - A variety of health and wellness programs provided at no cost, including a gym fitness reimbursement. - Paid time off for eligible family care needs. - Tuition assistance and educational achievement bonuses. - A corporate matching gifts program that further enhances your charitable donation. - Paid time off to volunteer in your community. We need to preserve all. We'll make a flat list; we can keep sub-bullets as separate

  items under same

  . That's fine. Now Pay paragraph: "The base salary range anticipated for this position is $147,000 - 170,000, plus an opportunity for an annual company bonus based upon a percentage of eligible pay. The salary estimate displayed represents the typical salary range for candidates hired in this position. Factors that may be used to determine your actual salary include your specific skills, how many years of experience you have and comparison to other employees already in this role." We'll put that as a

  . Now we need to ensure we don't include any application instructions like "Please note that only candidates who are selected for interview will be contacted directly." Remove. Also remove "We thank all candidates for their interest." etc. Also remove the diversity inclusion statements at the end. Now produce HTML fragment:

  About the role

  Design, build, and operate a secure and reliable internal platform for running business applications and machine learning workloads at scale.

  Munich Re is the world’s leading reinsurance company with more than 4