Staff / Principal Backend Engineer

INTEGRTR GmbH; India; À distance; INR 3 500 000 - 6 000 000; Plein temps

Résumé du poste

INTEGRTR GmbH is hiring a senior backend architect to act as the technical backbone for backend engineering. You will guide system design, review critical decisions, and elevate the engineering bar across the organization.

The role is hands-on and senior IC-focused, not management, with responsibility for architecture, platform coherence, and developer experience in a serverless Node.js monorepo. Remote-friendly with global collaboration.

Qualifications

• Strong distributed-systems and integration experience across multi-tenant environments.
• Proven ability to guide architecture discussions and raise engineering standards.
• Hands-on backend leadership with deep coding experience.

Responsabilités

• Own platform architecture and service boundaries across the backend stack.
• Lead design reviews, code reviews, and pairing to raise quality.
• Unblock teams and improve developer experience across tooling and workflows.
• Review and advise DevOps and other teams to maintain coherence.
• Work on POCs and introduce new tools and techniques.

Connaissances

Distributed systems

Architecture leadership

Backend engineering

APIs

Serverless

Formation

Bachelor's degree in CS/CE/IT

Outils

AWS

Serverless Framework

SAP SuccessFactors

Workday

Description du poste

INTEGRTR is building the next generation of enterprise integration and HR-tech products with speed, clarity, and a builder-first mindset.

This is a senior technical leadership role. You will serve as the technical backbone for backend engineering, guide system design, review critical decisions, and raise the engineering bar across the organization.

About the product you’ll work on

The product runs on a Node.js and serverless monorepo that does serious distributed work: multi-tenant systems with tenant-scoped isolation, asynchronous workflows, and data transformations with real consequences downstream. When it runs, our customers’ payroll, people, and compliance data depend on it being correct.

We move quickly, build in the open, and use AI tooling as a normal part of the job. Most of the time we’d rather get a sharp prototype out this week than wait on a perfect plan next quarter.

Why this role exists

We have strong engineers. What we don’t have yet is the person the team turns to in an architecture discussion, the one who lifts the work just by being part of it and who others want to learn from. Good decisions get made at the individual level, but nobody is looking across the whole platform and keeping it coherent.

That’s the gap we want to fill. Not someone who sits above the team, but the engineer everyone is glad to have in the room.

This is a senior individual-contributor role with real technical weight. It isn’t people management, and it isn’t a role where you stop writing code.

What you’ll own

• The platform, backend first. How the platform fits together: where the service boundaries sit, how the pieces talk to each other, and which technical debt is worth paying down. Backend is where you’ll go deepest. You set direction by convincing people, not by handing down orders.
• The standard of the work around you. Design reviews, code reviews, pairing, and the example your own commits set.
• Unblocking people. When someone is stuck, they bring it to you and leave with a way forward, fast.
• Developer experience. Keeping the codebase, tooling, and workflows good to work in, because the team’s daily speed is worth the effort.
• Helping the wider org. Reviewing and advising other teams, DevOps included, when they need a second set of eyes.
• The hard, hands-on work. The most ambiguous problems, wherever they sit in the platform.
• POCs and new tech. Getting a rough idea running, and bringing the team along by introducing tools and techniques they can pick up too.

A typical month

• Review the designs the team writes, and write one yourself when something needs it (AI helps here), then get everyone on the same page without it dragging.
• Sit with an engineer on a hard distributed-systems or data-integrity problem they can’t crack alone.
• Take on a performance or structural problem the practical way: profile it, find the actual bottleneck, and fix it with the right pattern instead of another patch. Rather than declaring the whole stack needs a rewrite, you break it into phases, take some of it on yourself, hand out the rest, and get people moving.
• Try a new tool or approach as a quick POC, then either back it or drop it.

What we’re looking for

• Solid distributed-systems and integration experience: multi-tenancy, APIs, async and event-driven work, data consistency, and the ways integrations fail when you don’t control the other side.
• Real interest in enterprise software. You don’t need SuccessFactors or Workday experience today, but you should want to understand how large organisations actually run, and be up for going deep with our help. We’ll teach you the SuccessFactors/Workday side.
• Clear communication. You can disagree well, explain a call so people get behind it, and reply when people need you.
• Good remote habits. Around when the team needs you, honest about your availability, and steady with updates. Remote work runs on that kind of trust.
• At ease with AI agents. You use them to move faster, and you know when to trust the output and when not to.
• A habit of finding the next workable step and getting going, instead of overthinking it.
• Hands-on time with SAP SuccessFactors (EC, OData, integrations) or Workday.
• Serverless (AWS, Serverless Framework), CAP on SAP BTP, or similar enterprise-cloud stacks.
• Built developer or internal tooling, or AI-assisted engineering workflows.
• A record of getting ideas from prototype to production quickly.

This role probably isn’t for you if

Be honest with yourself

We’d rather say it now and save everyone the time. This probably isn’t the right fit if:

• You’d rather design from a distance and stay out of the code most of the time.
• You do your best work staying in one area. This platform needs you moving across it.
• You want heavy process in place before you contribute. We lean on judgement over procedure.
• A teammate asking you to unblock them feels like an interruption.
• You tend to go quiet for a while without telling anyone.
• You’d spend more energy arguing why a new tool won’t work than finding where it does.

How we work

• Flat on purpose. What you say carries because it’s right and useful, not because of a title.
• Light on process, high on trust. We keep ceremony low and let people own their work.
• Focused on outcomes, fully remote. We care what you ship and how you help, not from where you work

What you get

• A real say in where the platform goes. Your technical calls shape what the whole team builds, which is about as much influence as you get without managing people.
• Problems with actual depth. Correctness-critical integration work at scale, the sort that makes you a better engineer whether you like it or not.
• A domain few engineers get into. The SuccessFactors and Workday world is niche and valuable, and the team will get you up to speed on it.
• Room to move. No layers to push through, a short path from idea to production, and the freedom to bring in the tools and practices you trust.
• People to grow. The space and the backing to mentor, pair, and lift a team’s technical level, which is its own kind of progress.