Senior Software Engineer, Payabli

• We're looking for someone who meets the minimum requirements below. If you meet them, we encourage you to apply. Your skills and trajectory matter more than checking every box
• 5+ years of professional infrastructure or platform engineering experience. You've built and operated production AWS environments that serve real traffic at scale—not just spun up sandbox accounts
• Deep AWS expertise. You think natively in AWS services (ECS/EKS, RDS, Lambda, VPC, IAM, CloudFormation/CDK/Terraform) and understand the trade-offs between them. You've made architectural bets and lived with the consequences
• Strong CI/CD experience. You've designed and maintained deployment pipelines (GitHub Actions, GitLab CI, Jenkins, or similar) that teams actually trust and rely on. You understand the difference between a pipeline that exists and one that accelerates the business
• Infrastructure-as-code fluency. You define infrastructure declaratively, version it, review it, and deploy it the same way you would application code
• Security-minded by default. You understand network segmentation, least-privilege access, secrets management, and encryption at rest and in transit—especially in environments handling financial data
• Proactive and opinionated. You don't wait for someone to file a ticket. You see what's broken or missing, propose a path forward, and drive it. You bring a point of view about how infrastructure should work and can back it up
• Strong communicator. You can translate infrastructure decisions into business impact for engineering leadership, and explain complex systems clearly to engineers who aren't infrastructure specialists
• Background with observability stacks (Datadog, Grafana, CloudWatch, OpenTelemetry) and on-call/incident response processes

Desirable

• As a Senior Software Engineer, Platform at Payabli, you'll own the infrastructure and developer experience that every engineer at the company builds on top of
• You won't be handed a task list—you'll define the vision for how we build, test, deploy, and operate our platform on AWS, then execute against it
• From CI/CD pipelines and infrastructure-as-code to local development and Cloud/Agent development environments, you'll be the person who makes every other engineer faster, safer, and more productive
• This is a high-ownership role
• We're looking for someone who sees a gap, builds a plan, and drives it forward—not someone who waits to be told what's next
• Own the infrastructure. Design, build, and operate Payabli's cloud infrastructure. You'll make the architectural decisions around networking, compute, storage, and security that determine how our platform scales, performs, and stays resilient as transaction volume grows
• Build the deployment backbone. Own and evolve our CI/CD pipelines end-to-end. Every push to production should be fast, safe, and repeatable. You'll design the release process that lets engineers ship with confidence—automated testing, staged rollouts, rollback strategies, and deployment observability baked in
• Make local development exceptional. Engineers should be able to clone a repo and be productive in minutes, not days. You'll own the local development experience and make sure it mirrors production closely enough to catch real problems early
• Enable AI-assisted development. As the team adopts AI coding agents and assistants, you'll build the environments that let engineers leverage these tools safely and effectively within a PCI-compliant infrastructure
• Define and drive the platform roadmap. Assess where we are, define where we need to be, and build the plan to get there. You'll partner with engineering leadership to prioritize infrastructure investments and communicate the "why" behind them
• Harden everything. Infrastructure in payments means PCI-DSS scoping, network segmentation, secrets management, access controls, and audit trails are your daily work. You'll ensure our infrastructure posture keeps pace with compliance requirements as we scale
• Instrument and observe. Build the monitoring, alerting, and observability stack that gives the team real-time visibility into system health. When something goes wrong at 2 AM, the infrastructure should tell us what happened before we have to ask
• Multiply the team. Document patterns, write runbooks, and establish infrastructure standards that make the entire engineering organization more self-sufficient. The best platform engineering is invisible—things just work