Staff Engineer

Staff EngineerEuropeTech – Integrations /Remote /Remoteapply for this job€90,000 - €125,000 a yearStaff 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...