{"id":1088730,"url":"https://alion.io/job/hevo-data-technical-lead-manager-2","title":"Tech Lead Manager - Autonomous Connectors","company":{"id":2891,"name":"Hevo Data","domain":"hevodata.com","url":"https://alion.io/company/hevo-data","size_band":"51-200","is_staffing_agency":false,"employer_type":"direct","is_intermediary":false,"listed_via":null,"ats_vendor":"Lever","truth_index":{"grade":"C","score":65,"open_postings":52,"ghost_share":0.577,"stale_share":0,"repost_share":0,"time_to_fill_p50_days":null,"computed_at":"2026-10-02T05:45:00Z"}},"role":"Leadership","role_family":"Leadership","seniority":"lead","employment_type":"full_time","work_mode":"on_site","remote_scope":null,"remote_scope_basis":null,"remote_working_hours":null,"hiring_geo_confidence":"structured","locations":["Pune, India"],"countries":["IN"],"hiring_countries":[],"hiring_countries_total":0,"salary":null,"salary_estimate":{"min_usd":30000,"max_usd":78000,"period":"year","method":"role_seniority_country_remote_cell","sample_n":22},"experience_years_min":8,"visa_sponsorship":false,"relocation_package":false,"has_equity":false,"technologies":[{"name":"Function Calling","optional":false},{"name":"LLM","optional":false},{"name":"Prompt Engineering","optional":false},{"name":"Tool Use","optional":false},{"name":"ETL/ELT","optional":true},{"name":"Java","optional":true},{"name":"Kubernetes","optional":true}],"status":"live","first_seen_at":"2026-09-21T11:35:09Z","employer_posted_date":"2026-09-21","last_verified_at":"2026-10-03T01:12:42Z","board_verified":true,"closed_at":null,"days_open":11,"trust":{"level":"ok","repost_count":0,"flags":["company_stale"],"days_open":10},"description":"What we are building\nWe are building an AI system that creates data connectors by itself and keeps them working by itself.\nNo engineer should need to manually build every connector. No engineer should need to come back six months later because the source API changed.\nWork that traditionally takes weeks or months should take hours. But building a connector is not the hardest part.\nThe real question is: Would you trust this system to run by itself, with nobody watching, for months?\nThat is the job.\nThe Problem\nEvery data company has the same problem. There is always another source a customer wants that you do not support.\nToday, 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.\nWe want an agent to do most of this autonomously.\nIt needs to understand API documentation, generate connector logic, validate the data and deploy the connector.\nThen the harder part starts.\nAPIs change. Schemas evolve. Authentication breaks. Rate limits change. Fields disappear. New failure modes appear in production.\nThe 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.\n“The AI built it” is not good enough. The connector has to be correct.\nIf a connector silently produces bad data, a customer dashboard may be wrong and someone may make a bad decision based on it.\nYour job is to make autonomous connectors trustworthy.\nYour Role\nYou will lead a team of 4 to 6 engineers while continuing to be deeply technical.\nRoughly 60 percent of your time will remain hands on. That includes architecture, design, coding, debugging, evaluations, code reviews and production issues.\nThis is not a people management role with occasional coding.\nYou will own a major part of the Connector Builder Agent, along with parts of our existing connector platform and database connector infrastructure.\nOther teams will own other parts of the system. You will work closely with them.\nExactly what you own will depend on your strengths and what the team needs when you join. We would rather build the role around a strong engineer than put someone into a fixed box.\nWhat you will work on\nThe central problem is deciding what the system can safely do by itself and where it needs human intervention.\nYou 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.\nYou will also help answer harder questions.\nHow do we know a generated connector is correct?\nWhich failures can an agent repair safely?\nWhen should the system stop and ask a human?\nHow do we catch an API change before the customer does?\nHow do we ensure that a model upgrade does not silently degrade hundreds of connectors?\nHow do we test systems whose outputs are not deterministic?\nThese are the problems you will help solve.\nWhat success looks like\nWithin your first few months, you should form a clear view of what trusted autonomy means for the systems you own.\nYou should establish measurable correctness criteria, build strong automated evaluations and define clear confidence thresholds and escalation paths.\nWithin six months, we expect your part of the system to autonomously build or maintain a meaningful class of connectors with measurable reliability.\nYou should also have raised the technical bar of the team around you.\nThe leadership part\nYou will hire 2 to 3 engineers over the next year.\nYou will help them become significantly better engineers.\nA year after joining your team, people should be solving harder problems than when they started. Some should be ready for promotion.\nIf growing engineers does not interest you, this is probably not the right leadership role.\nYou should already be the person engineers come to when the problem is difficult, even if you have never had a formal management title.\nWhen something breaks in production, you want to understand why.\nNot because we expect people to work all the time, but because you care whether the systems you build actually work.\nWho will thrive here\nYou have built serious backend, infrastructure or distributed systems.\nYou have also built real systems with LLMs and have experienced the gap between something working in a demo and surviving production.\nYou have dealt with outputs that change between runs.\nYou have built evaluations around probabilistic systems.\nYou have had to decide when a model should act autonomously and when deterministic software or a human should take over.\nYou want to lead engineers without giving up engineering.\nYou are comfortable working on ambiguous problems where the architecture is not already known.\nWho this role is probably not for\nIf you want to stop coding and become a full time people manager, this role will not work.\nIf your experience with LLMs is primarily prompt engineering or prototypes, the jump will be significant.\nIf you strongly prefer systems where correctness can be completely captured through deterministic code and unit tests, this problem may be frustrating.\nWe pay competitively, but compensation alone is unlikely to be the reason someone chooses this role.\nThe reason to join is the problem itself, the ownership you will have and how early the technology still is.\nWhat we look for\nYou have at least 8 years of experience building backend, infrastructure or distributed systems.\nYou have at least 1 year of technical leadership experience, with or without the formal title.\nYou have operated production systems and dealt with incidents, on call, reliability and SLAs.\nYou have built and operated an LLM powered system in production where correctness, reliability, latency or cost mattered.\nYou have hands on experience with areas such as agents, evaluations, retrieval, tool use, model failure modes or reliability.\nYou have experience with multi tenant systems, high availability or large data volumes.\nOur stack is primarily Java and Kubernetes. If you are strong in another JVM language or a similar systems language, you should be able to ramp quickly.\nExperience with data infrastructure, CDC, ETL, database internals or open source systems is useful but not required.\nStrong systems engineers can learn the domain.\nYour first three months\nIn your first month, learn how our connectors work today, where the agent performs well, where it fails and how the team operates.\nIn 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.\nBy your third month, you should be making architecture decisions, taking ownership of a major part of the system and starting to hire.\nWhy this role\nVery few teams are building autonomous AI systems that operate production infrastructure where being wrong has real consequences.\nThis is not a chatbot. It is infrastructure that has to remain correct, quietly, for months.\nIf that kind of problem excites you, there are not many places working on it this early.\nYou can talk to anyone in the company, including the CEO.\nArchitecture decisions in your area are yours.\nWhat you are trusted with depends on what you can do, not your title.\nSeveral of our engineering managers started as senior engineers.","description_format":"text","description_chars":7581,"description_truncated":false,"requirements":{"experience_years_min":8,"management_years_min":null,"team_size_min":null,"manages_managers":false,"education":{"level":"phd","optional":false},"security_clearance":false,"languages":[]},"benefits":[],"hiring_locations":[],"hiring_excludes":[],"relocation_offered":false,"industries":["Data Integration & ETL Tools"],"lifecycle":[{"event":"open","at":"2026-09-21T11:56:05Z"}],"liveness":{"score":58,"band":"ok","label":"Likely open","p_open":1,"p_active":0.585,"p_room":1,"age_days":10,"expected_fill_days":31,"reasons":["conf:11","stale_co","velocity","win:early"],"computed_at":"2026-10-02T05:45:00Z"},"pay":null,"html_url":"https://alion.io/job/hevo-data-technical-lead-manager-2","json_url":"https://alion.io/job/hevo-data-technical-lead-manager-2.json","meta":{"generated_at":"2026-10-03T01:54:45Z","cache_seconds":300,"methodology":"https://alion.io/methodology","terms":"https://alion.io/terms","contact":"https://alion.io/contact","api":"https://alion.io/developers","usage":{"tier":"crawler","counted_by":"address","units_charged":1,"used_today":1941,"day_limit":5000,"remaining_today":3059,"minute_limit":60,"resets_at":"2026-10-04T00:00:00Z"}}}