Staff Core Platform Engineer n8n · Remote · Germany · Platform & Infrastructure €81,500–€122,500 e 2mo ago

Devopsroles; Berlin; Hybrid; EUR 120,000 - 180,000; Full time

Job summary

n8n is seeking a Staff Architect to shape and evolve the core platform architecture powering 80+ product engineers and open-source users. You’ll drive coherent execution across Core Platform, design adaptable backends, and partner with the FE workstream on canvas architecture and platform primitives.

You’ll lead architectural decisions, mentor engineers, and define stable interfaces while expanding data pipelines, durable execution, and multi-tenant scalability for cloud and self-hosted

Qualifications

• Staff-level architectural ownership across multiple systems with long-term impact.
• Systems thinking about invariants, correctness, boundaries and trade-offs.
• Configurable, scalable systems serving multiple use cases.
• Distributed systems depth: asynchronous processing, idempotency, state machines.
• Data architecture for scalable persistence, performance and reliability.
• Strong TypeScript experience and backend Node.js beyond CRUD.
• Cross-team technical leadership through RFCs and design reviews.
• Platform enablement mindset to improve developer experience.

Responsibilities

• Lead architecture across Core Platform teams for coherent platform.
• Design adaptable backend foundations for multiple workloads and deployment models.
• Partner with FE platform on canvas architecture and platform primitives.
• Evolve core subsystems: durable workflow, orchestration, queue, worker management.
• Ensure correctness, resilience, and data persistence strategies across services.
• Define stable platform interfaces and abstractions for safer migrations.
• Mentor engineers through design reviews and establish technical standards.

Skills

Staff-level ownership

Systems thinking

Configurable systems

Distributed systems

Data architecture

TypeScript & Node.js

Cross-team leadership

Platform enablement

Long-horizon engineering

Job description

The AI orchestration of your wildest imagination.

n8n is the open workflow orchestration platform built for the new era of AI. We give technical teams the freedom of code with the speed of no-code, so they can automate faster, smarter, and without limits. Backed by a fiercely inventive community and 500+ builder-approved integrations, we’re changing the way people bring systems together and scale ideas for impact.

Since our founding in 2019, we’ve grown into a diverse team of over 260 - working across Europe and the US, connected by a shared builder spirit and with our centre of gravity in Berlin. Along the way, we’ve:

• Cultivated a community of more than 650,000 active developers and builders

• Earned 190K+ GitHub stars, making us one of the world’s Top 40 most popular projects

• Backed by top investors, from Sequoia’s first German seed to our SAP's recent strategic investment - bringing us to a $5.2bn valuation

We’re in a defining moment of an incredible journey. Come and build with us.

Your main goal will be to shape and evolve the core platform architecture that powers n8n — creating scalable, configurable foundations across execution, infrastructure, and frontend platform so 80+ product engineers and our open-source community can build confidently across cloud and self-hosted deployments.

Working across our platform teams, you’ll bring architectural coherence to the systems they jointly own and help us make the right long-term technical decisions as n8n scales:

Architectural direction across Core Platform

• Drive architecture across the two Core Platform teams, ensuring execution, infrastructure, data, and frontend platform systems evolve as a coherent whole rather than independent components.

• Design highly adaptable backend foundations that support different workloads, deployment models, shared product team needs, and future scale without creating unnecessary complexity.

• Partner with the FE platform workstream on core canvas architecture, real-time communication, performance, plugin contracts, and other platform primitives used by product teams.

Execution, distributed systems & data foundations

• Evolve core subsystems including durable workflow execution and state, orchestration, queue and task distribution, worker management, scheduling, and horizontal scaling.

• Design for correctness and resilience across distributed environments, including failure modes, idempotency, state transitions, tenant isolation, and reliability guarantees.

• Shape our data and persistence architecture, including database scaling, sharding, migration strategies, deployment abstractions, and long-term operational maintainability.

Platform architecture & engineering enablement

• Lead consequential technical decisions through clear proposals and RFCs, making trade-offs explicit and aligning engineers and stakeholders around durable solutions.

• Define stable platform interfaces and abstractions that reduce coupling, support safe migrations, and make the platform easier for feature teams to build on.

• Mentor engineers across all engineering teams through design reviews, pairing, and technical guidance, raising the bar for architecture, system design, and maintainability.

REQUIREMENTS

Must-haves

• Staff-level architectural ownership: You have a track record of leading architecture across multiple systems or teams, including migrations, re-architectures, or foundational platform initiatives with long-term organizational impact.

• Systems thinking: You reason deeply about invariants, correctness, failure modes, boundaries, and trade-offs, and you’re comfortable making decisions where there is no obviously perfect solution.

• Configurable systems at scale: You’ve designed highly configurable, adaptable systems that serve multiple use cases or operating modes without becoming brittle or excessively complex.

• Distributed systems depth: You’ve designed and operated distributed systems involving concepts such as asynchronous processing, idempotency, state machines, queues, consistency, and resilience.

• Data architecture at scale: You’ve worked on data-intensive systems where persistence, performance, isolation, migrations, and operational reliability were meaningful architectural concerns.

• TypeScript & Node.js depth: You have strong TypeScript experience and have built substantial backend systems with Node.js beyond conventional CRUD applications.

• Cross-team technical leadership: You influence through technical judgment, clear communication, RFCs, design reviews, and mentorship, helping multiple teams converge on better solutions without relying on formal authority.

• Platform enablement mindset: You care about creating clear contracts, abstractions, and developer experiences that allow other engineers to move faster and more safely.

• Long-horizon engineering: You’re energized by modularization, migrations, refactoring, and evolving existing systems while keeping the product and engineering organization moving.

Nice-to-haves

• Workflow, orchestration or devtools experience: You’ve worked on workflow engines, orchestration platforms, developer tools, or infrastructure-heavy SaaS products.

• Frontend platform architecture: You’ve worked with architecture-heavy frontend systems such as canvas applications, plugin systems, real-time applications, web workers, or complex rendering environments.

• Durable execution patterns: You’ve designed or operated systems using event sourcing, sagas, durable execution, or related state-management patterns.

• Multi-tenant architecture: You’ve designed systems where tenant isolation, resource management, data boundaries, or noisy-neighbour concerns were important.

• Open-source experience: You’ve contributed to or maintained open-source software and understand the additional pressure around public contracts and backward compatibility.

• Large-scale SaaS exposure: You’ve operated systems at meaningful scale or worked in environments where reliability and architectural decisions had broad customer impact.

• Monolith → modular migrations: You’ve decomposed monolithic systems or led incremental architectural migrations without preventing product teams from continuing to ship.

• Multi-deployment awareness: You’ve