Lead Software Engineer (Cloud Network)

ABOUT NU

Nu serves more than 140 million customers, guided by a mission to fight complexity and empower people. The company has been leading an industry transformation through innovative products and human-centered services.

Proprietary technology and data at scale power Nu’s digital platform, built to promote financial access, advancement, and transparency. Its business model thrives on customer love and lower costs, feeding a flywheel of growth and profitability.

Visit our Institutional Page https://www.nu.com/2026-en

ABOUT THE ROLE

Every transaction at Nubank travels across a network before it reaches a customer. As we grow across countries, accounts, regions and hybrid environments, the connectivity layer underneath has to stay fast, segmented, auditable and cheap to run — while never becoming the thing that takes the platform down.

As a Lead Software Engineer on a Cloud Network platform engineering team, you set and evolve the technical direction for how Nubank connects its cloud, hybrid and on-premises environments. You own problems whose scope spreads across several teams and business units, and you are expected to bring structure to ambiguity rather than wait for it to be resolved for you.

This is an IC6 role: you lead through technical depth, design authority and influence rather than direct reports. The goal you own is a cloud network platform that scales with the business, holds up under audit, and gets simpler over time instead of more complex.

YOU'LL BE RESPONSIBLE FOR

• Setting and evolving the technical direction of the cloud network platform owned by your team, aligning with Nubank's canonical approaches and contributing back to the broader technical community.

• Leading high-level and low-level design for connectivity patterns across multi-account, multi-region, multi-geo and hybrid-cloud topologies, independently making sound architectural decisions in multi-component, multi-team designs.

• Managing complex network projects and processes end to end — working independently, coordinating across subjects and stakeholders, and escalating for managerial support in a timely way rather than reactively.

• Proactively reducing long-term complexity through simplification, consolidation, deprecation and paved roads, explicitly balancing scalability, maintainability and cost, and considering both human and AI interaction with the platform.

• Owning the operational health of the network platform in your team's scope: leading complex incident response (diagnosis, coordination, resolution), driving complex postmortems, and owning the short- and long-term tech debt strategy that comes out of them.

• Promoting a culture of safe change — feature flags, gradual rollout, monitoring, fast rollback — applied to network changes, and driving simplification and cost optimization across the topology.

• Setting and enforcing quality standards for the team's automation and infrastructure code: testing practices, code review bar, reusable modules, and anticipation of quality and maintainability needs coming from business strategy.

• Defining observability for the platform — robust monitoring, controls and SLAs that surface issues proactively rather than after customer impact.

• Bringing a strong end-to-end domain understanding: tracing a business process from product through the transactional path down to the network and data layers, and understanding how network design choices propagate through it.

• Owning the network security posture of your scope, including PCI DSS or equivalent standards, segmentation, and controls that hold up under audit.

• Evaluating buy vs. build options and new products and technologies, being data-driven about stability, reliability, scalability and cost before committing to a solution.

• Mentoring IC4/IC5 engineers on the broader system landscape, design reasoning and operational practice, and raising the bar of the people around you.

• Participating in hiring as a core pa