Site Reliability Engineer

<div> <p>Remote · Full Time · Individual Contributor · +7 Years of Experience</p> <h1>Site Reliability Engineer</h1> <h2>Who We Are</h2> <p>Yuno is the AI-native operating system of global commerce, powering the financial infrastructure of enterprise merchants, banks, and wallets. Through a single API, Yuno connects them to pay-ins, payouts, fraud prevention, KYC/KYB, and stablecoins globally, so they can operate everywhere. Agnostic by design and connected to 1,000+ payment methods and 460+ integrations in 190+ countries, Yuno optimizes acceptance rates, reduces costs, and strengthens security through specialized AI agents that learn from every transaction. Global brands including McDonald's, NetEase Games, GoFundMe, and Rappi run their payments on Yuno.</p> <h2>About The Role</h2> <p>Yuno is looking for a Staff Site Reliability Engineer to set the technical direction for reliability across our infrastructure — starting with the platform that provisions, deploys, and manages AI agents at scale on AWS, the system powering payments across 190+ countries. The platform is in production and growing, and we need the most senior reliability voice in the room to evolve the architecture and make sure it stays reliable, observable, and ready to scale.</p> <p>This is not a "maintain what exists" role, and it's not a single-system role. You'll own the reliability strategy — driving architectural decisions, designing event-driven communication, defining how we measure and defend reliability, and setting the standards other engineering teams build on.</p> <h2>How AI Shows Up in This Role</h2> <ul> <li> <p>The platform you own is Yuno's AI agent infrastructure — provisioning and deploying AI agents at scale, plus the agents that route payments and prevent fraud. Keeping the AI-native layer reliable is the core of the role</p> </li> <li> <p>AI is our default execution layer: you're encouraged to use AI-assisted tooling across automation, runbooks, incident analysis, and root-cause investigations, and to help define how the wider engineering org adopts it. We care how you use it, not whether you do</p> </li> </ul> <h2>Your Contribution Will Be</h2> <ul> <li> <p><strong>Reliability strategy and standards</strong> — define the SLO culture, error-budget policy, and incident practices that scale across engineering teams, turning reliability from firefighting into a measurable, org-wide discipline</p> </li> <li> <p><strong>Platform architecture and evolution</strong> — drive architectural decisions as the platform matures; the deciding voice on choosing technologies, designing systems, and when to evolve the infrastructure</p> </li> <li> <p><strong>Messaging and event-driven architecture</strong> — design and own the messaging layer for inter-service communication, replacing synchronous patterns with durable, reliable async messaging</p> </li> <li> <p><strong>Infrastructure and deployment</strong> — own the cloud infrastructure, automate provisioning with IaC, and ensure the platform scales reliably as transaction volume grows</p> </li> <li> <p><strong>Observability</strong> — build the monitoring, tracing, and alerting that keeps the platform healthy; when something breaks at 3am, your dashboards and alerts should explain why before anyone has to dig</p> </li> <li> <p><strong>Incident leadership and mentorship</strong> — act as the senior escalation point for the hardest production problems, run blameless postmortems and root-cause analyses that turn into permanent fixes, and raise the reliability bar by mentoring senior and mid-level engineers</p> </li> <li> <p><strong>Chaos engineering mindset </strong>— continuous fault injection and resilience experiments that surface weaknesses before they turn into incidents, plus identifying and proposing resilience patterns to prevent those failures from reaching production.</p> </li> </ul> <h2>What Success Looks Like</h2> <p>Within your first 6–12 months, you've set the reliability strategy for the platform, driven at least one major architectural evolution (event-driven messaging, streaming reliability, or observability), and engineering teams have adopted the SLO and error-budget framework you defined. You're the person Yuno trusts with the hardest reliability calls.</p> <h2>Skills You Need</h2> <h3>Minimum Qualifications</h3> <ul> <li> <p>Event-driven architecture and messaging systems — you've designed and owned systems around message queues (Kafka, NATS, RabbitMQ) and understand at-least-once delivery, consumer groups, dead letters, and backpressure; you've migrated a system from synchronous to async</p> </li> <li> <p>Deep AWS — EC2, VPC, IAM, S3, and RDS — with strong networking fundamentals, since inter-service communication runs over the internal VPC</p> </li> <li> <p>Infrastructure as Code — Terraform or Pulumi, reviewed in PRs rather than clicked in consoles</p> </li> <li> <p>Kubernetes and Docker in production — container lifecycle, resource limits, health checks, and orchestration at scale</p> </li> <li> <p>Observability and SLOs — Datadog fluency or equivalent (dashboards, monitors, APM, distributed tracing), and a track record defining and operating SLOs, SLIs, and error budgets across services</p> </li> <li> <p>Chaos engineering and resilience testing — hands-on experience with fault injection, game days, or chaos experiments (Gremlin, Chaos Mesh, AWS FIS, or similar) to harden production systems</p> </li> <li> <p>Distributed systems debugging — you've diagnosed async flows and cascading failures in production and can explain what broke and how you fixed it; comfortable coding for automation and tooling (Go, Python, or similar)</p> </li> <li> <p>Databases — solid SQL (PostgreSQL) and NoSQL (MongoDB, Redis): when to use each, indexing, replication, and performance tuning</p> </li> <li> <p>Proven technical leadership — you've set reliability standards, influenced architecture across teams, and mentored engineers, not just owned your own scope</p> </li> <li> <p>English — advanced proficiency, written and spoken</p> </li> </ul> <h3>Preferred Qualifications</h3> <ul> <li> <p>AI / MLOps infrastructure — running AI workloads in production (model serving, LLM inference, GPU/resource management, and agent evaluation/observability tools like LangFuse, LangSmith, Braintrust, or MLflow)</p> </li> <li> <p>Multi-tenant container platforms — running customer or user workloads in containers (Replit, Railway, Fly.io, or internal PaaS)</p> </li> <li> <p>Data pipelines and orchestration — Airflow, Prefect, or similar; data warehouses like Databricks, Snowflake, or BigQuery a plus</p> </li> <li> <p>Incident management and on-call tooling — PagerDuty, Opsgenie, or incident.io</p> </li> <li> <p>Experience in the payments industry</p> </li> </ul> <h3>Nice to Have</h3> <ul> <li> <p>ECS experience</p> </li> <li> <p>s6-overlay for container process supervision</p> </li> <li> <p>Experience with AI agent framework ecosystems</p> </li> <li> <p>Spanish proficiency</p> </li> </ul> <h2>What We Offer at Yuno</h2> <ul> <li> <p>Competitive Compensation</p> </li> <li> <p>Remote Work — you can work from everywhere</p> </li> <li> <p>Home Office Bonus — a one-time allowance to set up your ideal home office</p> </li> <li> <p>Work Equipment</p> </li> <li> <p>Stock Options</p> </li> <li> <p>Health Plan wherever you are</p> </li> <li> <p>Flexible Days Off</p> </li> <li> <p>Language, Professional, and Personal Growth courses</p> </li> </ul> <h2>Disclaimer</h2> <p>We may use artificial intelligence (AI) tools to support parts of the hiring process, such as reviewing applications, analyzing resumes, or assessing responses. These tools assist our recruitment team but do not replace human judgment. Final hiring decisions are ultimately made by humans. If you would like more information about how your data is processed or wish to exercise your data protection rights, please contact us at <a href="mailto:hiring@y.uno">hiring@y.uno</a>.</p> </div>