Senior Software Engineer - Reliability

<h3><strong>About Us</strong></h3> <p>Nu is one of the largest digital financial platforms in the world, with more than 127 million customers across Brazil, Mexico, and Colombia. Guided by our mission to fight complexity and empower people, we are redefining financial services in Latin America and this is still just the beginning of the purple future we're building.</p> <p>Listed on the New York Stock Exchange (NYSE: NU), we combine proprietary technology, data intelligence, and an efficient operating model to deliver financial products that are simple, accessible, and human.</p> <p>Our impact has been recognized by global rankings such as Time 100 Companies, Fast Company’s Most Innovative Companies, and Forbes World’s Best Bank. Visit our institutional page <a href="https://international.nubank.com.br/careers/">https://international.nubank.com.br/careers/</a> &nbsp;</p> <h3><strong>About the role</strong></h3> <p>The U.S. Market team is launching a differentiated financial product in the largest and most demanding financial market in the world. We’re iterating quickly on real customer signals while building systems that will eventually serve customers at Nubank scale. That combination — early-stage velocity, regulatory weight, and high reliability expectations, requires an engineer whose primary mandate is reliability, scale, and operational excellence.</p> <p>This role exists to make sure the systems we’re building today can be trusted in production tomorrow, and to set the bar for what “production-ready” means on this team. The engineer in this role delivers their mandate by writing production code, shaping architecture, and engineering the systems themselves — not by absorbing operational load.</p> <h3><strong>You'll be responsible for</strong></h3> <p>Define and operate against SLOs. Establish meaningful SLIs and SLOs with product and engineering partners, manage error budgets, and use them as real inputs to prioritization rather than dashboards no one reads.</p> <ul> <li>Build the observability layer. Improve metrics, logs, traces, and alerting so issues are detected early, attributed precisely, and debugged with code-level confidence. Push instrumentation upstream into the services we own.</li> <li>Lead incident response. Act as incident commander when needed, drive blameless postmortems, and turn findings into concrete engineering work that lands. Build the muscle in the team so this isn’t centralized in any one person.</li> <li>Reduce toil through engineering. Identify repetitive operational work and eliminate it with software — automation, self-healing behavior, better defaults, better tooling — rather than absorbing it as ongoing overhead.</li> <li>Production Hardening. Stress-test designs for partial failure, dep