What you’ll own

Payrix is looking for a Senior Platform Engineer to help design, build, operate, and improve the cloud-native platform that Payrix engineering teams use to deliver payments capabilities safely, and at scale. This role sits inside the Payrix Platform Engineering team, which owns and enables the shared infrastructure, CI/CD, GitHub governance, infrastructure-as-code, security tooling, and developer experience patterns that Payrix services depend on across regulated PCI-DSS and SOC 2 environments within the Worldpay / Global Payments ecosystem. 

Platform Engineering & Developer Enablement 

• Build and improve Payrix’s internal platform capabilities so engineering teams can provision, deploy, observe, and operate services through clear, self-service patterns. 

• Define and maintain golden paths for new and existing Payrix services, including EKS, infrastructure-as-code, GitHub Actions, observability, tagging, secrets, access, and disaster recovery readiness. 

• Reduce friction and cognitive load for service teams by turning repeated manual steps into documented, automated, reusable workflows. 

• Create platform documentation, runbooks, examples, and implementation guidance in Confluence and code repositories so knowledge is searchable and sustainable. 

• Partner with engineering teams as an enabling platform team: teach, pair, consult, and build with teams while leaving long-term service ownership clear. 

Cloud Infrastructure, EKS & Kubernetes 

• Design, implement, and operate AWS and EKS platform foundations across Payrix environments, including cluster patterns, Kubernetes access guidance, cluster-level integrations, add-ons, node groups, ingress, certificates, secrets, runners, and shared operational guidance. 

• Contribute to multi-region and disaster recovery platform foundations, including EKS patterns, infrastructure readiness, environment consistency, and validation support. 

• Help modernize legacy and lower-environment deployment paths by enabling the move from Jenkins-based flows to GitHub Actions and standardized cloud-native delivery patterns.

• Troubleshoot complex infrastructure and platform issues across AWS, Kubernetes, CI/CD, networking, access, and runtime layers.

Infrastructure as Code & Automation 

• Build and maintain infrastructure-as-code using Terraform, Terraform Cloud, Pulumi, and supporting automation. 

• Help evolve Payrix’s IaC standards, module patterns, repository structure, stack organization, migration strategy, and governance-as-code practices. 

• Support active platform migrations, including Pulumi Cloud to S3 backend work and Terraform / Terraform Cloud patterns for non-data Payrix workloads. 

• Design automation that is repeatable, auditable, secure, and compatible with Payrix, Worldpay, and Global Payments operating requirements. 

CI/CD, GitHub Governance & Engineering Tooling 

• Improve engineering velocity and reliability through GitHub Actions, deployment automation, branch protection, repository standards, custom repository properties, service account guidance, and developer tooling improvements. 

• Partner with service teams to establish clear workflow ownership: Platform owns the enablement patterns and shared infrastructure; service teams own their application deployment workflows after handoff. 

• Support Payrix GitHub organization governance, access standardization, and repository hygiene in alignment with Entra / MyAccess / SCIM and Worldpay standards. 

• Use Jira and Confluence consistently so platform work, decisions, and operational knowledge remain visible and durable. 

Security, Compliance & Reliability 

• Build platform capabilities that satisfy PCI-DSS, SOC 2, data protection, and Worldpay landing zone expectations. 

• Support Snyk onboarding, project organization, policy and tagging conventions, and alert-routing standards while partnering with application teams on remediation ownership. 

• Contribute to observability, resiliency, performance, tagging, and cost-visibility patterns for platform-owned AWS resources. 

• Help clarify operational boundaries with SRE, Security, Identity, IX / FinOps, and mission teams through documented ownership, support paths, and escalation models. 

Technical Leadership & High-Impact Work 

• Act as a technical force multiplier: lead design discussions, write implementation plans, review infrastructure and application changes, mentor engineers, and unblock teams. 

• Step into ambiguous or cross-cutting problem spaces and drive them toward clear architecture, delivery plans, ownership, and documentation. 

• Contribute to platform roadmap execution across initiatives such as AWS account migration, disaster recovery, EKS standardization, lower-environment deployment modernization, Pulumi / Terraform evolution, Snyk enablement, GitHub governance, and Worldpay integration. 

• Balance architectural thinking with practical hands-on delivery; this role is not purely advisory. 

What you’ll bring   

• Senior-level experience in platform engineering, cloud infrastructure, DevOps, SRE, infrastructure engineering, or a similar hands-on role. 

• 5+ years' overall experience with cloud infrastructure (DevOps, SRE and/or Platform Engineering) 

• Strong production experience with AWS and cloud-native infrastructure. 

• Hands-on experience with Kubernetes, preferably Amazon EKS, including cluster operations, access patterns, add-ons, ingress, secrets, workload deployment, and troubleshooting. 

• Strong infrastructure-as-code experience with Terraform, Pulumi, or similar tools. 

• Experience designing and improving CI/CD pipelines and deployment automation, ideally with GitHub Actions. 

• Experience with GitHub administration or governance concepts such as repository standards, branch protection, rulesets, service accounts, access models, and organization-level hygiene. 

• Working knowledge of observability, reliability, resiliency patterns, incident troubleshooting, and operational support in distributed systems. 

• Experience operating in regulated, security-conscious environments; PCI-DSS, SOC 2, financial systems, or payments experience is strongly valuable. 

• Ability to work across application, infrastructure, platform, security, and operations boundaries without losing sight of accountable ownership. 

• Excellent written and verbal communication, including the ability to document decisions, explain tradeoffs, influence without direct authority, and keep work visible in Jira and Confluence.   

It’s a bonus if you have

• Experience building or operating payments platforms, transaction-processing systems, or other high-availability financial technology systems.

• Familiarity with merchant onboarding, authorization, settlement, funding, risk, underwriting, processor integrations, or payment lifecycle concepts.

• Experience with Snyk, Datadog, CloudZero, Entra / Active Directory, MyAccess, AWS VPN, Linux host access, Ansible, or similar enterprise platform tooling.

• Experience with disaster recovery, multi-region platform patterns, service inventory, RTO / RPO planning, and validation exercises.

• Experience working in SAFe / Agile environments, PI planning, sprint planning, backlog refinement, and cross-team dependency management.

• Familiarity with internal developer platforms, platform-as-a-product practices, CNCF cloud-native patterns, Team Topologies concepts, and developer experience measurement.

• Experience mentoring engineers or leading technical efforts as a senior, staff, principal, architect, or senior IC contributor. 

About the team 

Our inclusive and global teams win together every day. We’re proud to have the best minds in the industry, who you can learn from as you grow your career. The people, the energy, the connections– it’s unmatched. Come and be part of an ever-evolving company and get dynamic opportunities that go beyond borders.  

How Our Team Works: 

• Team first: We help teammates before taking on new work. We value accountability, follow-through, and active participation in team ceremonies. 

• Public, searchable communication: Slack is our primary async tool. We use threads and public team channels instead of hidden DMs whenever possible, so knowledge is shared and support load is visible. 

• Visible work: We track work in Jira. Work that is not tracked gets lost, cannot be prioritized, and creates hidden load. 

• Documentation as part of delivery: Platform work is not done until the usage guidance, operational notes, decisions, and ownership model are documented. 

• Respect for distributed work: The team spans time zones. Core overlapping hours are 10:00 AM – 5:00 PM ET, and we communicate absences, agendas, and schedule constraints clearly. 

• Ownership clarity:</