Staff Engineer — Integrations Team

1. Overview

Who We Are

Yuno is the payment orchestrator built for global scale, founded by the team behind Rappi, one of Latin America's most ambitious tech companies. We connect businesses to 300+ payment methods worldwide through a single integration. We're growing fast, and we're looking for engineers who want to build the infrastructure moving money globally.

The Role

We're hiring a Staff Engineer to set the technical direction for our Integrations domain — the 130+ provider integrations and 95+ webhooks that connect Yuno's platform to PSPs, acquirers, payment gateways, fraud and 3DS providers worldwide.

This is an individual-contributor role with domain-level scope, reporting directly to the VP of Engineering. You won't own a feature or a service — you'll own how the entire integration platform evolves: the patterns every integration follows, the frameworks the squads build on, the quality bar for production, and the architectural decisions that will still hold up at 5x our current scale. You'll lead through influence, not headcount: aligning multiple squads, coaching Senior engineers, and partnering with Product, Compliance, and Security on the trade-offs that shape the domain.

If you've been the most senior IC on a payments or integrations platform and want to do it again at a company growing into its global scale, this is that role.

2. How Yuno Will Challenge You

AI-First Engineering

At Yuno, AI is not optional, it's foundational to how we build. As a Staff Engineer you will:

• Use AI-assisted tools (e.g., Claude Code, Copilot, or similar) for coding, testing, debugging, and documentation as a daily default.

• Shape how the Integrations domain adopts and standardizes AI-assisted workflows — the patterns, prompts, guardrails, and review practices that other engineers will inherit.

• Continuously explore where AI can replace manual work in development, testing, incident response, and provider onboarding.

Building at Scale

• Set architectural direction for the integrations platform — define the patterns, frameworks, and reusable abstractions that 130+ provider integrations are built on.

• Drive platform-level improvements: dynamic mapping, pipeline orchestration, egress proxy contracts, observability primitives, error-severity models — the shared rails every integration depends on.

• Anticipate second-order effects of architectural choices: how a pattern adopted today plays out across regions, providers, and squads twelve months from now.

• Evolve high-performance APIs and microservices in Go, designed for reliability, low latency, and the throughput a global payment orchestrator demands.

Technical Excellence

• Define the quality bar for the Integrations domain — testing strategy, observability standards, incident-prevention practices, production-readiness criteria.

• Drive incident prevention and production excellence: post-incident learnings become reusable patterns, not one-off fixes.

• Apply and codify secure software development practices, including OWASP standards, PCI compliance, data privacy, and the regulatory requirements specific to payment integrations.

• Set the example for clean, well-tested, production-ready code — and make it the path of least resistance for every other engineer in the domain.

Cross-functional Execution

• Drive trade-offs at the domain level with Product, Compliance, Security, and Business — not just consume their requirements, but shape them.

• Align multiple squads on shared technical direction, RFC processes, and design reviews.

• Translate fast-moving regional and provider priorities into a coherent technical roadmap that doesn't fragment the platform.

Technical Leadership

• Lead cross-team design reviews for the highest-stakes integration and platform decisions.

• Mentor and grow Senior engineers across the domain; sponsor their next step.

• Build communities of practice around integrations engineering — the venue where standards get debated, agreed, and adopted.

• Be the engineer Squad leads come to when a decision is hard, ambiguous, or has consequences they can't fully see yet.

3. What You Bring

The Essentials

• 8+ years of backend engineering experience building high-throughput, production-grade systems in Go, Java, or Kotlin — with at least 3 years operating at Senior/Staff/Lead level.

• Demonstrated track record of leading architectural decisions adopted by multiple teams — not just within your own squad.

• Direct experience in payments, fintech, or PCI-regulated systems — integrations with PSPs, acquirers, fraud/3DS providers, or comparable regulated infrastructure.

• Deep expertise in microservices, event-driven architectures, APIs, and integration patterns at scale.

• Strong experience with SQL and relational databases (PostgreSQL preferred); comfort with caching, queues, and async pipelines.

• Experience defining technical standards, frameworks, or platform abstractions that other teams build on.

• Working knowledge of secure software development, OWASP, and PCI-DSS principles.

• Comfort using AI-assisted development tools (Claude Code, Copilot, or similar) as a core part of your workflow — and an opinion on where they help vs. hurt.

• Ability to communicate complex technical topics clearly to engineers, Product, and executive audiences alike.

• Demonstrated experience mentoring and growing other engineers.

• Full professional proficiency in English — written and spoken.

What Would Make You Stand Out

• Prior Staff or Principal Engineer title at a payments orchestrator, PSP, gateway, or fintech infrastructure company.

• Contributions to integration frameworks, payment orchestration platforms, or open-source projects in the payments / fintech space.

• Experience scaling integrations across multiple regions (LATAM, APAC, EMEA, NA) and the regulatory regimes that come with them.

• Public technical writing, conference talks, or other evidence of external technical voice.

• Hands-on experience with cloud and DevOps environments (AWS, Docker, Kubernetes).

4. Life at Yuno (Our Culture)

At Yuno, culture is a key part of how we operate and scale:

• Fast-paced & global: We operate in a dynamic, fully remote environment across multiple time zones.

• Remote-first: Work from anywhere while collaborating with a diverse, international team.

• Ownership & autonomy: Individuals are trusted to take responsibility and drive impact.

• Collaboration: Open feedback, teamwork, and clear communication are core to how we work.

• Continuous learning & innovation: We encourage growth and experimentation with new technologies.

• Transparency & impact: Everyone contributes directly to company success with high visibility.

5. What We Offer at Yuno

• Competitive Compensation.

• Remote Work — work from anywhere.

• Home Office Bonus — a one-time allowance to set up your ideal workspace.

• Work Equipment.

• Stock Options.

• Health Plan wherever you are.

• Flexible Days Off.