AI Enablement Lead
- Location Bengaluru, Karnataka, India (HO_IBC)
- Experience 8-12 yrs
- Job type Full-time
- Posted 12 Oct 2026
You will be taken to Ather Bengaluru’s own careers page to apply. Job ID AE5398.
Job description
You’ll be our: AI Enablement Lead You’ll be based at: IBC, Bangalore You’ll be aligned with: Head of AI You’ll be a member of: AI Enablement Team
What You’ll do at Ather: Ather builds India’s smart electric scooters end to end — the vehicle, the software that runs it, the factory that makes it, and the charging network that powers it. We are a fast-growing company, and we are now going all-in on becoming AI-native — which at a company this varied means a lot of very different things. Buying the tools was the easy part. This role owns the hard part: making AI the way work actually gets done, team by team. ● Own the adoption charter: Work with every part of the business — Manufacturing, Quality and Supply Chain through to Engineering, Design, Finance, HR and Customer-facing teams — and make AI a daily habit in each of them, not a tool people merely have access to. ● Own the impact: Pick the handful of workflows that actually decide cost, quality or speed at Ather — a quality check, a demand plan, a month-end close, a customer conversation — and enable the end users to improve those processes with AI. Prove the gain in the function's own numbers. ● Build and grow the AI Enablement function: You will be the first person in the team. Decide the direction to grow the team, catering to the unique requirements of Ather. Recruit, train and hold accountable the champions across the org, and run the operating rhythm that keeps it alive — clinics, deep-dives, forums, hackathons. ● Own how proven workflows spread — and what's missing. Stay close enough to every function to know not just what's working, but what's still broken: where teams are stuck without the right tool, guide, or guardrail. Turn those gaps into centrally-owned assets — policies, playbooks, tooling standards, approval processes — so functions aren't each solving the same problem their own way. Package what already works into recipes anyone can pick up, and build what's missing before five different teams improvise five different answers to it.