Senior Software Engineer, Platform

We need to output HTML fragment with sections: h3 headings for sections present: About the role? Actually we have Overview, Responsibilities, Technologies We Use, Qualifications, Additional Information (benefits?), Compensation Range (Pay). Also maybe "Company Description" but we should not repeat job title. We need to include sections only when posting has real specific content. We need to preserve all substantive info, remove boilerplate like EEO, legal, accommodation contact, etc. Also remove duplicated lines. We need to 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. We must not repeat job title as heading. No Job ID etc. We need to decide which sections to include: Overview (maybe "About the role")? The posting includes "Overview" paragraph about work auth and hybrid. Could be "About the role". Also "Responsibilities" present. "Technologies We Use" could be "Skills" or maybe "Technologies". The instruction says use headings like Skills, Benefits, Pay, Schedule. But we can also use other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. So we can map: - Overview -> About the role (h3) - Responsibilities -> Responsibilities (h3) - Technologies We Use -> Skills (h3) (list of technologies) - Qualifications -> Qualifications (h3) (list) - Additional Information includes benefits description: flexible time off, holidays, etc. That's Benefits (h3) - Compensation Range -> Pay (h3) - Schedule? The posting mentions hybrid role requiring 3 days a week in office. That's schedule info. Could be Schedule (h3) or include in About the role. Since we have schedule info, we can create Schedule section. We must not create sections with filler like "commensurate with experience". We have actual content. We need to preserve all substantive info. Let's extract content. Company Description: Not needed? It's descriptive but could be part of About the role? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." Company description may be considered background; we could include in About the role as prose. But we need to preserve all substantive information. The company description is substantive but maybe not required? It's about the company, not the role. Might be okay to include in About the role. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove the accommodation contact line and EEO line. Also remove the "Compensation Range: ..."? No, we need to keep Pay. We need to keep the hybrid role requiring 3 days a week in a CJ office location (www.cj.com). That's schedule. We need to keep "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)". That's about role. We need to keep "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." etc. That's part of responsibilities? Actually it's description of role. Could be in About the role. We need to keep the bullet list under Responsibilities (the long list). We'll convert each bullet to

  . We need to keep "Technologies We Use" list. We need to keep "Qualifications" list. We need to keep "What Success Looks Like" maybe could be part of Responsibilities or Additional? It's substantive; we could include as a separate section maybe "Expectations" but not in allowed headings. Could fold into Responsibilities or Additional. Probably better to include as part of Responsibilities (since it's about outcomes). But we can also create a section "Expectations" but not in list. Safer to fold into Responsibilities as prose. We need to keep "Additional Information" which includes benefits etc. We'll extract benefits list. We need to keep "Compensation Range: USD $112,290.00 - USD $172,032.00/Annually." That's Pay. We need to keep schedule info: hybrid role requiring 3 days a week in office. We need to remove duplicated lines like "This is a hybrid role requiring 3 days a week in a CJ office location (www.cj.com)" appears twice? Actually appears in Overview and Additional Information. We'll keep once. Now craft HTML. Structure:

  About the role

  Company description paragraph(s) plus overview.

  We need to include company description: "Welcome to Our World We’ve been leading the charge..." etc. That's long. We'll include as prose. Then responsibilities:

  Responsibilities

  ...

  Then Skills:

  Skills

  ...

  (list technologies) Then Qualifications:

  Qualifications

  ...

  Then Benefits:

  Benefits

  ...

  Then Pay:

  Pay

  Compensation Range: USD $112,290.00 - USD $172,032.00/Annually.

  Then Schedule:

  Schedule

  Hybrid role requiring 3 days a week in a CJ office location.

  We must ensure we don't include any boilerplate like EEO, accommodation, legal. Check for duplicated content: In Additional Information there is also "Hybrid work arrangements for optimal work-life balance" which is similar to schedule; we can keep schedule only. Now let's extract precise text. Company Description paragraph: "Welcome to Our World We’ve been leading the charge in the affiliate industry from day one—establishing performance marketing and paving the way for future innovations. We're known for maintaining one of the largest, most reliable partnership platforms with impeccable, personalized service. Founded in Santa Barbara, California in 1998, CJ (formerly Commission Junction) stands as the most trusted name in performance marketing. We specialize in building partnerships between top brands and reputable publishers to drive revenue and business growth. CJ’s industry-leading solutions make us the platform of choice for over 3,800 global brands across sectors like retail, travel, finance, technology, and home services. As part of Publicis Groupe, our savvy data capabilities, cutting-edge tech, and strategic expertise facilitate genuine connections, allowing brands to reach consumers wherever they are. A Quick Peek at Affiliate Marketing Think back to your last online purchase. Did an influencer tip you off about a great product and offer a discount? Or perhaps you relied on a trusted review site to make your decision? Whatever path you took, affiliate publishers likely played a role by influencing, informing, or helping you find the best deal. CJ connects brands with these publishers, creating valuable resources for shoppers like you." We'll keep that as prose. Overview paragraph: "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)". We'll incorporate. Then the role description: "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. "Platform" here is broad - it is the Kubernetes clusters, but also the observability stack every squad depends on, the CI/CD and artifact infrastructure their builds run through, the AWS networking that connects them, the secrets and access systems that gate them, and the cost visibility that keeps them accountable. EngExp owns all of it, and this role touches most of it. This is not just an infrastructure role - your value is in engineering judgment. 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. We especially want someone with real depth in the systems below - we have made platform decisions we later had to reverse because the team lacked deep expertise in a component we owned, and that depth is exactly what this role brings." We can include that in About the role as prose. Now Responsibilities list: The bullet points start with "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. Then "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'll combine all these into a single

  list. Now Technologies We Use list: - 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,