Lead Systems Engineer: Scalable Messaging & Kafka

Nubank

United States

On-site

USD 210,000 - 252,000

Full time

14 days+

Get more replies from employers

Send a job-specific resume in minutes.

Benefits offered by this job

Health Insurance

Life Insurance

Pension Plan

Extended maternity and paternity leave

Nucleo - Learning platform

NuLanguage - Language learning program

NuCare - Mental health program

Vacations

Job summary

Nubank is seeking an experienced Lead Software Engineer to evolve and operate its messaging platform and the infrastructure for asynchronous communication at scale. The role covers a large, multi-account AWS environment with Kubernetes-backed infrastructure, driving reliability and platform excellence across multiple business domains and countries.

You will own important technical problems, improve observability, and shape engineering decisions in partnership with the team.

Qualifications

Strong software engineering fundamentals and production distributed systems.
Kubernetes, networking, and AWS in large-scale environments.
Operate infrastructure-heavy platforms with high reliability.
Troubleshoot complex production issues across app, infra, network.
Improve observability, automation, and operational tooling.
Understand scalability, resilience, performance and failure isolation patterns.
Work autonomously on ambiguous technical problems and execute.
Collaborate across teams.

Responsibilities

Operate and improve large-scale messaging and platform infrastructure based on Kafka used by critical systems.
Improve reliability, scalability, and performance of asynchronous platforms.
Design and implement high-throughput, low-latency, fault-tolerant solutions.
Improve observability, automation, and operational excellence.
Support incident analysis, troubleshooting, and root cause remediation.
Optimize infrastructure usage and drive cost awareness in AWS.
Work on platform capabilities enabling safe growth in message volume, topic count, and cluster footprint.
Collaborate with engineers to evolve platform standards, tooling, and best practices.
Contribute to architectural discussions on messaging, traffic patterns, service communication, and platform reliability.