Description:

The job, honestly

We're building a small team of engineers (2-3 people) where each person owns an entire product. Not a feature. Not a module. The product from architecture to deployment to the thing your users touch.

The catch: you'll do it with agentic coding tools as your primary workflow. Claude Code, Cursor, AI-assisted debugging, automated code generation not as a side experiment, but as how you work every day. If you're already shipping code this way, you know exactly what

we mean. If you think AI tools are a gimmick, this isn't the role.

We're the AI team at CarDekho Group, one of India's largest auto-tech platforms. You'll report to the Head of AI and work alongside a team that's been building production LLM systems at scale.

You, probably:

- 2-5 years of experience building and shipping software. You've owned things in production and lost sleep over them.

- Full-stack capable. You can go from a Postgres schema to a React component to a deployment pipeline in the same afternoon. You don't need to be an expert in everything the tools fill gaps but you need to be unafraid of any layer of the stack.

- Already living in the AI-augmented workflow. You use Claude Code, Cursor, Copilot, or similar tools daily not for autocomplete, but for real architectural work. You know when to trust the output and when to throw it away.

- Stack-flexible. We don't care if youre strongest in Python, TypeScript, Go, or Rust.

- Products dictate stacks, not resumes. You should be comfortable picking up whatever the problem demands.

- Product-minded. You think about what to build, not just how. You have opinions about UX. You push back on specs that dont make sense. Youd rather ship something imperfect than design something perfect.

- Self-directed. This is a remote team with high trust and low ceremony. If you need someone to assign you Jira tickets every morning, this wont work. If you thrive when given a problem and left alone to solve it, keep reading.

What you wont find here :

- A 15-person team where you own one microservice

- Mandatory DSA rounds in the interview

- 3+ years of React as a hard requirement

- A manager who reviews every PR

- The phrase fast-paced environment used unironically

What we care about in the interview :

Well give you a real problem and a time-box. Youll solve it however you want AI tools encouraged, copy-paste from Stack Overflow encouraged, whatever gets it done well. We want to see how you think, how you use your tools, and what you ship not whether you can reverse a linked list on a whiteboard.