DevOps Infra Lead

#### **🌍 Our Vision & Mission** At Payflows, we give finance teams the tools to reclaim their time and energy. Our platform weaves together banking connectivity, payments, AI, and procurement so they can ditch the busywork and focus on what really moves the needle. #### **🤝 Why Join Us?** We’re a small, mighty team who’ve earned our stripes at Airbnb, Luko, BNP Paribas, and Facebook. It’s not always easy—things move fast, and we expect a lot—but if you’re hungry for impact, you’ll find it here. 🛠️ We’re builders at heart. We move fast, think deeply, ship often — and we’re always hungry to learn more. You'll collaborate closely with product and tech to craft elegant backend systems that scale as fast as we do. #### **🚀 What You’ll Do** You'll own the infrastructure for a product that real finance teams rely on every day. For us, infrastructure is not just about uptime; it's about reliability, security, and trust - especially when money and automation are involved. The platform has to be boring in the best possible way: predictable, observable, and safe to deploy to. * In a typical week, you might: * Evolve our infrastructure-as-code to add a service, a queue, or a whole new environment. * Improve our CI/CD pipelines so engineers ship safely and fast, dozens of times a day. * Investigate a production issue: a latency spike, a failing deploy, a database under load. * Strengthen observability with dashboards, alerts, and traces, so we catch problems before customers do. * Harden our security, secrets management, and access controls. * Tune cost and performance across our AWS footprint. Your time will be split between **building new platform capabilities** and **making what already exists more reliable**. Both matter. You'll help shape the **foundation** that everything else stands on: the pipelines, environments, and guardrails that let engineers and our AI agents act safely in production. You'll work closely with backend, frontend, and the AI team. We expect you to take ownership of the platform and make it more reliable over time, not wait for tickets. #### **💻 Our current tech reality** Our stack evolves based on our challenges, but we care more about good design than trendy tools We're an AWS shop, and we lean on managed services and infrastructure-as-code so the system is reproducible and easy to reason with. A growing part of our world is making the backend a set of reliable, deterministic tools that AI agents can call, which raises the bar on reliability even further. * **Cloud:** AWS * **Infra-as-code:** Pulumi (Python) * **Compute:** ECS + Lambda, serverless when it makes sense * **Data:** PostgreSQL on RDS/Aurora * **CI/CD:** GitLab CI * **Orchestration:** Airflow (MWAA) * **Observability:** Grafana Cloud, CloudWatch, Sentry * **Auth & identity:** Cognito, IAM * **Edge & frontend:** API Gateway, ALB, AWS Amplify for the web app Some of this is clean, version-controlled, and reproducible. Other parts grew fast and live a little too much in people’s heads instead of in code. Closing that gap is a big part of why this role exists. Over the next year, we'll focus on: * Making every environment reproducible from code * Better observability and alerting, fewer surprises * Tightening the security and compliance posture that comes with handling enterprise finance data * Faster, safer deploys * Keeping AWS costs sane as we scale