Senior Software Engineer, Platform

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

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate. Include sections only when posting has real specific content. So we need to extract content. Let's parse the posting. Company Description: not needed? It's description of company; maybe we can include as About the role? Actually "About the role" heading could contain overview of role. The posting includes "Overview" section: "You must be work authorized in the United States without the need for employer sponsorship. This is a hybrid role requiring 3 days a week in a CJ office location (www.cj.com)". Also "About CJ Engineering" etc. That's more about company culture. Could be part of About the role? But we need to decide. We have sections: Responsibilities (clearly present). Qualifications (present). Skills? Not explicit list but could be derived from Technologies We Use etc. Could treat as Skills. Benefits: there is a section "Additional Information" includes benefits like flexible time off, paid holidays, etc. Also "Why Our Workplace Stands Out" includes benefits. So we can create Benefits section. Pay: there is "Compensation Range: USD $112,290.00 - USD $172,032.00/Annually." So we can include Pay section. Schedule: there is hybrid role requiring 3 days a week in office. Also earlier "Overview" says hybrid role requiring 3 days a week in a CJ office location. So we can include Schedule section. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive information, not invent or summarize away detail. So we need to include details from responsibilities, qualifications, technologies, etc. We must not repeat job title as heading. The job title is Senior Software Engineer on the Engineering Experience (EngExp) platform team. We should not put that as heading. We need to output only HTML fragment, no /, no markdown fences. We need to use

  for section headings. For each section we need content: either

  prose or

  • for lists. We need to decide which sections to include: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. We must ensure we only include sections with real specific content. Let's extract content for each. About the role: Could combine overview and description of role: "As a Senior Software Engineer on the Engineering Experience (EngExp) platform team, you help run and evolve the platform that powers CJ's production systems across multiple AWS regions." plus description of platform etc. Also "You are a leader on the team: you own the reliability and operability of the platform, act as a critical reviewer of systems and changes, set standards, and mentor other engineers." Also maybe "We especially want someone with real depth in the systems below". That's more qualifications. But we can put overview in About the role. Responsibilities: The "Responsibilities" heading in posting includes bullet-like paragraphs. We need to convert to
    • . The content includes: - The Systems You Work On: EngExp Owns The Systems Below. You'll Own Their Reliability, Be The Critical Reviewer Of Changes To Them, And Raise The Team's Depth In Them Then sub-bullets: Observability & monitoring — Prometheus, Alertmanager, Grafana, and OpenTelemetry across every production region. This is not dashboard-building: you own cardinality budgets and recording-rule design, keep a production Prometheus healthy as it outgrows a single shard (federation / sharding / long-term store strategy), and own Alertmanager HA and the blast radius of alert-routing config. Deep Prometheus and Alertmanager expertise is a core requirement. Kubernetes & cloud infrastructure — multi-region EKS clusters: upgrades, node group and Karpenter management, controller lifecycle, and add-on / configuration management. Identify failure modes before they happen (subnet IP exhaustion, API server latency, ArgoCD reconciliation lag, Prometheus cardinality, Karpenter consolidation disruption). AWS networking — VPC design, subnet allocation and CIDR management, VPC peering, Transit Gateway, security groups, Route53, and NAT gateway topology across multiple accounts and regions, plus 24/7 networking alarms for all prod networking between clusters and squad resources. CI/CD & artifact management — GitLab administration (runner fleet, AMI updates, cache, access - not just pipeline authoring), GitOps delivery through ArgoCD, and the Nexus artifact repository including its storage lifecycle as it grows. Access & identity — Vault secrets management, IAM roles and service accounts for apps in clusters, cluster permission management for audit compliance, and AI model access management (including cost alerts and reporting). Cost observability — OpenCost, EBS orphan cleanup, cost anomaly investigation, and rightsizing attribution across teams, so waste is attributable rather than shared overhead. Internal tools & delivery — the container image build pipeline and base image standards, code audit tooling, HedgeDoc, and the UI CDN (S3 + CloudFront), plus adopted applications with no other owner. What You'll Do (list): - Own the reliability and operability of the systems above - focused on what is happening and why - Establish and enforce platform standards: RBAC, admission webhooks, resource limits, LimitRanges, policy-as-code - Manage infrastructure-as-code with Terraform across AWS accounts - Act as a high-quality reviewer of infrastructure changes - Terraform, Kubernetes configs, CI/CD pipelines, observability config - catching subtle issues and long-term risks before they ship - Turn recurring requests (ingress, DNS, service accounts) into self-service workflows that are hard to misuse - Drive resolution of platform incidents with a focus on learning and lasting system improvement - Evaluate new patterns (Gateway API / Kgateway, claim-based self-service) on tradeoffs, not hype - Mentor less-senior engineers and raise the team's depth in the components we own We need to include all that as list items. Qualifications: The posting has "Qualifications What We Look For:" with bullet points: - 6+ years of experience in software and/or infrastructure engineering - Bachelor's degree or equivalent experience - Deep, hands-on production experience operating Kubernetes and AWS at scale, across multiple accounts and regions - Real operational depth in at least one system we own beyond the cluster - most importantly the observability stack (Prometheus/Alertmanager at scale), but AWS networking, Vault, or artifact/CI infrastructure also count. We are filtering for people who have run these systems, not just used them. - Strong AWS networking judgment (VPC, peering, Transit Gateway, subnet/CIDR design) - A track record as a critical reviewer - spotting subtle infrastructure issues and long-term risks before they ship - Experience leading technical work and mentoring engineers; can manage, clarify, and plan around uncertainty - Effective communication and the ability to influence design in a product-focused way Also "Nice To Have" list: but those are optional; we could include under Skills maybe? But we can treat Nice To Have as part of Skills or Qualifications? The instruction: Use
      • for any list of duties/requirements/benefits. So Nice To Have is a list of requirements (nice-to-have). Could be included under Qualifications or Skills. Probably better to include under Qualifications as optional? But we could create a Skills section for technologies. However we have a separate "Technologies We Use" list. That could be Skills. Thus we can have Skills section: list of technologies used. Let's extract Technologies We Use: - Kubernetes / EKS (multi-cluster, multi-region), Karpenter, cert-manager, external-dns - Prometheus, Alertmanager, Grafana, OpenTelemetry (and long-term storage / sharding for Prometheus) - AWS networking (VPC, VPC peering, Transit Gateway, Route53, NAT Gateway, security groups, subnet/CIDR design across accounts and regions) - Terraform, AWS (IAM, EKS, S3, EBS) - ArgoCD, GitLab CI/CD, Nexus (artifact registry), Docker, container image build pipelines - Vault, OpenCost - Gateway API / Kgateway - Kubernetes controllers/operators (reconciliation patterns, restart safety) - Go experience is a plus, not required We can put these as
        • . Benefits: from "Additional Information" and "Why Our Workplace Stands Out". Let's gather: - Flexible time off without the hassle of accrual - A generous number of paid holidays - Company-sponsored team-building events - An Employee Referral Program - Annual recognition awards - Hybrid work arrangements for optimal work-life balance - Parental bonding leave - Backup care options for children and elders - An employee discount program - International SOS program for global support - Business Resource Groups, where employees connect over shared interests to cultivate an engaging, inclusive environment - Competitive salaries, 401K matching, wellness programs, comprehensive medical, dental, and vision coverage (mentioned earlier) Also earlier: "Apart from offering competitive salaries, 401K matching, wellness programs, and comprehensive medical, dental, and vision coverage, we provide:" then list. Thus Benefits section includes those items. Pay: Compensation Range: USD $112,290.00 - USD $172,032.00/Annually. Schedule: hybrid role requiring 3 days a week in office. Also mention "This is a hybrid role requiring 3 days a week in a CJ office location (www.cj.com)". Also later "This is a hybrid role requiring 3 days a week in office." So schedule: 3 days per week in office, rest remote. We need to avoid repeating info. Now we need to output HTML. Structure:

          About the role

          ...

          Responsibilities

          • ...
          ...

          Qualifications

          • ...
          ...

          Skills

          • ...
          ...

          Benefits

          • ...
          ...

          Pay

          ...

          Schedule

          ...

          Make sure not to include empty sections. Now craft the prose for About the role: combine overview and role description. From posting: Overview: "You must be work authorized in the United States without the need for employer sponsorship. This is a hybrid role requiring 3 days a week in a CJ office location (www.cj.com)" - but schedule and work auth maybe better in Schedule and maybe a note. However About the role could include: "As a Senior Software Engineer on the Engineering Experience (EngExp) platform team, you help run and evolve the platform that powers CJ's production systems across multiple AWS regions. The platform includes Kubernetes clusters, observability stack, CI/CD and artifact infrastructure, AWS networking, secrets and access systems, and cost visibility. You own reliability and operability, act as a critical reviewer, set standards, and mentor engineers." Also include work authorization? Could be in About the role or Schedule. Probably better to keep work authorization in About the role as a requirement? But it's a qualification? It's more eligibility. Could be in Qualifications? Not listed. Might be okay to include in About the role as a note. But we must not invent. We'll include: "You must be work authorized in the United States without the need for employer sponsorship." as part of About the role. Now Responsibilities list items: need to capture all bullet points. We'll break into two groups: The