Back to jobs

AI Engineer - Voice & Agentic Systems

Pay
Pay not listed
Work setting
Remote — work setting source
Work setup in the employer’s posting: Remote
From the employer’s posting
Employment
Full-time — employment source
Employment type in the employer’s posting: Full time
From the employer’s posting
Apply at Weya AI

Posting record

Report an error
Status in our records
Live
First seen by us
Oct 30, 202622 days ago
Recorded sightings
10
Last seen by us
Nov 21, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 22

Up longer than most. Similar jobs usually come down between day 1 and day 15.

From 1,368 similar postings that came down. Coming down is not always a hire.

Weya AI is hiring

1 open job

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

See how this role fits your experience

Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • Python
  • AWS
  • Azure
  • Docker
  • GCP
  • Kafka
  • Kubernetes
  • Redis
  • FastAPI
  • Go
  • PostgreSQL
Where the posting names them
Job Title: AI Engineer (Voice & Agentic Systems) Location: Noida Working Mode: Remote Type: Full-time Experience: 2+ Years (shipping LLM agents) About the Company: weya builds AI automations - Voice, video and WhatsApp agents that banks, lenders and insurers put in front of their customers. Our agents handle collections, onboarding, renewals, KYC follow-ups and support calls at scale, across India, the Middle East & Africa, Australia and the US. We're a small team of 11-15 people. Every engineer ships to production, talks to customers, and owns real outcomes. If an agent mishandles a loan call, it costs a client money and trust, so we build for reliability first. About the Role: You'll design, build and run the agents that talk to our clients' customers: LLM orchestration with LlamaIndex/LangChain, FastAPI services behind them, and real-time voice pipelines wired into telephony providers. You own an agent end to end, from the first prompt to the 10,000th concurrent call. What You'll Do? Build agentic workflows with LlamaIndex and LangChain: tool calling, RAG over policy and loan documents, multi-step reasoning, and guardrails for regulated conversations. Design and run FastAPI services that serve agents in real time: async endpoints, WebSockets, webhooks, background tasks and clean API contracts. Build low-latency voice agents end to end: STT, LLM, TTS, voice activity detection, barge-in/interruption handling, and turn-taking. Integrate and maintain telephony providers (e.g. Twilio, Plivo, Exotel, Vonage, SIP trunks): inbound/outbound calls, call transfer, recordings, DTMF, and media streaming. Engineer for failure: provider outages, dropped calls, LLM timeouts, partial transcripts, retries and idempotency, so one bad dependency never takes down a campaign. Write tests that catch problems before clients do: unit and integration tests, simulated calls, load tests, and regression suites for agent behaviour. Instrument everything: latency per turn, call success rates, cost per call, and alerts that fire before a client notices. Work directly with FDEs and clients to turn real call transcripts into better agents. Requirements What We're Looking For? (Non-Negotiable) Agentic frameworks: shipped production agents with LlamaIndex and/or LangChain (or LangGraph), including tool use, memory and RAG. Not just notebooks. FastAPI: extensive experience building async Python services with FastAPI, Pydantic, WebSockets and background workers, under real traffic. Voice agents: built at least one voice agent that handled real customer calls, with hands-on work on STT/TTS providers (e.g. Deepgram, ElevenLabs, Azure, Google) and latency tuning. Telephony: integrated two or more telephony providers or SIP setups, and can explain how audio flows from a phone network to your code and back. Production mindset: you think about concurrency, rate limits, timeouts, retries and edge cases before writing the happy path, and you write tests for them. Debugging under pressure: comfortable reading logs, call recordings and traces to find why a call failed. Clear written English; able to explain a technical trade-off to a client. Good to have (Bonus Points): Real-time voice frameworks such as LiveKit Agents or Vapi, or speech-to-speech models. Go for high-throughput services alongside Python. Multilingual voice work, especially Hindi, Hinglish, Arabic or other Indic languages. Experience in BFSI or other regulated domains: consent, call recording rules, PII handling, audit trails. LLM evaluation: automated scoring of agent conversations, prompt regression testing. WhatsApp Business API or video agent experience. Docker, Kubernetes, AWS/GCP, Redis, Postgres, and queues like Kafka or RabbitMQ. Benefits Get Real Experience on "What Success looks like?" To apply: send your CV at hr@weya.ai, GitHub or a demo of a voice agent you built, and one paragraph on the hardest telephony problem you've solved. Open question: application email or link.

Your next step

Complete your application on weya.zohorecruit.in. The employer’s form will show what is required.

Already applied? Track this application

Job description

View original posting ↗

Job Title: AI Engineer (Voice & Agentic Systems) Location: Noida Working Mode: Remote Type: Full-time Experience: 2+ Years (shipping LLM agents) About the Company: weya builds AI automations - Voice, video and WhatsApp agents that banks, lenders and insurers put in front of their customers. Our agents handle collections, onboarding, renewals, KYC follow-ups and support calls at scale, across India, the Middle East & Africa, Australia and the US. We're a small team of 11-15 people. Every engineer ships to production, talks to customers, and owns real outcomes. If an agent mishandles a loan call, it costs a client money and trust, so we build for reliability first. About the Role: You'll design, build and run the agents that talk to our clients' customers: LLM orchestration with LlamaIndex/LangChain, FastAPI services behind them, and real-time voice pipelines wired into telephony providers. You own an agent end to end, from the first prompt to the 10,000th concurrent call. What You'll Do? Build agentic workflows with LlamaIndex and LangChain: tool calling, RAG over policy and loan documents, multi-step reasoning, and guardrails for regulated conversations. Design and run FastAPI services that serve agents in real time: async endpoints, WebSockets, webhooks, background tasks and clean API contracts. Build low-latency voice agents end to end: STT, LLM, TTS, voice activity detection, barge-in/interruption handling, and turn-taking. Integrate and maintain telephony providers (e.g. Twilio, Plivo, Exotel, Vonage, SIP trunks): inbound/outbound calls, call transfer, recordings, DTMF, and media streaming. Engineer for failure: provider outages, dropped calls, LLM timeouts, partial transcripts, retries and idempotency, so one bad dependency never takes down a campaign. Write tests that catch problems before clients do: unit and integration tests, simulated calls, load tests, and regression suites for agent behaviour. Instrument everything: latency per turn, call success rates, cost per call, and alerts that fire before a client notices. Work directly with FDEs and clients to turn real call transcripts into better agents. Requirements What We're Looking For? (Non-Negotiable) Agentic frameworks: shipped production agents with LlamaIndex and/or LangChain (or LangGraph), including tool use, memory and RAG. Not just notebooks. FastAPI: extensive experience building async Python services with FastAPI, Pydantic, WebSockets and background workers, under real traffic. Voice agents: built at least one voice agent that handled real customer calls, with hands-on work on STT/TTS providers (e.g. Deepgram, ElevenLabs, Azure, Google) and latency tuning. Telephony: integrated two or more telephony providers or SIP setups, and can explain how audio flows from a phone network to your code and back. Production mindset: you think about concurrency, rate limits, timeouts, retries and edge cases before writing the happy path, and you write tests for them. Debugging under pressure: comfortable reading logs, call recordings and traces to find why a call failed. Clear written English; able to explain a technical trade-off to a client. Good to have (Bonus Points): Real-time voice frameworks such as LiveKit Agents or Vapi, or speech-to-speech models. Go for high-throughput services alongside Python. Multilingual voice work, especially Hindi, Hinglish, Arabic or other Indic languages. Experience in BFSI or other regulated domains: consent, call recording rules, PII handling, audit trails. LLM evaluation: automated scoring of agent conversations, prompt regression testing. WhatsApp Business API or video agent experience. Docker, Kubernetes, AWS/GCP, Redis, Postgres, and queues like Kafka or RabbitMQ. Benefits Get Real Experience on "What Success looks like?" To apply: send your CV at hr@weya.ai, GitHub or a demo of a voice agent you built, and one paragraph on the hardest telephony problem you've solved. Open question: application email or link.

Demand for AI Engineer roles

New AI Engineer postings at the employers we follow are up 340% over the last 6 weeks compared with the 6 before.

Weekly new AI Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 78, the most 803, and the latest week had 438.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under AI Engineer, by the work the posting describes.

AI engineers build products on top of AI models that already exist, most often large language models: they connect a model to a company's data and tools and ship the assistants, agents and search features people use.

Postings ask for strong Python or TypeScript, experience with model APIs, retrieval and agent frameworks, and ways to test whether the model's answers are good enough.

An ML engineer trains and serves models; an AI engineer usually starts from a model someone else trained and builds the product around it, though titles often mix the two.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Location not supplied.

This passage needs a closer read in the full description.

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.