Senior Engineer, DevOps/Platform Reliability

We need to output HTML fragment with sections: About the role, Responsibilities (maybe from bullet list), Requirements (maybe Required Qualifications), Qualifications (maybe Preferred Qualifications), Benefits (What We Offer), maybe Pay? The posting mentions compensation package includes competitive salary and bonus plan, but no specific numbers. The rule: do NOT create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation package includes competitive salary and bonus plan, vacation, sick, personal time off policies, generous 401K match, strong healthcare benefits. That's benefits. So we can include Benefits section. Pay: they mention competitive salary and bonus plan but not specific numbers; still it's stating compensation. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation package includes competitive salary and bonus plan. So we could include Pay section? Might be considered stating compensation. However they also list benefits. The instruction: "Prefer a few substantive sections over many thin ones." Could combine Pay and Benefits into one Benefits section? But they said use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include Benefits and maybe Pay if we have content. Since they mention competitive salary and bonus plan, we could put that in Pay. Benefits: vacation, sick, personal time off, 401K match, healthcare. We'll create both. We need to remove boilerplate: EEO, equal opportunity, etc. Also remove navigation, cookie, legal, application instructions. Also remove duplicated lines. We need to preserve all substantive information. Let's extract content. First, "About PayCargo" paragraph: description of company. Should we include? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must include About the company. But we could include as a

before sections? The page already shows job title; we should not repeat job title as heading. The "About PayCargo" is not a heading per list, but we could keep as a paragraph before sections. The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." So we can include a

about PayCargo. Then "About The Role" heading: we should use

About The Role

and then prose. Then responsibilities: The bullet list under "As The Senior Engineer, DevOps/Platform Reliability, You Will" with subheadings: Infrastructure & Platform Modernization, CI/CD & Release Engineering, Observability & Reliability, Secure AI Platform Support, Cross-Functional Partnership. Each has bullet points. We need to turn these into

• . The subheadings could be maybe

  ? Not allowed; only headings listed are those specific. But we could keep subheadings as or just include as part of li? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

  for section headings (e.g...). It might be okay to use other headings for subsections, but safer to not add extra headings; we can just treat each bullet group as a

  with preceding

  describing the category. However we need to preserve all substantive information; we can keep the subheadings as inside

  or as part of li. Simplify: We'll create a

  Responsibilities

  then a
  with all responsibilities items (including the subcategory details). Could flatten. Similarly, Required Qualifications: list of qualifications. We'll put under

  Required Qualifications

  with
  . Preferred Qualifications: under

  Preferred Qualifications

  with
  . Experience And Education: seems duplicate of Required Qualifications? Actually it's similar. We'll treat as part of Required Qualifications maybe. But we need to preserve all info; we can combine. "You Will Likely Succeed If": could be Skills or Attributes. Could be under

  Skills

  or

  Qualifications

  . We'll put under

  Skills

  . "What Success Looks Like": could be under

  Responsibilities

  or maybe separate. We'll treat as part of Responsibilities or maybe as a separate section "Expectations". But not in list. Could add as

  Success Metrics

  but not allowed. Better to incorporate into Responsibilities. "What We Offer": Benefits section. We need to remove boilerplate: EEO statement, equal opportunity, etc. Now craft HTML. Let's extract paragraphs. About PayCargo: "Millions of shipments with goods and materials move around the world daily, by land, sea, or air. PayCargo is the world's leading online payment solution that is revolutionizing the shipping and cargo world. With a fast and efficient way to reduce costs associated with payment processing, we help improve the speed and profitability of our customers' businesses. PayCargo's platform connects payers and vendors across the cargo and logistics ecosystem, supporting payments, remittance data, integrations, vendor release workflows, and customer-facing digital experiences." We'll put that as a

  . About The Role: The paragraph after "About The Role": "The Senior Engineer, DevOps/Platform Reliability is responsible for building and operating the infrastructure, pipelines, and platform standards that keep PayCargo's global payments platform reliable, observable, and supportable. The role spans the full platform — EC2-based services, scheduled jobs, and file processing alongside containerized (ECS/Fargate) and serverless (Lambda) workloads — across a multi-account AWS environment, Terraform, and a GitHub and ZenHub workflow that ships through GitHub Actions and GitHub OIDC, with a focus on modernizing how PayCargo builds, deploys, and runs software. As one example, PayCargo's SFTP runs on AWS Transfer Family with a Lambda identity provider. This is a hands-on individual contributor role. The Senior Engineer, DevOps/Platform Reliability modernizes legacy scheduled jobs and file processes into containerized, observable services, codifies infrastructure as repeatable Terraform patterns, and creates standards that other developers can follow without depending on a single person for every implementation. The role requires strong judgment, strong follow-through, and a focus on reducing reactive fire drills and single points of failure. Working within PayCargo's DevSecOps model, the Senior Engineer, DevOps/Platform Reliability partners closely with Security, Engineering, Architecture, Product, Support, and executive stakeholders to deliver scalable, secure, and repeatable platform execution. This position has no direct reports. The role leads indirectly by defining infrastructure and deployment standards, guiding engineers toward repeatable patterns, and reducing single points of failure across the platform." We'll put that as

  under

  About The Role

  . Now responsibilities: The list under "As The Senior Engineer, DevOps/Platform Reliability, You Will". We'll extract each bullet. Infrastructure & Platform Modernization: - Modernize legacy scheduled jobs, cron scripts, and file processes into containerized (ECS/Fargate), observable, supportable services - Build and maintain infrastructure patterns in Terraform, with reusable modules, remote state, and plan/apply through CI - Standardize environment configuration, secrets management (Secrets Manager and SSM Parameter Store), and repeatable deployment paths across environments and accounts - Create platform standards that other developers can follow without depending on DevOps for every implementation CI/CD & Release Engineering: - Build, maintain, and harden CI/CD pipelines integrated with GitHub and ZenHub, with deployments authenticated through GitHub OIDC to eliminate static cloud credentials - Improve build, test, and deployment automation to make releases faster, safer, and more repeatable - Establish rollback, promotion, and environment-promotion practices that reduce release risk - Embed security and quality gates into pipelines in partnership with Security and Engineering Observability & Reliability: - Implement and maintain monitoring, logging, and alerting using CloudWatch, SNS, and Sentry, with log analytics through Athena and Glue - Improve telemetry, dashboards, and on-call workflows (PagerDuty) so issues are detected and resolved quickly - Support disaster recovery, backup, and failover patterns across regions and accounts - Lead incident response and root cause analysis with clear, durable follow-up Secure AI Platform Support: - Support the infrastructure for a contained AI platform, including whitelisted egress and approved deployment paths - Help operationalize controls such as stateless model access and bounded environments in partnership with Security and Architecture - Build deployment and monitoring patterns for AI-assisted applications so they are observable and supportable Cross-Functional Partnership: - Partner with Security to embed controls into pipelines, environments, and infrastructure-as-code, including OIDC roles, least privilege, mTLS, and Tailscale-based access - Work with Engineering and Architecture to translate designs into runnable, supportable infrastructure - Advise Product and Support on operational realities, trade-offs, and delivery risk - Implement and operate the infrastructure, pipelines, and environments according to the standards and architecture owned by the VP, Infrastructure & Security - Provide clear status, escalate risks early, and document infrastructure, pipelines, and runbooks We'll put all these under

  Responsibilities

  with a
  • each. Now Required Qualifications: list: - 5+ years of hands-on DevOps, platform, or infrastructure engineering experience preferred - Strong experience with AWS (ECS/Fargate, Lambda, VPC, IAM), and working knowledge of Azure or Entra ID - Hands-on experience with infrastructure-as-code using Terraform, including reusable modules, remote state, and plan/apply in CI - Strong experience with Docker and container orchestration such as ECS/Fargate and ECR - Experience building and maintaining CI/CD pipelines, preferably with GitHub Actions, including OIDC-based cloud authentication - Experience with monitoring and observability tooling such as CloudWatch, SNS, Sentry, and Athena/Glue - Strong understanding of secrets management (Secrets Manager, SSM Parameter Store), environment configuration, and secure deployment - Strong troubleshooting, incident response, and root cause analysis skills - Ability to create repeatable standards and documentation that reduce single points of failure Also Experience And Education: - Bachelor's degree in Computer Science, Information Technology, Engineering, or a related field, or equivalent practical experience - 5+ years of hands-on DevOps, platform, or infrastructure engineering experience preferred (duplicate) - Demonstrated experience operating production infrastructure and CI/CD in cloud environments - Experience with containerization, infrastructure-as-code, and observability tooling - Payments, fintech, SaaS, or logistics experience is a plus We can combine these into Required Qualifications (maybe split into Required and Preferred). But we already have Preferred Qualifications section later. Let's treat Required Qualifications as the first list (the bullet list under "Required Qualifications"). Then "Experience And Education" could be considered part of Required Qualifications as well, but we could put under

    Qualifications

    maybe. However we have separate "Preferred Qualifications". We'll put "Experience And Education" under

    Qualifications

    (though not in list). But the instruction says use headings like Qualifications. We'll use

    Qualifications

    for that. Preferred Qualifications list: - Experience modernizing legacy scheduled jobs and file-processing workloads into containerized services - Experience operating both EC2-based services and containerized or serverless workloads - Experience with disaster recovery, multi-region (us-east-1 / ap-east-1) redundancy, and failover design - Familiarity with secure AI/LLM platform patterns, whitelisted egress,