New opportunity

Senior Developer - Voice AI

United Airlines · Chicago, United States

About this role

United Airlines seeks a Senior Developer - Voice AI in Chicago to design and build scalable AI agents for customer-service automation across voice, chat and future channels. The role focuses on high-volume retail customer requests, including peak demand and irregular operations, with the goal of faster resolution and reduced wait times.

Responsibilities

  • Design, develop and deploy AI agents and agentic workflows using LangChain, LangGraph or similar frameworks; build conversational AI and voice automation capabilities integrated with customer-service channels.
  • Implement agent orchestration, prompt engineering and retrieval-augmented generation patterns. Write and maintain documented Python, TypeScript and .NET/C# code, and deploy solutions at scale using cloud technologies, preferably AWS.
  • Translate business and user requirements into designs and technical specifications with AI/ML engineers, data scientists, product teams, end users and vendor contractors. Prototype, test, debug and support agents; troubleshoot code, assess emerging AI technologies and contribute to architecture, security, code-quality and responsible-AI practices. Participate in the full Agile development lifecycle.

Minimum qualifications: A bachelor's degree and at least 3 years of software design and development experience. Strong Python proficiency; experience with TypeScript, .NET/C#, AWS implementation and cloud automation development tools; and knowledge of object-oriented design, application development, API development and integration, SQL, NoSQL and design patterns. Applicants must be legally authorized to work for any US employer without sponsorship. A degree field in computer science, engineering, information systems or a related area is preferred.

Preferred qualifications

At least 2 years building AI agents, conversational AI or voice automation; hands-on LangChain or LangGraph experience; familiarity with generative AI, LLMs, prompt engineering, RAG and vector databases. Experience with AWS Lambda, Step Functions, API Gateway, S3, DynamoDB, ECS, EC2 and CloudWatch; event-driven and asynchronous architectures; DevOps, CI/CD, infrastructure as code, A/B testing, AI governance, enterprise applications, contact-center platforms and Agile/Scrum is valued. Airline or travel experience is a plus.

The position is full-time at 40 hours per week. Base pay is $112,480.00–$146,540.00, with eligibility for bonus and/or long-term incentives. Listed potential benefits include health coverage, retirement benefits, paid leave and flight privileges.

For full details about this role, click “Apply on company site” to view the employer’s original posting.

Skills for this role

AI agentsAgentic workflowsConversational AIVoice automationLangChainLangGraphPythonTypeScript.NETC#Prompt engineeringRetrieval-augmented generation (RAG)Generative AILarge Language Models (LLMs)AWSAPI developmentAPI integrationObject-oriented designSQLNoSQLVector databasesAWS LambdaAWS Step FunctionsAmazon API GatewayAmazon S3Amazon DynamoDBAmazon ECSAmazon EC2Amazon CloudWatchEvent-driven architecture principles and patterns might be too long? No.

Your skill match

Checking your profile…

YOUR NEXT STEP

Get interview-ready for this role

A focused preparation guide, built around this job’s responsibilities and requirements.

✦ AI-generated guide
Preparation suggestions, not the employer’s actual interview questions. Always check the original posting for current requirements.
01

Understand the role

What matters most

  • Build production AI agents

    The posting calls for independently designing, developing and deploying multiple AI agents and agentic workflows using LangChain, LangGraph or similar frameworks. Prepare to explain design decisions from prototype through deployment and support.

  • Automate customer journeys across channels

    The role targets high-volume customer retail requests across voice, chat and future channels, especially during peak demand and irregular operations. Prepare to discuss how an agent would integrate with customer-service channels and support fast resolution.

  • Engineer reliable orchestration and retrieval

    The duties include optimizing agent orchestration, prompts and retrieval-augmented generation, alongside maintainable Python, TypeScript and .NET/C# code. Prepare a concrete account of how you would test, debug and document these components.

  • Own architecture and cross-functional delivery

    The developer contributes to architecture, security, code quality and responsible AI while translating requirements with product, AI/ML, data and end-user teams into specifications. Prepare to explain how you would make and communicate technical trade-offs through the Agile lifecycle.

Likely challenges to think through

  • Scaling through demand spikes

    Likely preparation challenge, not a confirmed problem: peak demand and irregular operations could strain response times and reliability. Be ready to reason about capacity, asynchronous work and monitoring while preserving a usable voice experience.

  • Balancing autonomy with trustworthy answers

    Likely preparation challenge, not a confirmed problem: agentic workflows may need to resolve requests quickly without producing unsupported or unsafe responses. Prepare to discuss retrieval quality, testing, security and responsible-AI safeguards, including when an agent should not proceed autonomously.

  • Keeping channels and systems aligned

    Likely preparation challenge, not a confirmed problem: voice and chat automation must connect to customer-service channels while requirements evolve across teams. Prepare to describe API boundaries, shared workflow behavior and how end-user feedback would shape prototypes without assuming a particular existing platform.

03

Practice your answers

Technical practice

How would you design an AI agent workflow for a customer-service request?

What to coverThe posting calls for scalable agents and agentic workflows using LangChain, LangGraph, or similar frameworks. Suggested preparation: explain how you would define workflow steps, coordinate tool calls, manage state, and decide when the agent should stop or seek assistance.

How would you keep customer-service automation responsive during peak demand or irregular operations?

What to coverThe role explicitly addresses high-volume customer requests, including irregular operations. Suggested preparation: discuss capacity, latency, graceful degradation, and the trade-off between faster responses and reliable resolution.

How would you integrate a conversational agent across voice and chat channels?

What to coverThe posting calls for voice automation and conversational AI integrated with customer-service channels. Suggested preparation: describe what conversation state and service APIs could be shared, what differs by channel, and how you would test the customer experience.

How would you design and evaluate a retrieval-augmented response?

What to coverRAG patterns, prompt engineering, and vector databases appear in the posting. Suggested preparation: explain retrieval and prompt design, then compare responses for relevance, grounding, latency, and cases where retrieved information is insufficient.

How would you structure maintainable agent code and its service integrations?

What to coverThe role calls for documented Python, TypeScript, and .NET/C# code, plus API integration, object-oriented design, and SQL and NoSQL knowledge. Suggested preparation: explain module boundaries, API contracts, data-store choices, and how you would test integrations without tightly coupling the agent to a channel.

How would you choose an AWS deployment approach for an agent workflow?

What to coverAWS implementation is required, while Lambda, Step Functions, API Gateway, S3, DynamoDB, ECS, EC2, and event-driven processing are listed as preferred experience. Suggested preparation: compare appropriate managed and compute options against workflow duration, asynchronous work, scaling, and operational complexity rather than assuming one prescribed stack.

How would you diagnose an agent that starts giving poor answers or failing requests?

What to coverThe posting includes testing, debugging, production support, and analyzing code to find errors. Suggested preparation: walk through separating retrieval, prompt, orchestration, API, and application-code failures, including what you would log or measure while protecting customer information.

What safeguards would you build into a customer-facing AI agent?

What to coverSecurity protocols, code quality, responsible AI, and AI governance are named in the posting. Suggested preparation: discuss access controls, sensitive-data handling, unsafe or unsupported responses, and how you would verify safeguards without claiming a particular United policy.

How would you determine whether a new agent or prompt improves customer-service outcomes?

What to coverThe role emphasizes faster resolution and reduced wait times; A/B testing and experimentation are preferred experience. Suggested preparation: propose outcome and quality measures, compare alternatives, and explain how you would detect improvements that come at the expense of accuracy or customer experience.

How would you take an agent change from prototype to maintainable release?

What to coverThe posting covers prototyping, the full Agile lifecycle, documentation, and deployment; CI/CD and infrastructure as code are preferred. Suggested preparation: outline testing, review, deployment, monitoring, and rollback considerations, distinguishing posting requirements from your proposed approach.

Behavioural practice

Tell me about a time you translated an ambiguous user need into a technical specification.

What to coverThe role involves analyzing user needs and writing specifications from business requirements. Suggested preparation: use a real situation/action/result example showing how you clarified the need, made design decisions, and checked that the result met it.

Describe a time you refined a solution after feedback from end users.

What to coverThe posting calls for collaborating with end users to prototype, refine, test, and debug agents. Suggested preparation: give a real situation/action/result example that distinguishes the feedback, your changes, and the observed outcome.

Tell me about a time you made a technical trade-off while working independently.

What to coverThis senior role calls for independently building solutions and contributing to architectural decisions. Suggested preparation: use a real situation/action/result example explaining the alternatives, your reasoning, how you communicated the decision, and its result.

Describe a difficult defect you investigated and supported through resolution.

What to coverTroubleshooting code and supporting automation workflows are stated responsibilities. Suggested preparation: give a real situation/action/result example covering diagnosis, the fix or mitigation, and what you did to prevent recurrence.

Tell me about coordinating delivery across teams with different priorities.

What to coverThe posting names AI/ML engineers, data scientists, product teams, employees, and vendor contractors as collaborators. Suggested preparation: use a real situation/action/result example showing how you aligned requirements and responsibilities, resolved a disagreement, and delivered an outcome.

02

Sharpen your knowledge

Topics to prepare

  • Agent orchestration and scale

    The role calls for scalable AI agents and agentic workflows for high-volume customer requests, including peak demand and irregular operations. Suggested revision exercise: diagram an agent’s decision points, failure paths and handoffs for a surge in service requests.

  • Voice and chat journeys

    The posting calls for conversational AI and voice automation integrated with customer-service channels. Suggested revision exercise: map one customer request through voice and chat, noting where context must carry between turns or channels.

  • Application and API design

    Object-oriented design, design patterns, API development and integration are stated qualifications. Suggested revision exercise: outline service boundaries and API contracts for an agent that needs customer-service information, including how integration errors are handled.

  • Prompting and retrieval

    Prompt engineering and RAG are responsibilities; LLM and vector-database familiarity is preferred. Suggested revision exercise: compare a prompt-only answer with a retrieval-grounded answer, then identify how to handle missing or conflicting retrieved information.

  • Cloud and asynchronous architecture

    AWS implementation is a minimum qualification; event-driven and asynchronous architectures are preferred. Suggested revision exercise: sketch how an agent request could be processed during a demand spike, identifying scaling, retry and observability considerations.

  • Security and responsible AI

    The role calls for adherence to security protocols and responsible-AI principles. Suggested revision exercise: review a proposed customer-service agent flow for inappropriate data exposure, unsupported answers and points needing a safe fallback.

Skills to revise

  • Build a Python agent workflow

    Strong Python proficiency and agent development are stated in the posting. Suggested exercise: implement and document a small Python agent workflow using LangChain, LangGraph or a similar framework, with a tool call and a recoverable error path.

  • Implement channel-facing APIs

    The posting asks for TypeScript and .NET/C# development and strong API integration knowledge. Suggested exercise: implement a small request-and-response endpoint in each language and test how each reports an upstream service failure.

  • Practice AWS deployment and monitoring

    AWS implementation is required; Lambda, Step Functions, API Gateway and CloudWatch are among the preferred services. Suggested exercise: build a small deployment with relevant listed services and inspect logs from a failed request. This service combination is a preparation suggestion, not a stated architecture.

  • Work with SQL and NoSQL data

    Knowledge of SQL and NoSQL databases is a minimum qualification. Suggested exercise: model a conversation’s request and status data in both forms, write a query or lookup for its current state, and explain the trade-offs.

  • Test and debug customer-service agents

    Prototyping, testing, debugging and supporting agents with end users are stated responsibilities. Suggested exercise: create tests for ambiguous requests, unavailable information and peak-load failures; trace one failure to code and document the fix.

  • Write a technical specification

    The role includes translating business requirements into technical specifications with product, AI/ML and other collaborators. Suggested exercise: turn a stated customer-service intent into a brief specification covering the user flow, API dependencies, failure handling and testable acceptance criteria.

04

Your preparation checklist

  • Build a requirements evidence sheet

    List factual examples for the posted minimum qualifications: degree, software design and development experience, Python, TypeScript, .NET/C#, AWS, cloud automation, APIs, object-oriented design, SQL and NoSQL. Note the stated work-authorization requirement separately; mark preferred experience as preferred.

  • Prepare an agent project walkthrough

    If you have a relevant project, outline your own design and implementation decisions, agent orchestration, prompts or RAG, testing, outcomes and lessons learned. Distinguish what you built from team contributions; do not invent metrics.

  • Practice a peak-demand design exercise

    Sketch a hypothetical voice-and-chat agent for a high-volume customer request during irregular operations. Show intent handling, integrations, failure paths and when a customer would be routed to another service channel; explain how the design could scale.

  • Select a code and integration example

    Prepare to explain a Python implementation and any relevant TypeScript or .NET/C# work. Bring a concise account of API contracts, design patterns, database choices, tests, debugging and documentation.

  • Draw a deployment and operations diagram

    Show how you would deploy, automate and monitor an agent on AWS, including capacity and asynchronous-work tradeoffs. Label services such as Lambda, Step Functions or CloudWatch as design options rather than claiming United uses them.

  • Define quality and responsible-AI checks

    Draft a small test plan for response accuracy, retrieval failures, security and customer-impacting errors. Explain what you would measure before release and how you would investigate failures; A/B testing is listed as preferred experience.

  • Rehearse a cross-functional delivery story

    Use a real example, if available, to show how you turned user or business needs into specifications, refined a prototype with stakeholders and supported it through an Agile development lifecycle.

  • Write targeted questions for the employer

    Ask which customer intents and channels are priorities, how success is measured during peak demand and irregular operations, and what constraints shape agent architecture, integrations and responsible-AI review.

AI-generated from the job information · Prepared Oct 1, 2026 (UTC)Useful preparation, not a guarantee of eligibility or an offer.

Availability last checked: Nov 4, 2026. Status can change after a check; confirm on the employer’s website. Report an issue · Our checking policy

KEEP EXPLORING

Similar AI jobs

Related skills and specializations in United States. Matched to this role, not your profile.

Explore more jobs
Finding similar opportunities…