Senior Staff Software Engineer - Developer Experience
Base Career · Palo Alto, CA · 4 wk ago
Information TechnologyFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID. Remove boilerplate.
We need to parse the posting.
Content:
- About Nu (company description) maybe not needed as heading? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include sections only if posting has real specific content for them.
We have "About the role" section: after "About Nu" there is "About the role". So we can have
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include sections only if posting has real specific content for them.
We have "About the role" section: after "About Nu" there is "About the role". So we can have About the role
with paragraph(s) describing role.
Then "Core Responsibilities" maybe map to Responsibilities heading. So Responsibilities
with list.
Then "Key Business & Engineering Metrics You Will Influence" maybe could be considered part of Responsibilities or maybe separate? Not a standard heading; but we could incorporate into Responsibilities or maybe a separate section like "Metrics". Not in allowed list. Probably we should not create extra headings; we can embed within Responsibilities as prose.
Then "Challenges and Opportunities (What You’ll Own)" maybe also part of Responsibilities.
Then "Core Qualifications (What We're Looking For)" map to Qualifications heading. Also "Core Qualifications" includes Senior IC Leadership Track Record etc. Could also include Requirements? There's no separate Requirements section; but we could treat Qualifications as Requirements. The instruction: use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Qualifications content. We may not have separate Skills; maybe we can embed skills within Qualifications. But we could create a Skills heading if there is explicit skill list. Not really.
We have Benefits: list after "Work Setup". So we can have Benefits
with - items.
Pay: Not mentioned. So we should NOT include Pay heading.
Schedule: There's "Work model Hybrid / On-Site Office requirement 2 days per week at the office." That's schedule info. So we can include
Schedule
with paragraph.
Also maybe "About Nu" could be considered "About the role"? Already have About the role. The company description maybe not needed as a heading; but we could include as part of About the role paragraph.
We must not include boilerplate like recruitment process AI etc. Remove that.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details.
Let's extract content.
About Nu paragraph: "Nu is the leading digital bank in Latin America, serving 140 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."
We can include that in About the role paragraph maybe preceding role description.
About the role paragraph: "We are looking for a Senior Staff Software Engineer to drive the overarching strategy, technical vision, and execution across Nubank’s Quality & Developer Experience ecosystem. You will sit at the epicenter of our engineering transformation. This role goes far beyond traditional quality assurance or testing; you will own the end-to-end (E2E) Developer Experience (DevEx) across the entire Software Development Life Cycle (SDLC). From internal developer platform tools and boundary APIs to our suite of testing mechanisms and automated code reviews, your mission will be to architect AI-native systems that drastically reduce review latency, guarantee architectural correctness, and double engineering productivity across Nubank. Working alongside our most tenured engineering leaders and reporting into platform leadership, you will serve as the technical authority who brings fresh, market-leading perspectives from high-velocity environments to elevate our foundational standards."
Then maybe include Mission paragraph: "Mission Architect, scale, and operationalize an AI-transformed Developer Experience & Quality strategy so that: ..." This is a list of bullet points? It's a colon then bullet list with dash? Actually it's sentences with colon and then bullet-like items each starting with a bold phrase? In text: "Mission Architect, scale, and operationalize an AI-transformed Developer Experience & Quality strategy so that: The "Secure and Quality Path" is the Default: Automated mechanisms, linting, and smart context-aware agents enforce strict architectural standards, eliminating code quality degradation caused by high-volume AI code generation. Developer Velocity Doubles (2x): The friction in review latency, pull request (PR) approvals, and continuous integration is systematically dismantled, enabling thousands of engineers to ship features safely to 140M+ customers at unprecedented speeds. SDLC is Re-imagined for AI: Foundational tools across code authorship, testing, boundary APIs, and PR reviews are seamlessly integrated with state-of-the-art AI frameworks, smart LLM evaluations, and context-engineering hooks. Automated Approval Standards are Built: Clear deterministic checks and intelligent human-in-the-loop triggers are established to achieve safe, automated PR approvals without manual bottlenecks."
We could format as - each bullet.
Then Core Responsibilities: list.
Let's extract responsibilities bullet points:
- Architect E2E Quality & DevEx Platforms: Define and evolve the multi-year vision for our developer tooling ecosystem—covering internal developer platforms, boundary APIs, test automation suites, and pull request review systems.
- Lead the AI-Driven Code Review Evolution: Architect automated review mechanisms that leverage multi-model evaluations (e.g., using specialized LLMs to audit generated code), custom IDE/GitHub plugins, and deterministic linting to accelerate PR merge times while preventing code bloat or quality degradation.
- Define Human-in-the-Loop Boundaries: Set company-wide paradigms for when code changes can be automatically approved and merged versus when human intervention or secondary AI audits are required.
- Partner & Mentor Across Engineering: Act as a force multiplier by partnering with engineers and product managers, elevating the technical bar and instilling modern, high-velocity DevEx practices.
- Balance AI Speed with System Integrity: Establish observability, defect-tracking metrics, and safety rails to ensure that rapid AI-assisted development does not introduce structural fragility into Nubank's core services.
- Influence Build vs. Buy Strategy: Evaluate top-tier market tools, AI coding frameworks, and internal platforms to decide when to build bespoke internal agents or integrate emerging third-party tooling.
Then Key Business & Engineering Metrics You Will Influence: list:
- Developer Productivity & Velocity: Achieve a 2x improvement in overall engineering productivity across Nubank's engineering organization.
- PR Review Latency: Direct reduction in time-to-merge for pull requests across all BUs and countries.
- Code Base Health & Quality: Zero degradation in code quality and zero increase in system defects despite exponentially higher volumes of AI-generated code.
- Automated PR Approvals: Increase in the percentage of routine, low-risk code changes safely approved and merged via automated mechanisms.
- Platform Adoption & Satisfaction: High adoption and developer satisfaction (CSAT) across proprietary internal DevEx tools and boundary APIs.
Then Challenges and Opportunities (What You’ll Own): list:
- Navigating Scale: Every change you introduce to the SDLC impacts thousands of microservices and hundreds of engineering teams delivering features to over 140 million users.
- Tackling "Code Slop" at the Root: As AI agents generate code faster than humans can read it, you will solve one of the industry's newest and hardest problems: keeping codebase quality high without slowing down the team.
- High Autonomy & Strategic Breadth: You will operate with autonomy, driving horizontal technical alignment without needing micro-oversight, helping lead our joint DevEx technical council.
Then Core Qualifications (What We're Looking For): list:
- Senior IC Leadership Track Record: backend software engineering experience, with a proven track record designing developer platforms, core infra, or DevEx systems at high scale.
- Deep DevEx & SDLC Expertise: Extensive domain depth in code review systems, test automation platforms, CI/CD pipelines, developer platforms, or static analysis tools built for massive engineering organizations.
- AI Transformation & Tooling Experience: Direct hands-on experience or deep technical familiarity with AI-assisted software development—including LLM evaluation pipelines, GitHub Copilot/agent integrations, prompt/context/graph engineering, or AI-driven code review frameworks.
- Autonomous & Opinionated Technical Leader: Demonstrable history of driving technical strategy independently, navigating ambiguity, and bringing strong, battle-tested opinions on "what good looks like" in modern software development.
- High-Velocity Culture Fit: Experience operating in fast-moving, high-bar environments (e.g., top-tier tech firms, high-growth AI/DevEx startups, or elite AI labs) where speed of execution and technical rigor are equally valued.
Then Work Setup: "Work model Hybrid / On-Site Office requirement 2 days per week at the office."
Then Benefits list:
- Opportunity of earning equity at Nu (RSUs as a public company)
- Medical, Dental, and Vision Insurance
- Life Insurance and AD&D
- Extended maternity and paternity leaves
- Nucleo - Our learning platform of courses
- NuLanguage - Our language learning program
- NuCare - Our mental health and wellness assistance program
- 401K
- Health Savings Account and Flexible Spending Account
- Work-from-home allowance
- Relocation assistance package
We should not include the recruitment process AI note.
Now produce HTML.
We need sections: About the role, Responsibilities, Qualifications, Benefits, Schedule. Possibly also include a section for "Metrics"? Not in allowed headings; but we could incorporate into Responsibilities as a subsection? The instruction: Prefer a few substantive sections over many thin ones. So we could merge Metrics into Responsibilities as part of responsibilities. But we have a separate list for metrics; maybe we can keep as part of Responsibilities (
). Similarly Challenges could be part of Responsibilities.
Thus we will have:
About the role
... company description + role description ...
Responsibilities
- ... (including mission bullets, core responsibilities, metrics, challenges) ...
But we need to keep the content structured; maybe we can have multiple under same heading? The instruction: Use - for any list of duties/requirements/benefits. It doesn't forbid multiple lists. So we can have separate
for each logical group under Responsibilities.
Similarly for Qualifications: we can have - each qualification.
Benefits:
- each benefit.
Schedule:
Work model Hybrid / On-Site Office requirement 2 days per week at the office.
We must not repeat job title as heading.
Now craft HTML.
Be careful to escape any HTML special characters like &, <, >. The text includes "&" in "AD&D". Should we escape? In HTML, "&" must be written as &. So "Life Insurance and AD&D" => "Life Insurance and AD&D". Also "RSUs" fine. Also "AI/DevEx" includes slash okay. Also "CI/CD". Also "LLM". Also "AI-native". Also "AI-assisted". Also "AI-driven". Also "AI/DevEx". Also "AI/DevEx". Also "AI/DevEx". Also "AI/DevEx". Also "AI/DevEx". Also "AI/DevEx". Also "AI/DevEx". Also "AI/DevEx". Also "AI/DevEx". Also "AI/DevEx". Also "AI/DevEx". Also "AI/DevEx". Also "AI/DevEx". Also "
Schedule
with paragraph. Also maybe "About Nu" could be considered "About the role"? Already have About the role. The company description maybe not needed as a heading; but we could include as part of About the role paragraph. We must not include boilerplate like recruitment process AI etc. Remove that. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details. Let's extract content. About Nu paragraph: "Nu is the leading digital bank in Latin America, serving 140 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." We can include that in About the role paragraph maybe preceding role description. About the role paragraph: "We are looking for a Senior Staff Software Engineer to drive the overarching strategy, technical vision, and execution across Nubank’s Quality & Developer Experience ecosystem. You will sit at the epicenter of our engineering transformation. This role goes far beyond traditional quality assurance or testing; you will own the end-to-end (E2E) Developer Experience (DevEx) across the entire Software Development Life Cycle (SDLC). From internal developer platform tools and boundary APIs to our suite of testing mechanisms and automated code reviews, your mission will be to architect AI-native systems that drastically reduce review latency, guarantee architectural correctness, and double engineering productivity across Nubank. Working alongside our most tenured engineering leaders and reporting into platform leadership, you will serve as the technical authority who brings fresh, market-leading perspectives from high-velocity environments to elevate our foundational standards." Then maybe include Mission paragraph: "Mission Architect, scale, and operationalize an AI-transformed Developer Experience & Quality strategy so that: ..." This is a list of bullet points? It's a colon then bullet list with dash? Actually it's sentences with colon and then bullet-like items each starting with a bold phrase? In text: "Mission Architect, scale, and operationalize an AI-transformed Developer Experience & Quality strategy so that: The "Secure and Quality Path" is the Default: Automated mechanisms, linting, and smart context-aware agents enforce strict architectural standards, eliminating code quality degradation caused by high-volume AI code generation. Developer Velocity Doubles (2x): The friction in review latency, pull request (PR) approvals, and continuous integration is systematically dismantled, enabling thousands of engineers to ship features safely to 140M+ customers at unprecedented speeds. SDLC is Re-imagined for AI: Foundational tools across code authorship, testing, boundary APIs, and PR reviews are seamlessly integrated with state-of-the-art AI frameworks, smart LLM evaluations, and context-engineering hooks. Automated Approval Standards are Built: Clear deterministic checks and intelligent human-in-the-loop triggers are established to achieve safe, automated PR approvals without manual bottlenecks." We could format as- each bullet.
Then Core Responsibilities: list.
Let's extract responsibilities bullet points:
- Architect E2E Quality & DevEx Platforms: Define and evolve the multi-year vision for our developer tooling ecosystem—covering internal developer platforms, boundary APIs, test automation suites, and pull request review systems.
- Lead the AI-Driven Code Review Evolution: Architect automated review mechanisms that leverage multi-model evaluations (e.g., using specialized LLMs to audit generated code), custom IDE/GitHub plugins, and deterministic linting to accelerate PR merge times while preventing code bloat or quality degradation.
- Define Human-in-the-Loop Boundaries: Set company-wide paradigms for when code changes can be automatically approved and merged versus when human intervention or secondary AI audits are required.
- Partner & Mentor Across Engineering: Act as a force multiplier by partnering with engineers and product managers, elevating the technical bar and instilling modern, high-velocity DevEx practices.
- Balance AI Speed with System Integrity: Establish observability, defect-tracking metrics, and safety rails to ensure that rapid AI-assisted development does not introduce structural fragility into Nubank's core services.
- Influence Build vs. Buy Strategy: Evaluate top-tier market tools, AI coding frameworks, and internal platforms to decide when to build bespoke internal agents or integrate emerging third-party tooling.
Then Key Business & Engineering Metrics You Will Influence: list:
- Developer Productivity & Velocity: Achieve a 2x improvement in overall engineering productivity across Nubank's engineering organization.
- PR Review Latency: Direct reduction in time-to-merge for pull requests across all BUs and countries.
- Code Base Health & Quality: Zero degradation in code quality and zero increase in system defects despite exponentially higher volumes of AI-generated code.
- Automated PR Approvals: Increase in the percentage of routine, low-risk code changes safely approved and merged via automated mechanisms.
- Platform Adoption & Satisfaction: High adoption and developer satisfaction (CSAT) across proprietary internal DevEx tools and boundary APIs.
Then Challenges and Opportunities (What You’ll Own): list:
- Navigating Scale: Every change you introduce to the SDLC impacts thousands of microservices and hundreds of engineering teams delivering features to over 140 million users.
- Tackling "Code Slop" at the Root: As AI agents generate code faster than humans can read it, you will solve one of the industry's newest and hardest problems: keeping codebase quality high without slowing down the team.
- High Autonomy & Strategic Breadth: You will operate with autonomy, driving horizontal technical alignment without needing micro-oversight, helping lead our joint DevEx technical council.
Then Core Qualifications (What We're Looking For): list:
- Senior IC Leadership Track Record: backend software engineering experience, with a proven track record designing developer platforms, core infra, or DevEx systems at high scale.
- Deep DevEx & SDLC Expertise: Extensive domain depth in code review systems, test automation platforms, CI/CD pipelines, developer platforms, or static analysis tools built for massive engineering organizations.
- AI Transformation & Tooling Experience: Direct hands-on experience or deep technical familiarity with AI-assisted software development—including LLM evaluation pipelines, GitHub Copilot/agent integrations, prompt/context/graph engineering, or AI-driven code review frameworks.
- Autonomous & Opinionated Technical Leader: Demonstrable history of driving technical strategy independently, navigating ambiguity, and bringing strong, battle-tested opinions on "what good looks like" in modern software development.
- High-Velocity Culture Fit: Experience operating in fast-moving, high-bar environments (e.g., top-tier tech firms, high-growth AI/DevEx startups, or elite AI labs) where speed of execution and technical rigor are equally valued.
Then Work Setup: "Work model Hybrid / On-Site Office requirement 2 days per week at the office."
Then Benefits list:
- Opportunity of earning equity at Nu (RSUs as a public company)
- Medical, Dental, and Vision Insurance
- Life Insurance and AD&D
- Extended maternity and paternity leaves
- Nucleo - Our learning platform of courses
- NuLanguage - Our language learning program
- NuCare - Our mental health and wellness assistance program
- 401K
- Health Savings Account and Flexible Spending Account
- Work-from-home allowance
- Relocation assistance package
We should not include the recruitment process AI note.
Now produce HTML.
We need sections: About the role, Responsibilities, Qualifications, Benefits, Schedule. Possibly also include a section for "Metrics"? Not in allowed headings; but we could incorporate into Responsibilities as a subsection? The instruction: Prefer a few substantive sections over many thin ones. So we could merge Metrics into Responsibilities as part of responsibilities. But we have a separate list for metrics; maybe we can keep as part of Responsibilities (
- ). Similarly Challenges could be part of Responsibilities.
Thus we will have:
- ... (including mission bullets, core responsibilities, metrics, challenges) ...
- for any list of duties/requirements/benefits. It doesn't forbid multiple lists. So we can have separate
- for each logical group under Responsibilities.
Similarly for Qualifications: we can have
- each qualification.
Benefits:
- each benefit.
Schedule:
Work model Hybrid / On-Site Office requirement 2 days per week at the office.
We must not repeat job title as heading. Now craft HTML. Be careful to escape any HTML special characters like &, <, >. The text includes "&" in "AD&D". Should we escape? In HTML, "&" must be written as &. So "Life Insurance and AD&D" => "Life Insurance and AD&D". Also "RSUs" fine. Also "AI/DevEx" includes slash okay. Also "CI/CD". Also "LLM". Also "AI-native". Also "AI-assisted". Also "AI-driven". Also "AI/DevEx". Also "AI/DevEx". Also "AI/DevEx". Also "AI/DevEx". Also "AI/DevEx". Also "AI/DevEx". Also "AI/DevEx". Also "AI/DevEx". Also "AI/DevEx". Also "AI/DevEx". Also "AI/DevEx". Also "AI/DevEx". Also "AI/DevEx". Also "
- each benefit.
Schedule:
- each qualification.
Benefits:
About the role
... company description + role description ...
Responsibilities
- under same heading? The instruction: Use