Technical Lead Manager

Read this first

You're probably already doing most of this job without the title. People bring designs to you before they build, your review is the one that catches things, and when something breaks late at night you're on the thread whether or not you're on-call. Juniors ask you about their careers even though nobody made that your job.

What we'd like to add is a team that's actually yours, a real say in who joins it, and the authority to decide how your part of the system gets built.

TLM is the step before Engineering Manager and we'd rather say that plainly than pretend otherwise. In 12 to 18 months you're either running a bigger team as an EM or you've worked out that you'd rather go deep, in which case Staff and Principal are open. Either way you won't be stuck.

You'd be running an AI-native team

• You'll build the AI connector framework. The system that generates connectors, tests them, and repairs them on its own when a source system changes underneath.
• AI runs through every workflow, not just the product. Design, review, testing, production debugging. Teaching your team to work this way is part of the job.
• Real scale behind it. 100 billion records and petabytes of data every month, 2,000+ customers, and 150+ source systems that change their APIs without warning.
• The day job changes. Your engineers write specifications, evaluations and guardrails as much as application code, and you'll be judging output that isn't fully predictable. Few engineers in India are paid to do this yet.

What you'll actually be building

What's in it for you

What a good first year looks like

• The framework is generating production connectors, and the quality bar is set by evaluations you designed
• Shipping a new connector takes a fraction of the time it does today, and you can prove it with a number
• You've hired two or three engineers yourself and they're shipping
• At least one person on your team has been promoted

What we're looking for

• 8+ years on backend or distributed systems
• At least a year leading a team, and it doesn't have to have been official. If you're already the person everyone goes to, that counts
• You've run something in production and been there when it broke. On-call, incidents, SLAs
• Strong Java or another JVM language, with Kafka and Kubernetes in production
• Real experience with multi-tenant systems, high availability, or data at volume
• You've built something with LLMs rather than just used a coding assistant. Agents, evaluations, retrieval, prompt systems in production, any of it
• You can explain a complicated system to someone who isn't an engineer
• You've given someone hard feedback and kept the relationship afterwards

About Hevo

Pinterest, Gartner, Shopify, Iceland Air and Jawa Motorcycles run their data on Hevo, along with about two thousand other companies across 40+ countries. We move data from 150+ sources into Snowflake, BigQuery and Databricks without the customer writing code or putting an engineer on it.

Series B, $43 million raised from Sequoia Capital, Chiratae and Qualgro. San Francisco and Bangalore, with the platform built here.

We're not the biggest company you could join. We are one of the few where the engineering is hard, the team is growing fast enough that your scope grows with it, and the person building the system decides how it gets built.

If you've been waiting for someone to hand you a team, apply.