Senior Software Engineer (Github) - IC5 - 2026
Nubank
- Location
- São Paulo
- Employment
- Full Time
- Work model
- Remote
- Level
- Senior
- Posted
- 26d ago
Skills
About this role
About Nu Nu is the leading digital bank in Latin America, serving 135 million customers across Brazil, Mexico, and Colombia. The company has been leading an industry transformation by leveraging data and proprietary technology to develop innovative products and services. Guided by its mission to fight complexity and empower people, Nu caters to customers’ complete financial journey, promoting financial access and advancement with responsible lending and transparency. The company is powered by an efficient and scalable business model that combines low cost to serve with growing returns. Nu’s impact has been recognized in multiple awards, including Time 100 Most Influential Companies, Fast Company’s Most Innovative Companies, and Forbes World’s Best Banks. Visit our Institutional Page About the team The GitHub Governance team is one of the highest-leverage teams in ETS. It decides — and operationalizes — how ten thousand Nubankers interact with GitHub, how repositories are governed, how access is granted and revoked, how vulnerabilities are surfaced and triaged, and how the platform serves as the substrate for AI-assisted development at Nubank. The team's mandate touches every engineer in the company and every InfoSec, IAM, and Datasec partner that depends on the platform. The team is currently four people, holding the platform's active mandate: KPMG audit obligations, EMU (Enterprise Managed Users) migration, rollouts including Copilot Code Review, vibe-coding profile design, the inactivity-rule mechanism, and IP control work tied to the AI-First posture. Every GitHub change at Nubank now routes through formal change management with InfoSec.
About the role
This role is a senior individual contributor on the GitHub Governance team, sharing technical ownership of the platform's surface with the existing senior engineers. The role is hands-on and execution-heavy: shipping platform changes, building automation, partnering with InfoSec on IAM and Datasec design decisions, and contributing senior judgment to the team's most exposed work. The role operates with autonomy, owning problems end-to-end, making technical calls within their scope without waiting for direction, and knowing when to escalate versus move forward. What the person will own As a Senior Software Engineer you will work across the team's portfolio, owning the slices that fit their depth and partnering on the rest. The current portfolio includes KPMG audit response and evidence collection, EMU migration (user-profile migration is the active Wave 1, with the Identity Hub workaround as the path forward), rollouts including Copilot Code Review, vibe-coding profile work and the connected guardrails, the inactivity-rule design, and IP control mechanisms. Beyond execution, you will be a senior voice in the team's design discussions: architecture decisions, integration patterns with Identity Hub, ITSec/IAM/Datasec touchpoints, and the cross-pack discussions with Coding Tools, AI Enablement, and Enterprise Solutions. You will be one of the engineers shaping how GitHub-change governance works in practice at Nubank. This role will also serve as a technical partner in shaping the team's GitHub platform strategy, working alongside the PM to evaluate GitHub's product roadmap, anticipate how upcoming features affect Nubank's governance model.
What we are looking for
Must-have Demonstrated depth administering GitHub Enterprise at scale (10,000+ users), including EMU (Enterprise Managed Users), organization and repo-level policy design, and rulesets. Hands-on experience with GitHub Copilot administration and rollout at an organizational level. Proficiency with the GitHub API and automation via GitHub Actions, including building or maintaining CODEOWNERS structures and branch protection patterns at scale. Working knowledge of GitHub audit logs and the ability to trace a policy decision through to its downstream effects on users, repositories, audit trails, and connected