Free · takes a minute · your resume fills your profile
CoreHRx never asks candidates for money. If anyone does, .
Sign in to see your fit: the skills, experience and location this job asks for, checked against your profile.
Location: Pune, Maharashtra
Department: Engineering
We are building an AI system that creates data connectors by itself and keeps them working by itself.
No engineer should need to manually build every connector. No engineer should need to come back six months later because the source API changed.
Work that traditionally takes weeks or months should take hours. But building a connector is not the hardest part.
The real question is: Would you trust this system to run by itself, with nobody watching, for months?
That is the job.
The Problem
Every data company has the same problem. There is always another source a customer wants that you do not support.
Today, supporting that source means an engineer has to understand the API, implement authentication, pagination, schema handling and incremental syncs, test the connector, deploy it and maintain it indefinitely.
We want an agent to do most of this autonomously.
It needs to understand API documentation, generate connector logic, validate the data and deploy the connector.
Then the harder part starts.
APIs change. Schemas evolve. Authentication breaks. Rate limits change. Fields disappear. New failure modes appear in production.
The system needs to detect those changes, understand what happened, decide whether it can safely repair the connector, validate the fix and know when to ask a human for help.
“The AI built it” is not good enough. The connector has to be correct.
If a connector silently produces bad data, a customer dashboard may be wrong and someone may make a bad decision based on it.
Your job is to make autonomous connectors trustworthy.
Your Role
What you will work on
The central problem is deciding what the system can safely do by itself and where it needs human intervention.
You will work on problems such as understanding API documentation automatically, inferring authentication and pagination, discovering schemas, handling schema evolution, generating connector code, detecting API changes, repairing failures, scoring confidence and building evaluation systems that tell us whether an autonomous action was actually correct.
You will also help answer harder questions.
These are the problems you will help solve.
What success looks like
The leadership part
Who will thrive here
Who this role is probably not for
What we look for
Your first three months
In your first month, learn how our connectors work today, where the agent performs well, where it fails and how the team operates.
In your second month, form your own view of what trusted means for your area and begin building the evaluations and reliability mechanisms needed to prove it.
By your third month, you should be making architecture decisions, taking ownership of a major part of the system and starting to hire.
Why this role
Hevo is a Series B data infrastructure company with $42M raised.
More than 2,000 companies across 40 plus countries use Hevo to move data from more than 150 sources into platforms such as Snowflake and BigQuery.
Our customers include DoorDash, Shopify, Pinterest, Postman and Icelandair.
Our engineering team is built in India, and so are the decisions.
We are not the remote engineering office of a US company.
The people building the product are the people deciding what to build.
Most IT Jobs posts in Pune ask for 3–6 years of experience (42% of 122 that say).
From live job posts on CoreHRx, updated 1 Nov 2026. Skill figures count posts that list their skills; salary figures only posts that show a salary.
The post asks for 8 Yrs experience.
In Pune, Bangalore (on-site).
It is a full time job.
Interview preparation · 60 questions
This guide is for Indian job seekers preparing for Java backend roles, from freshers facing campus and first-job interviews to experienced developers moving into senior positions at product companies and IT services firms. It covers what interviewers ask most in 2025 and 2026 on Java 17 and 21 and Spring Boot 3: OOP, collections, equals and hashCode, streams, exceptions, concurrency and JVM memory, then dependency injection, auto-configuration, REST controllers, validation, JPA and Hibernate, security, microservices and testing. Questions are grouped as easy, medium and hard. Read each answer, compile the code yourself and practise explaining it aloud.
Questions you may be asked
Create a free profile and we email you new IT jobs in Pune, at most once a week.