Want to know if this job is worth applying to?
Bengaluru, Karnataka, India
Hybrid
Nexla is the data connectivity layer for enterprise AI. Over 1,000 bidirectional connectors give agents real-time access to data and actions over MCP. Nexla's Agentic Data Integration handles high-volume streaming ETL, CDC, and Document ETL. At the core of the platform is Helix, a context engine that continuously learns from metadata, schemas, telemetry, and documentation to give agents accurate context and keep pipelines reliable. Nexla processes over a trillion records a month for enterprises including DoorDash, LiveRamp, LinkedIn, and J&J. Honorable Mention in the Gartner Magic Quadrant™ for Data Integration Tools, and top-rated by customers on Gartner Peer Insights four years running.
Role
You would work on the backend systems that move data through Nexla: JVM services, the streaming runtime on Kafka, and the distributed processing underneath it. Production Java every day. You take a problem, shape the design, build it, and own it through deploy and on-call. You debug it when it breaks. Small, focused team, which is why the ownership is real rather than nominal. This role sits closest to the integration layer, where the platform meets everything outside it, so the problem below is the one you would live in.
What you'll own
Roughly 70% building and shipping, 15% design and technical discussion, 15% code review and the RFCs, runbooks, and docs that come with it.
The hard problem
Our platform integrates with more than a thousand external systems, each with its own schema quirks, auth scheme, rate limits, and retry semantics. The framework problem is the N+1 one: making the thousandth integration as cheap to add as the tenth. That means absorbing the differences into the abstraction rather than special-casing them, while the data underneath keeps moving at production volume.
Must-Haves
Bonus points
You'll thrive here if
One thing to be clear about: our product definition is still moving as AI reshapes data integration, and the platform has to move with it. If you want a stable, well-defined surface to work on, this is not it.
How we hire
Four conversations, about two weeks end to end.
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, 2 days a week in office. Compensation includes base salary and equity, set by depth and experience rather than by title. You will need to overlap with morning Pacific hours for syncs, design reviews, and collaboration with our US-based leadership and engineering teams.
Worth a look before you apply
A few large companies - DoorDash, SentinelOne, Johnson & Johnson, LinkedIn, Amex, Integrity Marketing, among them use Nexla for data integration. Connectors, runtime, transformations, scheduling, the parts of the stack where data has to move between systems reliably.
The reason this is an interesting moment to join is what the agent shift is doing to the category. Data integration used to mean "land this data in that warehouse so a human can look at it." That product is mature. What it's becoming is closer to "an agent asks a business question, and the platform figures out which data and what code and which APIs add up to a real answer." That's a much bigger problem, and most of the architecture for it hasn't been built yet by anyone.
A concrete example. A revenue team wants to ask "which enterprise customers are showing renewal risk" and get a real answer through whatever agent or app they work in. Today there is no clean way to answer that question, it requires CRM, usage, support, and billing data joined in org-specific ways, and the calling agent can't just invoke a tool that returns the right answer unless someone first establishes whether the underlying data is even capable of producing one.
That is the system we are building. A probe agent investigates the data plane whether the right fields are populated, whether freshness is adequate, whether the joins exist, whether credentials cover the required scope and returns a grounded feasibility answer. Where there are gaps, Express.dev composes the pipelines to close them. The capability is then exposed as an MCP server: "renewal risk" as a curated product, with the business logic correct and the query semantics described well enough that the calling agent uses it as intended. The MCP Gateway governs which agents can call which capabilities, with the policies, audit, and observability an enterprise control plane requires.
The bet is that ten years of connector work, an enterprise customer base, and a runtime that already moves real volume are the right foundation to define this layer from.
