Interested in this AI/ML Engineer role at Exotel?
Apply Now →About This Role
About Exotel
Exotel is a Customer Engagement Platform for businesses, built for interactions handled by both people and AI agents.
We provide the stack behind those interactions - voice, SMS, WhatsApp, RCS and the telephony infrastructure underneath it. Our customers use Exotel to sell, support, collect payments, resolve issues and serve millions of their own customers.
Voice AI is a major part of where this is going.
Our Voice AI agents answer and place phone calls, reason with an LLM, integrate with customer systems and complete tasks. Customers are already running them in production and paying us by the minute.
The market is moving fast. Models are getting better and cheaper, latency is falling and new competitors appear constantly. We need someone who can build the business at that pace.
Build and run Voice AI as a business
Exotel is building the infrastructure behind customer conversations across voice, SMS, WhatsApp, RCS and AI agents.
Voice AI is becoming a major part of this business. Our AI agents answer and place calls, reason using LLMs, connect with customer systems and complete real-world tasks. Customers are already running these agents in production and paying us based on usage.
The market is moving extremely quickly. Models are getting better and cheaper, latency is falling, and competition is increasing.
We are looking for someone who can turn this technology into a large, profitable business.
This is not a traditional Product leadership role.
You will own where we play, what we build, who we sell to, how we price, how we scale, and ultimately whether the business wins.
What You Will Own
1. Strategy – Decide Where We Win
Build a clear view of:
- Which customer segments and use cases are worth pursuing.
- Where Voice AI can create meaningful business value.
- Where we have a genuine competitive advantage.
- Where we are behind the market.
- What we should build, buy, partner for or ignore.
- Which opportunities are attractive enough to invest in.
You will continuously test this thesis through customers, deals, product usage and losses.
The roadmap should be a consequence of this strategy — not the starting point.
2. Product – Build What Customers Will Pay For
Set the product direction for Voice AI.
Decide:
- Which workflows agents should handle end-to-end.
- Which capabilities should become core product features.
- What should remain customer-specific.
- How agents integrate with customer systems.
- When to use the best model versus the most economical model.
- What should be built internally versus sourced externally.
You own the customer experience.
If an agent is slow, unreliable, interrupts unnecessarily, makes mistakes or fails to complete a task — you own the problem.
3. Business – Own the Number
You will own the business outcome.
You will:
- Build the business plan with GTM and Finance.
- Determine where revenue should come from by segment, use case and account.
- Work directly with Sales on strategic opportunities.
- Set pricing and commercial guardrails.
- Decide which deals are worth pursuing.
- Understand why the business is ahead or behind plan.
- Balance growth with profitability.
You should be equally comfortable discussing product metrics and revenue numbers.
4. Economics – Know What Every Interaction Costs
Voice AI economics are fundamentally different from traditional SaaS.
Model choice, inference, routing, caching, infrastructure, latency and architecture directly impact margins.
You will:
- Build and own the unit-economic model.
- Define cost-per-minute targets.
- Understand contribution margin by use case/customer.
- Drive down inference and infrastructure costs.
- Make quality vs latency vs cost trade-offs.
- Decide when higher model cost is justified by higher customer value.
The cost of a minute is a product and business decision.
5. Customers & GTM – Stay Close to the Market
You will spend significant time with customers and prospects.
You should be comfortable:
- Joining strategic customer calls.
- Running important product demonstrations.
- Understanding customer workflows.
- Listening to successful and failed conversations.
- Working with Sales on important opportunities.
- Understanding why we win and lose.
- Turning market feedback into product, pricing and positioning decisions.
The expectation is not to sit behind the product team and wait for customer feedback.
You are expected to be in the market.
6. Build a High-Agency Pod
You will lead a self-contained Voice AI pod comprising:
- Product
- Engineering
- Delivery
- Forward-Deployed Engineering
The pod owns the journey from:
Customer problem → Solution → Production Voice Agent → Measurable outcome
Your job is to give the team direction, raise the quality of decision-making and remove dependencies that slow execution.
You should be comfortable operating with high autonomy and limited structure.
7. Turn Customer Work Into Product
Early customers will require significant hands-on implementation.
Your job is to continuously reduce this dependency.
You will decide:
- What FDEs should build for a customer.
- What should become a reusable product capability.
- What should never be built again.
- Which patterns across customers deserve product investment.
A key measure of success is:
Less custom work → Faster deployment → Better margins → More scalable growth.
What We're Looking For
We care more about what you have actually owned than your previous title.
You have ideally:
- Built and launched an AI product used by paying customers in production.
- Taken a product from 0→1 or early scale and materially influenced its direction.
- Owned revenue, gross margin, P&L or meaningful business metrics.
- Personally made pricing or commercial decisions.
- Built or deeply understood product unit economics.
- Worked directly with Sales and customers on important deals.
- Led cross-functional Product and Engineering teams.
- Operated with significant autonomy and incomplete information.
- Made difficult product/business trade-offs.
- Changed or killed initiatives when evidence showed they were not working.
Particularly relevant experience
- Voice AI / Conversational AI
- LLM applications
- Real-time AI systems
- Speech-to-Text / Text-to-Speech
- LLM inference economics
- Model routing/caching/optimisation
- CPaaS / Contact Centre / Telephony
- Enterprise SaaS
- AI products with usage-based pricing
- Working with Forward-Deployed Engineering / Delivery teams
This Role May Be a Strong Fit If You Are
- A Product leader who has genuinely owned a business, not just a roadmap.
- A GM / Business leader with deep product and technology understanding.
- A Founder / early-stage leader who has built an AI product and taken it to customers.
- An AI product leader who has worked closely with GTM, customers, pricing and unit economics.
This is probably not the right role if:
- Your experience is primarily roadmap execution.
- You have worked on AI technology but haven't shipped products to paying customers.
- You have limited exposure to revenue, pricing or business economics.
- You prefer large, well-defined organisations and established processes.
- You are primarily an engineering leader without product/customer/business ownership.
What Success Looks Like After a Year
Voice AI is a better business because you ran it.
- We know where to compete and where not to.
- The product strategy is clear, and the roadmap follows from it.
- Customers reach production faster.
- Agents complete more of the jobs they are given.
- Conversation quality, latency and reliability improve materially.
- Cost per minute falls, and gross margins improve.
- Custom work decreases as FDE learnings become product capabilities.
- The pod operates with high autonomy.
- Revenue grows, and customers continue to expand their usage.
The numbers should confirm the story:
Revenue growth | Gross margin | Cost per minute | NRR | Time to production | Task completion | FDE hours/customer
Role Details
About This Role
AI/ML Engineers build and deploy machine learning models in production. They work across the full ML lifecycle: data pipelines, model training, evaluation, and serving infrastructure. The role has evolved significantly over the past two years. Where ML Engineers once spent most of their time on model architecture, the job now tilts heavily toward inference optimization, cost management, and integrating LLM capabilities into existing systems. Companies want engineers who can ship production systems, and the experimenter-only role is fading fast.
Day-to-day, you're writing training pipelines, debugging data quality issues, setting up evaluation frameworks, and figuring out why your model performs differently in staging than it did on your dev set. The best ML engineers are obsessive about reproducibility and measurement. They instrument everything. They know that a model is only as good as the data feeding it and the infrastructure serving it.
Across the 10,419 AI roles we're tracking, AI/ML Engineer positions make up 75% of the market. At Exotel, this role fits into their broader AI and engineering organization.
Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.
What the Work Looks Like
A typical week might include: debugging a data pipeline that's silently dropping 3% of training examples, running A/B tests on a new model version, writing documentation for a feature flag system that lets you roll back model deployments, and reviewing a junior engineer's PR for a new evaluation metric. Meetings tend to be cross-functional since ML touches product, engineering, and data teams.
Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.
Skills in Demand for This Role
Python and PyTorch dominate the requirements. Most roles expect experience with cloud platforms (AWS, GCP, or Azure) and familiarity with ML frameworks like TensorFlow or JAX. RAG (Retrieval-Augmented Generation) has become a top-3 skill requirement as companies integrate LLMs into their products. Docker and Kubernetes show up in about a third of postings, reflecting the production focus of the role.
Beyond the core stack, employers increasingly want experience with experiment tracking tools (MLflow, Weights & Biases), feature stores, and vector databases. Fine-tuning experience is valuable but less common than you'd think from reading Twitter. Most production LLM work is RAG and prompt engineering, not fine-tuning. If you have both, you're in a strong position.
Companies that are serious about AI/ML hiring tend to post specific infrastructure details in the job description: the frameworks they use, their model serving stack, their data pipeline tools. Vague postings that just say 'ML experience required' without specifics are often companies that haven't figured out what they need yet.
Compensation Benchmarks
AI/ML Engineer roles pay a median of $213,800 based on 16,346 positions with disclosed compensation. Mid-level AI roles across all categories have a median of $193,200.
Across all AI roles, the market median is $214,834. Top-quartile compensation starts at $266,000. The 90th percentile reaches $321,730. For comparison, the highest-paying categories include AI Safety ($274,500) and Research Engineer ($252,000). By seniority level: Entry: $114,400; Mid: $193,200; Senior: $230,000; Director: $272,100; VP: $235,000.
Exotel AI Hiring
Exotel has 1 open AI role right now. They're hiring across AI/ML Engineer. Based in Bengaluru, Karnataka, India.
Location Context
Across all AI roles, 6% (580 positions) offer remote work, while 9,776 require on-site attendance. Top AI hiring metros: New York (3,785 roles, $222,480 median); San Francisco (3,262 roles, $261,300 median); Los Angeles (1,896 roles, $210,000 median).
Career Path
Common paths into AI/ML Engineer roles include Data Scientist, Software Engineer, Research Engineer.
From here, career progression typically leads toward ML Architect, AI Engineering Manager, Principal ML Engineer.
The fastest path into ML engineering is through software engineering with a self-directed ML education. A CS degree helps, but production engineering skills matter more than academic credentials. Build something that works, deploy it, and measure it. That portfolio project is worth more than a Coursera certificate. For career growth, the fork comes around the senior level: go deep on technical complexity (staff/principal track) or move into managing ML teams.
What to Expect in Interviews
Expect system design questions around ML pipelines: how you'd build a training pipeline for a specific use case, handle data drift, or design A/B testing infrastructure for model deployments. Coding rounds typically involve Python, with emphasis on data manipulation (pandas, numpy) and algorithm implementation. Take-home assignments often ask you to build an end-to-end ML pipeline from raw data to deployed model.
When evaluating opportunities: Companies that are serious about AI/ML hiring tend to post specific infrastructure details in the job description: the frameworks they use, their model serving stack, their data pipeline tools. Vague postings that just say 'ML experience required' without specifics are often companies that haven't figured out what they need yet.
AI Hiring Overview
The AI job market has 10,419 open positions tracked in our dataset. By seniority: 117 entry-level, 4,975 mid-level, 3,840 senior, and 1,487 leadership roles (Director, VP, C-Level). Remote roles make up 6% of the market (580 positions). The remaining 9,776 roles require on-site or hybrid attendance.
The market median for AI roles is $214,834. Top-quartile compensation starts at $266,000. The 90th percentile reaches $321,730. Highest-paying categories: AI Safety ($274,500 median, 90 roles); Research Engineer ($252,000 median, 580 roles); AI Engineering Manager ($250,811 median, 72 roles).
Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.
The AI Job Market Today
The AI job market spans 10,419 open positions across 16 role categories. The largest categories by volume: AI/ML Engineer (7,849), AI Product Manager (516), AI Software Engineer (513). These three account for the majority of open positions, though smaller categories often have higher per-role compensation because of specialized skill requirements.
The seniority mix tells a story about where AI teams are in their maturity. Entry-level roles (117) are outnumbered by mid-level (4,975) and senior (3,840) positions, reflecting that most companies are past the 'build a team from scratch' phase and need experienced engineers who can ship production systems. Leadership roles (Director, VP, C-Level) total 1,487 positions, representing the bottleneck between technical execution and organizational strategy.
Remote work availability sits at 6% of all AI roles (580 positions), with 9,776 requiring on-site or hybrid attendance. The remote share has stabilized after the post-pandemic correction. Senior and specialized roles (Research Scientist, ML Architect) are more likely to be remote-eligible than entry-level positions, partly because experienced hires have more negotiating power and partly because these roles require less hands-on mentorship.
AI compensation is structured in clear tiers. The market median sits at $214,834. Top-quartile roles start at $266,000, and the 90th percentile reaches $321,730. These figures include base salary with disclosed compensation. Total compensation (including equity, bonuses, and sign-on) runs 20-40% higher at companies that offer those components.
Category matters for compensation. AI Safety roles lead at $274,500 median, while Prompt Engineer roles sit at $140,000. The spread between highest and lowest-paying categories reflects the premium on specialized technical skills versus broader analytical roles.
The most in-demand skills across all AI postings: Python (2,350 postings), Aws (1,173 postings), Azure (1,030 postings), Rag (986 postings), Gcp (714 postings), Pytorch (649 postings), Kubernetes (583 postings), Claude (581 postings). Python dominates, appearing in the vast majority of role descriptions regardless of category. Cloud platform experience (AWS, GCP, Azure) is the second most common requirement. The newer entrants to the top skills list (RAG, vector databases, LLM APIs) reflect the shift from traditional ML toward generative AI applications.
Frequently Asked Questions
Get Weekly AI Career Intelligence
Salary data, skills demand, and market signals from 16,000+ AI job postings. Every Monday.