Back to jobs

AI Engineer

Pay
Pay not listed
Work setting
Not stated
Employment
Not stated

What you’ll work on

Full posting

This is the senior build role for Nexperia's agent engineering practice in Bangalore.

You work closely with the Integration Architect on how agents connect into IDEs and internal systems, and with the MLOps/eval function on the quality bar an agent has to clear before it ships.

  • Design agent architecture: reasoning loops, planning, tool-calling and memory/context management.

  • Own the build of user-facing surfaces for Copilot-style products: chat UI, IDE extensions and CLI tools.

  • Build multi-step orchestration: task decomposition, tool selection and error recovery.

From the employer’s posting
This is the senior build role for Nexperia's agent engineering practice in Bangalore. You own the architecture of the agents themselves — reasoning, planning, tool-calling and memory — and you own the surfaces people actually use them through: chat UI, IDE extensions, CLI tools and the APIs behind them.
You work closely with the Integration Architect on how agents connect into IDEs and internal systems, and with the MLOps/eval function on the quality bar an agent has to clear before it ships.
Architect and orchestrate agents Design agent architecture: reasoning loops, planning, tool-calling and memory/context management. Build multi-step orchestration: task decomposition, tool selection and error recovery.
Ship end-to-end agent products Own the build of user-facing surfaces for Copilot-style products: chat UI, IDE extensions and CLI tools. Build the backend APIs that connect those surfaces to agent and LLM services, including streaming responses, session state and context handling.
Design agent architecture: reasoning loops, planning, tool-calling and memory/context management. Build multi-step orchestration: task decomposition, tool selection and error recovery. Partner with the Integration Architect on connecting agents to IDEs and internal systems.

What you’ll bring

All qualifications

Core experience

  • 1-6 years hands-on building LLM or agent systems.
  • Experience with CI/CD tooling (GitHub Actions, Jenkins or similar), cloud infrastructure (AWS, Azure or GCP) and containers (Docker, Kubernetes).
  • Strong Python and/or TypeScript; comfortable owning a service end to end.
  • Experience or interest in developer enablement or platform engineering — documentation, SDKs, or internal tooling built for non-specialist users, not just for your own team.

Preferred experience

  • Familiarity with enterprise AI/copilot platforms and cloud-native model ecosystems — Microsoft Copilot and Copilot Studio, Azure AI Foundry (model catalog, deployments, and orchestration), and AWS model configuration (Bedrock model access, inference profiles/settings) is a plus.
  • Experience in the manufacturing industry, preferably semiconductor, is a plus.
Qualification wording
1-6 years hands-on building LLM or agent systems.
Experience with CI/CD tooling (GitHub Actions, Jenkins or similar), cloud infrastructure (AWS, Azure or GCP) and containers (Docker, Kubernetes).
Strong Python and/or TypeScript; comfortable owning a service end to end.
Experience or interest in developer enablement or platform engineering — documentation, SDKs, or internal tooling built for non-specialist users, not just for your own team.
Familiarity with enterprise AI/copilot platforms and cloud-native model ecosystems — Microsoft Copilot and Copilot Studio, Azure AI Foundry (model catalog, deployments, and orchestration), and AWS model configuration (Bedrock model access, inference profiles/settings) is a plus.
Experience in the manufacturing industry, preferably semiconductor, is a plus.
Apply at Nexperia

Posting record

Report an error
Status in our records
Live
First seen by us
Oct 26, 202626 days ago
Recorded sightings
9
Last seen by us
Nov 16, 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 26

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

At Nexperia, jobs usually come down by about day 57.

From 1,376 similar postings that came down, and 8 of Nexperia’s. Coming down is not always a hire.

Nexperia is hiring

7 open jobs

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

  • Takes jobs down at a usual pace
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
  • TypeScript
  • AWS
  • Azure
  • Datadog
  • Docker
  • GCP
  • Grafana
  • Kubernetes
  • React
  • Node.js
Where the posting names them
- 1-6 years hands-on building LLM or agent systems. - Strong Python and/or TypeScript; comfortable owning a service end to end. - Hands-on with agent frameworks or SDKs (Claude Agent SDK/MCP, LangGraph, AutoGen) or custom orchestration.
Valuable extras - Strong in React/TypeScript for frontend work, and Node.js or Python for backend work. - Experience with CI/CD tooling (GitHub Actions, Jenkins or similar), cloud infrastructure (AWS, Azure or GCP) and containers (Docker, Kubernetes).
- Comfortable designing REST, GraphQL and streaming/WebSocket APIs, and familiar with LLM streaming APIs (SSE/WebSockets) and token-by-token rendering. - Familiarity with enterprise AI/copilot platforms and cloud-native model ecosystems — Microsoft Copilot and Copilot Studio, Azure AI Foundry (model catalog, deployments, and orchestration), and AWS model configuration (Bedrock model access, inference profiles/settings) is a plus. Valuable extras
- Strong in React/TypeScript for frontend work, and Node.js or Python for backend work. - Experience with CI/CD tooling (GitHub Actions, Jenkins or similar), cloud infrastructure (AWS, Azure or GCP) and containers (Docker, Kubernetes). - Observability tooling — Datadog, Prometheus/Grafana, or LLM-specific tools like LangSmith or Arize — and familiarity with LLMOps practices: prompt versioning, eval pipelines, cost tracking.
- Experience with CI/CD tooling (GitHub Actions, Jenkins or similar), cloud infrastructure (AWS, Azure or GCP) and containers (Docker, Kubernetes). - Observability tooling — Datadog, Prometheus/Grafana, or LLM-specific tools like LangSmith or Arize — and familiarity with LLMOps practices: prompt versioning, eval pipelines, cost tracking. - Working knowledge of auth and session management, and awareness of security and compliance considerations for AI systems.

Your next step

Complete your application on nexperia.wd3.myworkdayjobs.com. The employer’s form will show what is required.

Applying through Workday

  • You create an account with each employer before you can upload anything. Every Workday employer has its own account, so one sign-up doesn’t carry over.
  • “Autofill with Resume” comes right after sign-in, before the My Information and My Experience steps. Check every field it fills in those steps, since that’s what recruiters see.
  • Your application status lives in that employer’s Candidate Home, under the same sign-in.

Already applied? Track this application

Job description

View original posting ↗

Nexperia is a world-class company in semiconductor development and in-house production. We form a global network of talent, with passion and performance, perseverance and professionalism. Join TeamNexperia and become part of a leading company that supports, rewards and challenges you equally, in a dynamic environment, working for world-class results. Talk to us today and learn your true capabilities in an energetic company where you will develop and thrive, the Efficiency Company – Nexperia.



About the team

Digital Enablement is Nexperia's fast-track enabler of AI & Digital use-cases and platform enablement. We operate as one global practice across Nijmegen, Hamburg, Kuala Lumpur, Seremban and Bangalore, covering digital strategy, cloud and infrastructure, digital factory and enterprise, data, AI and integration.

Bangalore is where we build and ship the agentic systems that put Nexperia's AI patterns in front of real users: copilots, IDE tooling and internal automation that engineers across the company touch every day.


About the role

This is the senior build role for Nexperia's agent engineering practice in Bangalore. You own the architecture of the agents themselves — reasoning, planning, tool-calling and memory — and you own the surfaces people actually use them through: chat UI, IDE extensions, CLI tools and the APIs behind them.

You work closely with the Integration Architect on how agents connect into IDEs and internal systems, and with the MLOps/eval function on the quality bar an agent has to clear before it ships.

This is a hands-on role. You are still writing and reviewing code, still debugging orchestration failures when something breaks in production, and still accountable for what ships — not a role that manages from a distance.


What you will do

Architect and orchestrate agents

  • Design agent architecture: reasoning loops, planning, tool-calling and memory/context management.
  • Build multi-step orchestration: task decomposition, tool selection and error recovery.
  • Partner with the Integration Architect on connecting agents to IDEs and internal systems.

Ship end-to-end agent products

  • Own the build of user-facing surfaces for Copilot-style products: chat UI, IDE extensions and CLI tools.
  • Build the backend APIs that connect those surfaces to agent and LLM services, including streaming responses, session state and context handling.
  • Ship integrations into developer tools (VS Code extension API, LSPs, browser extensions) and own deployment of both the frontend and backend components you build.

Set the bar and take releases live

  • Review code and agent designs from the two Junior AI Engineers, and mentor them toward independent ownership.
  • Define the agent quality bar with the MLOps/eval function before anything ships, and work with that function on the CI/CD, monitoring, versioning/rollback and observability an agent needs once it's live.


Enable the Spokes

  • Own the governance bar for citizen-built agents — what "safe to ship" means for security, data access, cost and quality — in partnership with security/compliance and the Integration Architect.
  • Publish and maintain the standards — prompting, evals, architecture patterns — that spoke teams build against.
  • Own the design of the self-service component catalog spokes build on top of, and the support model — office hours, an embedded rotation, or a ticket queue — for citizen developers using it

What you bring

We have kept this list to what the role truly requires. If this role excites you and you meet most, but not all, of these points, we encourage you to apply.


Core requirements

  • 1-6 years hands-on building LLM or agent systems.
  • Strong Python and/or TypeScript; comfortable owning a service end to end.
  • Hands-on with agent frameworks or SDKs (Claude Agent SDK/MCP, LangGraph, AutoGen) or custom orchestration.
  • Has shipped an agentic system to production, not just a prototype.
  • Solid grasp of traditional machine learning/AI (e.g., classification, regression, clustering, feature engineering) in addition to LLM/agent-based approaches..
  • Comfortable designing REST, GraphQL and streaming/WebSocket APIs, and familiar with LLM streaming APIs (SSE/WebSockets) and token-by-token rendering.
  • Familiarity with enterprise AI/copilot platforms and cloud-native model ecosystems — Microsoft Copilot and Copilot Studio, Azure AI Foundry (model catalog, deployments, and orchestration), and AWS model configuration (Bedrock model access, inference profiles/settings) is a plus.


Valuable extras

  • Strong in React/TypeScript for frontend work, and Node.js or Python for backend work.
  • Experience with CI/CD tooling (GitHub Actions, Jenkins or similar), cloud infrastructure (AWS, Azure or GCP) and containers (Docker, Kubernetes).
  • Observability tooling — Datadog, Prometheus/Grafana, or LLM-specific tools like LangSmith or Arize — and familiarity with LLMOps practices: prompt versioning, eval pipelines, cost tracking.
  • Working knowledge of auth and session management, and awareness of security and compliance considerations for AI systems.
  • Experience in the manufacturing industry, preferably semiconductor, is a plus.
  • Experience or interest in developer enablement or platform engineering — documentation, SDKs, or internal tooling built for non-specialist users, not just for your own team.


Why join us

  • Real ownership: you set the architecture and the quality bar for agents that ship to real users, not just a reference design others build from.
  • A mentoring role with teeth: two Junior AI Engineers are counting on your reviews, and Nexperia measures you on their growth as much as on your own output.
  • You're measured not only on what the Hub ships, but on how many spoke teams successfully ship agents using what you've published.
  • Global exposure from Bangalore: you work with the AI and Data Centers of Enablement, the Integration Architect, platform engineering, security and compliance, with visibility up to the CIO and IT Management Team.
  • A team that values structured thinking, intellectual honesty about trade-offs and good documentation over heroics.





.

Talent acquisition based on Nexperia vacancies is not appreciated. Nexperia job adverts are Nexperia copyright © material and the word Nexperia® is a registered trademark.

D&I Statement

As an equal-opportunity employer, Nexperia values diversity not just because it is the right thing to do but because diverse teams perform better. We are dedicated to being inclusive, and a proof point of this dedication is that we were the main partner of the very first Dutch Paralympic Team NL House during the Paris 2024 Paralympic Games. Our recruitment process is inclusive and accessible to all, and we consider all applicants fairly, as well as providing a safe work environment and reasonable adjustments where requested.

In addition, we offer our colleagues the possibility to join employee resource groups such as the Pride Network Group or global and local Women's groups. Nexperia is committed to increasing women in management positions to 30% by 2030.

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

Bangalore

Working pattern and location restrictions need checking in the full posting.

Work authorization
Enable the Spokes - Own the governance bar for citizen-built agents — what "safe to ship" means for security, data access, cost and quality — in partnership with security/compliance and the Integration Architect. - Publish and maintain the standards — prompting, evals, architecture patterns — that spoke teams build against. - Own the design of the self-service component catalog spokes build on top of, and the support model — office hours, an embedded rotation, or a ticket queue — for citizen developers using it What you bring

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.