Staff Software Engineer

Hevo Data moves more than 300 billion events a month through its data pipeline platform for over 2,000 customers across 40 plus countries, and this Staff role works on the core engine that does it. At that volume the product effectively is throughput and correctness, so the requirements concentrate on the parts of engineering that decide both. The posting is specific in a way that makes the interview predictable: alongside eight or more years of software development from an enterprise background, it asks for experience with the open source data processing engines the platform is built around, and separately for experience developing with concurrent and non blocking systems. That last requirement is the distinguishing one. Plenty of backend engineers with a decade behind them have never written genuinely concurrent, non blocking code, and it is listed on its own rather than folded into the general experience bar, which is a strong signal about where the technical conversation will go.

What the posting requires

- 8+ years of experience in software development, from an enterprise background
- Experience with popular open source data processing engines such as Spark, Kafka or Flink, or equivalent
- Experience developing with concurrent and non blocking systems
- A bachelor's degree in computer science, software engineering or a related field, or equivalent experience

The broader stack spans Java, Python, Go and C++.

What you would actually be doing

Engineering on the core pipeline engine behind a platform handling more than 300 billion events a month for over 2,000 customers across 40 plus countries. The problems at that scale are throughput, backpressure, correctness under load and failure behaviour rather than feature breadth.

Location and working pattern

Bangalore.

A good fit if

You have deep backend systems experience and want data infrastructure at scale. If you have specifically worked on concurrency and non blocking systems, this posting is asking for you more directly than most listings do, and that is worth leading with in your application.

Think twice if

Your experience is mainly request and response web services or CRUD applications. The concurrency requirement is called out separately from the general experience bar, which usually means it is a real filter rather than a preference.