Software Engineer (JVM)

Overview

Build and ship backend JVM services that move data through Nexla's integration platform, including the streaming runtime on Kafka and the distributed processing underneath, working closest to the integration layer where the platform meets external systems.

What you'll do

• Own features end to end: shape the approach with your lead, build it, write the tests, ship it, and stay with it after it ships.
• Write tests that catch real failures and code that the next person can read without a guided tour.
• Debug your own work in production, and over time other people's work.
• Trace failures through Kafka, a distributed runtime, or a third-party API that went quiet.
• Get fluent in the domain: schemas that change without warning, auth schemes, rate limits, and retries.
• Spend roughly 80% of time building and shipping, and 20% on code review, design discussions, and learning the systems around you.
• Work on pieces of the framework problem of making each new integration (across more than a thousand external systems) as cheap to add as the last.

What you'll need

• 2 to 5 years of professional software engineering experience.
• Java as your primary language.
• Solid JVM fundamentals: collections, concurrency basics, how memory behaves, and enough to read a stack trace or a thread dump.
• Write tests as part of building, not after someone asks for them.
• Comfortable with SQL.
• At least one of the protocols the platform speaks: gRPC, REST, webhooks, or CDC.
• Use AI tools in your actual work and say specifically where they help and where they mislead you.

Nice to have

• Exposure to Kafka, Spark, Flink, or a similar distributed system in production, even if you were not the one running it.
• Kubernetes, or experience debugging something that was not running on your laptop.
• Open-source contributions, side projects, or anything you have built that you can walk through.
• Data integration, ETL, or work that involved cleaning up someone else's messy data.

Details

• Location: Bengaluru, Karnataka, India.
• Hybrid work: 2 days a week in office.
• Compensation includes base salary and equity, set by depth and experience rather than by title.
• Overlap with morning Pacific hours for syncs, design reviews, and collaboration with US-based leadership and engineering teams.
• Hiring process: four conversations over about two weeks (coding, low-level design, high-level design, and hiring manager), with AI tools permitted in the coding round.