Software Engineer II (JVM)

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

• Core framework features, designed and shipped by you. Schema evolution, pagination, rate limiting, circuit breaking, and the automated retries and self-recovery that keep pipelines running without a human watching. The SDKs and interfaces other teams build on sit here too: you write them, document them, and use them yourself.
• The streaming and processing path in production. Kafka, Spark, and Flink workloads, checkpointing, backpressure, and failure recovery. You operate what you build.
• Design decisions inside your scope, and a real voice in the ones above it. Multi-tenancy, concurrency, and latency show up in almost everything here, and you would be expected to have views on the tradeoffs rather than only implementing someone else’s.
• The hard debugging. Trace failures across Kafka clusters, distributed runtimes, and flaky third-party APIs, fix them, then build the guardrails so they do not come back.

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

• 5 to 8 years of software engineering, with some of it on backend platforms, services, or SDKs rather than only end-user applications.
• Strong Java. You understand JVM memory management, concurrency models, and non-blocking I/O, and you can work your way to the cause of a thread starvation issue from a heap dump.
• Hands-on experience with distributed systems in production: Kafka, Spark, Flink, or similar. You have run them, not only built against them.
• Comfort with the modern data stack and the protocols around it: Snowflake, Databricks, gRPC, GraphQL, webhooks, and CDC.
• You have owned production systems and know what good operational discipline looks like.
• You use AI tools in your actual work and can say specifically where they help and where they mislead you.

Bonus points

• Contributions to open-source data projects such as Airbyte, Flink, Debezium, or Arrow.
• Time at an iPaaS or ELT company: MuleSoft, Fivetran, Informatica, Airbyte, or similar.
• Deep Kubernetes and cloud-native experience, including Strimzi for Kafka.
• Security architecture: OAuth 2.0, mTLS, and encrypted credential management at scale.

You'll thrive here if

• You want ownership and will take it. You write code every day and you carry what you ship, through deploy and on-call.
• You are comfortable defining scope on the fly and shipping before the full picture is clear.
• You would rather build the guardrail than fix the same failure twice.
• You raise the quality of what is around you through review and pairing, not just the quality of what you write yourself.

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.

• Coding. Working through real code rather than a puzzle.
• Low-level design. How you structure a system at the class and interface level, and the tradeoffs you would defend.
• High-level design. Distributed systems design on a problem close to what we run in production.
• Hiring Manager. Ownership, clarity of thinking, and how you actually use AI in your work.

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

• 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