Back to jobs

Forward Deployed AI Architect

Pay
Pay not listed
Work setting
Remote — work setting source
Work setup in the employer’s posting: TELECOMMUTE
From the employer’s posting
Employment
Not stated
Check the employer’s page ↗

Posting record

Report an error
Status in our records
Live
First seen by us
Nov 1, 202620 days ago
Recorded sightings
20
Last seen by us
Nov 21, 2026
Employer says posted
Sep 29, 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 20

Similar jobs usually come down between day 3 and day 42.

From 633 similar postings that came down. Coming down is not always a hire.

EPAM Systems is hiring

892 open jobs

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

Hiring record

Your next step

Check the employer’s posting for the current role and application details.

Already applied? Track this application

Job description

View original posting ↗

Most enterprise AI initiatives stall between pilot and production. The demo works; the path to a system that runs a real business process, under real controls, with a real owner, is where they get stuck. The Forward Deployed AI Architect is the person we place inside the client to get them unstuck. You will be embedded with client business owners and engineering leaders, designing AI-native, Enterprise AI and Applied AI solutions — assistants, RAG systems, agents, agentic workflows, autonomous components — and taking them from pilot to production. You will carry the architect's responsibilities (framing the problem, fitting the business scope exactly, making trade-offs explicit, deciding what the system must not do) while sitting at the client's table, in their vocabulary, on their timeline. The role is modeled on the forward-deployed engineering pattern but operates at the architecture level. It rewards people who like ownership, who can work with ambiguity without a home team beside them, and who measure themselves by what reached production at the client, not by what was presented. Req# 1090267686 Responsibilities Embed with a client account, working directly with business owners, product leaders, engineering teams, security, risk, and operations to take AI solutions from pilot to production Design end-to-end AI-native architectures: orchestration, retrieval, integration with systems of record, agent autonomy and guardrails, identity and authorization, evaluation, observability, and cost model Own three artifacts that make your impact measurable: a capability economics model — what each AI capability costs and what it earns, so investment decisions are made on evidence; trust-rung evidence for every agent — the documented proof of how much autonomy each agent has earned and under what controls; a knowledge-graph slice of the client domain — the entities, relationships, and constraints the solution depends on, captured so the architecture and the business share one model Turn contradictory or incomplete requirements into explicit business decisions with named owners Decide, per component and per risk, how much can be delegated to AI — including AI coding agents in the delivery process — and where a human must stay in the loop Define how each system is evaluated: how the client will know an assistant or agent fits the business scope, not just that it produces fluent output Build proofs of concept and reference implementations when a decision needs evidence or a team needs an example of "good" Feed what you learn at the client back into EPAM's AI architecture practice: patterns, reference architectures, and what generation gets wrong Requirements You have taken AI-native systems to production at a client or customer — RAG, assistants, agents or agentic workflows with real users and real business processes behind them — in a solutions architecture, customer engineering, forward-deployed, or consulting role, with architect-level responsibility for the system around the model You are a proven solution architect from a consulting or client-facing background who has started building with AI on your own initiative in the last year or so, and wants to make AI-native design at the client's side the center of your work A track record of client- or customer-facing architecture: you have framed problems for people who are not technologists, presented options with costs and risks, and got decisions made Solid solution or software architecture experience with delivery accountability — systems you designed that shipped and ran Depth in integration, distributed systems, cloud, and data-flow architecture at enterprise scale Comfort operating with ambiguity, conflicting stakeholders, and shifting requirements, without waiting for clarity before starting A habit of writing things down so decisions survive you: ADRs, design documents, evidence for autonomy and risk decisions Recent hands-on coding ability, enough to prototype and keep your constraints honest Willingness to be on-site with clients and to travel as the engagement requires Nice to have Regulated-industry experience — financial services, healthcare and life sciences, insurance — including working with security, risk, and compliance functions Agent frameworks, tool and function calling, MCP, orchestration patterns, LLM observability Identity and authorization for agentic systems (OAuth 2.1, SPIFFE, AuthZEN, DPoP) Experience with cost and token economics, or with building business cases for AI capabilities Presales, proposal, or account-shaping experience Forward-deployed or field engineering background at an AI or data platform vendor

About EPAM Systems

People
About 3,012 in 2024.Benefit plan filings (Form 5500)
Company
Listed as EPAM.
H-1B visas
21 approved for new hires in fiscal 2025.US Citizenship and Immigration Services

Demand for Forward Deployed Engineer roles

New Forward Deployed Engineer postings at the employers we follow are up 225% over the last 6 weeks compared with the 6 before.

Weekly new Forward Deployed Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 51, the most 267, and the latest week had 217.
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 Forward Deployed Engineer, by the work the posting describes.

Forward deployed engineers are placed with their employer's customers: they learn a customer's problem and write the code that makes the employer's product solve it inside the customer's own systems.

Postings ask for strong software engineering, most often in Python, ease with customers and their executives, often travel, and in about three of four cases work with large language models or AI agents.

An AI engineer or data engineer builds for their own employer's product team; a forward deployed engineer does similar work inside a customer. We give this role to every posting whose title says forward deployed.

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.

AI answers unavailable

We couldn’t identify enough role detail in this saved description to support an AI answer. Read the full posting