Role, briefly
Two systems sit at the centre of Nexla, and this role covers both. The connector layer talks to everything else: over a thousand SaaS applications, databases, streams, files, and APIs, bidirectionally, each with its own schema quirks, auth scheme, rate limits, and retry semantics. The runtime is what moves the data once a connector has it, built on Kafka, our own execution engine, and Ray for AI workloads, at billions of events a day with sub-second latency. You would own the engineering across both, along with the DevOps and QA work that keeps them shippable and running. The split today is roughly half design and code, half leading the team. You are expected to be in the architecture, in the reviews, and in the hard debugging sessions, not managing from a distance.

What you’ll own

• The architecture across connectors and runtime. How we abstract a thousand systems, how we handle JSON, Parquet, and Avro at throughput, how work gets scheduled and recovered when a node dies. You make those calls and you write the hard parts yourself.
• Reliability of everything your team ships, on-call included. Fewer failures reaching customers, faster detection when they do, and a release and test path that catches the obvious things before a customer does.
• What ships and in what order. You work directly with product, customer success, and support on what customers actually need, and you decide what gets built, what gets deprecated, and what waits.
• The engineers around you. Hiring, growth, and raising the technical bar, mostly through design review and pairing rather than process. As the team grows you will build tech leads under you and hand off implementation ownership, without handing off architectural accountability.

Ninety days in: you have shipped something non-trivial to production, named the two worst parts of the current design with a proposal attached, and the team has started routing hard design questions to you before they route them upward.

A real problem you’d hit here
We have thousands of connectors with thousands of customer pipelines running on them, and a runtime underneath that has to hold throughput and reliability at the same time. Neither property is something you fix once. The connector surface keeps growing, every new system brings its own failure mode, and the interesting bugs almost always live at the seam between a connector and the runtime, where neither team's instrumentation quite reaches. Closing that gap is the standing problem of this team.

Must-haves

• 12+ years building backend systems, and you are still hands-on. You can point at code you wrote recently and are proud of.
• Deep JVM experience. You have debugged distributed systems where the failure was not in the code you wrote.
• Production depth in Kafka, Kubernetes at high throughput, Redis or Memcached, and APIs over gRPC and REST.
• You have led engineers technically and carried direct reports: design review, mentoring, hiring, and the harder performance conversations.
• You use AI tools in your actual work and can say specifically where they help and where they mislead you.

Bonus points

• Data integration, ETL, or iPaaS background.
• Experience with Ray, Spark, or Flink for distributed or AI data processing.
• You have run DevOps and QA alongside an engineering team and know what good looks like in both.

You’ll thrive here if

• Urgency is your default. You'd rather ship a good answer this week than a perfect one next quarter, and you make that call without being asked.
• You own the outcome, not your slice of it. When something breaks between two teams, you fix it rather than route it.
• You close loops. What you pick up gets finished, and the people around you stop having to follow up.
• You set the pace. The team will calibrate its urgency to yours, and you know that.
• You want design authority across a wide surface without giving up the keyboard.

One thing to be clear about: this is a broad team and a broad stack, and you will not be the deepest expert in every corner of it. What we need is someone with the judgment to know where to go deep and the honesty to say when they are out of their depth.

How we hire
Five conversations, about one to two weeks end to end.

• Low-level design. Working through real code and real design detail rather than a puzzle. 60 min.
• High-level design. How you shape systems at scale: throughput, failure modes, and the tradeoffs you would defend under pressure. 60 min.
• Call with our Head of Product. How you work with a product: what you push back on, how you sequence, and how you decide what does not get built. 45 min.
• Bar Raiser with our CTO. The problem space, the architecture you would inherit, and whether this scope is what you actually want. 60 min.
• Call with our CRO. Ownership, judgment, and how you raise the bar of the people around you. 45 min.

On AI in the coding round. Use it the way you would on the job, ours or anyone else’s. We build AI tooling and we expect you to use AI tooling, so watching you work without it would tell us nothing useful. What we dig into is your judgment: what you delegated, what you verified, and what you threw away.
You will hear from us either way.

The practical stuff
Bengaluru, hybrid. Compensation includes base salary, bonus, and equity, set by depth and experience rather than by title. Part of your team sits in Eastern Europe and you will work closely with our US leadership team, so overlap outside Bengaluru hours is part of the job. We will be specific about how much in the first conversation rather than springing it on you later.

Worth a look before you apply:

• What we are building now. MCP Studio and Express, our two newest bets.
• Who uses us, and why. nexla.com/customers
• The product in engineer terms. docs.nexla.com
• Our CEO on why we take "Remember to Relax" seriously. Read the founder story
• Everything else. nexla.com  ·  Blog  ·  All open roles