What is Forward Deployed Architecture?

The discipline

The architecture underneath is the standard one

The discipline being carried into the field is the settled one. AWS's Well-Architected Framework, the most widely used formal statement of what architecture weighs, organizes design around six pillars: operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability.

The forward deployed listings ask for the same trade-off set without citing any framework. Climb, a data and AI consultancy, lists scalability, security, maintainability, performance, cost, and delivery speed as the balance its architect holds. Adobe's posting reaches for observability, reliability, high availability, and enterprise security standards. Sustainability appears in none of the tracked listings, and no listing treats the quality bar itself as new; the postings reserve their novelty claims for the position.

Across listings

Every listing keeps the architect at the keyboard

One person accountable for the whole design is the first constant. Atlassian calls it owning the target-state architecture. Adobe calls it the end-to-end technical vision of an implementation. Climb calls it the technical architecture of a client engagement, held by a design authority who makes the platform, integration, security, and cost decisions and stands behind them.

The second constant is a hiring bar against purely advisory work. Adobe requires the architect to build proofs of concept personally. Climb requires code on the critical path. DevRev budgets thirty to fifty percent of the role's time for hands-on implementation. Google Cloud describes its generative AI architect team as one that codes, debugs, and deploys inside customer environments. Gallagher, hiring the title for its own IT organization, asks for production-quality code under ambiguity. Several postings write the requirement as a denial: Atlassian's states the role is neither a traditional solutions engineer job nor a hands-on-keyboard engineering job, and Gallagher's opens by saying it is not a traditional architecture role. The consistent target of the denials is the advisory stereotype the word architect carries.

The third constant is output that outlives the engagement. Every tracked company asks the architect to codify field patterns: reference architectures at Adobe, NVIDIA, Anthropic, and Climb; architecture decision records, prototypes, and infrastructure modules at Atlassian; reusable blueprints and enablement assets at Anthropic; accelerators contributed back to the practice at Climb. On the productization loop the whole role family shares, the architect's unit of reuse is the reference architecture: the document and pattern set a future engagement starts from instead of starting from the customer's whiteboard.

Across the AI-centered listings a fourth deliverable class recurs: evaluation frameworks at Anthropic and DevRev, AI governance and human-in-the-loop patterns at Atlassian, architecture governance review at Gallagher, prototype standards on Google Cloud's team. In enterprise AI engagements the architect seat owns the structure that makes a system's output verifiable, which is the part of a deployment a customer cannot adopt without.

Placement

The pre-sale line blurs at the architect tier

The engineer's side of the family draws a clean boundary: sales engineering before the contract, forward deployed engineering after it. The architect listings do not honor that line. Anthropic's architect tier is written as a pre-sales position in its own postings and compensated on target earnings. DevRev's architect scopes engagements with pre-sales teams and then owns the delivery once the deal closes. Atlassian embeds its principal architects in one to three accounts at a time for three to nine months, inside a sales organization. Climb's architect owns delivery on consultancy engagements. Catio's founding architect spans product-led entry through production outcomes. The seat attaches wherever design authority is needed, and companies place it before the contract, after it, or across it.

For a reader of postings, the department tells more than the title. NVIDIA and Atlassian post the role under sales. NVIDIA's closest non forward deployed architect listing, in Japan, posts under professional services and reads as operations work. Gallagher posts the title under information technology, and its version is internal: an insurance claims organization embedding an architect with its own business stakeholders, no vendor platform in the arrangement. One listing is a data point and not a pattern, but it is the first tracked use of the title employer-side.

The title also has no enforced floor yet. HighRadius posts a Forward Deployed Architect asking two to five years of experience for work weighted toward adoption playbooks, steering committees, and change management, a profile closer to engagement management than to the design seat every other tracked listing describes. Reading the responsibilities, here as everywhere in the family, settles what the title does not.

Team structure

How companies staff the practice

Current listings show the practice in three shapes. The embedded model assigns one architect deep into a small number of accounts: Atlassian's one to three accounts for months at a time, DevRev's architect as the technical owner of the customer relationship, Climb's architect owning one engagement's system end to end. The portfolio model runs one architect across many: NVIDIA's seat provides architectural direction across strategic engagements simultaneously, is invoked where standard product capability runs out, and owns cross-customer programs such as benchmarking. The organizational model builds architecture into a managed structure: Google Cloud runs a regional generative AI architect team under a manager who owns prototype standards and deploys specialists in MLOps, generative media, and agentic systems into accounts.

Anthropic's is the most built-out architecture organization in the tracked set, under its own name: Applied AI Architecture. Individual architect seats cover commercial, enterprise tech, industries, and government technology. Managers run segments for partnerships, startups, and cybersecurity. A security architect seat serves regulated European enterprises, and a head-level seat runs architecture for nonprofit and mission-driven deployments. The segmentation is by market rather than by technology, the same verticalization pattern the engineering practice shows, one tier up.

The builder and coordinator pairing that defines forward deployed engineering as a practice recurs at the architect level. Climb pairs its architect with a forward deployed AI lead who owns the overall engagement and the client relationship while the architect owns the system itself. Adobe seats its architect inside a forward deployment engineering team as the senior design authority and mentor for the engineers around it. And Catio shows the practice at its entry state: a founding architect, hired singular, to create the technical backbone of the company's commercial motion before any team exists.

Naming

One seat, several spellings

Adobe's posting is headlined Forward Deployed Architect. The body of the same posting writes Forward Deployment Architect and places the role inside a Forward Deployment Engineering team. Both forms, one document. What the variation signals is not stated in the posting, and this reference reads it as exactly that: two live spellings of one title at one company.

Anthropic titles its engineers with the full forward deployed phrase, without exception, and titles its customer-facing architect tier Applied AI Architect, with the practice form Applied AI Architecture in its manager and head titles. Its architect postings name forward deployed engineering as a fit background, and the seats are pre-sales, which places the two title families on different sides of an engagement at that company. The functions sit adjacent without being the same seat, and this reference records them separately.

The remaining variants are function and stage markers. Amazon posts a Senior Forward Deployed Deep Learning Architect inside its Generative AI Innovation Center, the function written into the middle of the title. Atlassian levels the title with Principal. Catio stages it with Founding FDA. Google Cloud's posting also writes field deployed architect, lowercase, in its own responsibilities text, alongside the forward deployed form. Forward deployed technical architect circulates as a phrasing for the seat as well; no tracked listing posts it as an exact title.

The background nouns the listings draw on stay consistent: solutions architecture first, as the stated prior role in nearly every posting, then systems, enterprise, platform, and security architecture. Forward Deployed Solutions Architect, the highest-volume variant on the role side, is covered on the forward deployed architect reference.

The prefix

What forward deployed adds to architect

The comparison that isolates the prefix is the same company posting both forms. NVIDIA's non forward deployed senior solutions architect deploys, validates, and hands over specific AI compute systems, and its posting describes that work, in NVIDIA's own words, as embodying the forward deployed engineer approach. NVIDIA's Forward Deployed Architect, posted separately, directs architecture across a portfolio of strategic engagements, owns benchmarking programs, and feeds patterns to the product roadmap. At the one seniority level the two ladders share, NVIDIA publishes the same base band for both titles, and the forward deployed ladder extends one level higher. The title marks scope and accountability. It carries no pay premium at equal level, and the embedded work mode exists at NVIDIA without the title.

Atlassian shows the word architect traveling without the prefix into pure strategy work: a director-level workforce intelligence architect in its people organization designs models, scenarios, and planning frameworks, with no customer and no shipped system. The forward deployed architect at the same company is defined by customer embedding and durable shipped artifacts. Where Atlassian attaches the prefix, it binds architect back to systems delivered inside an account.

Read across every pair, the prefix consistently marks position: embedded with a customer, accountable for an engagement's design, feeding patterns back to the platform. It does not consistently mark seniority, a pay band, or a distinct technical skill set. Forward deployed architecture is an operating model applied to a standing discipline, and the listings, including the ones that use the phrase without the title, treat it exactly that way.

What does "forward deployed" mean, across every role →

The same team-function lens on the creative branch: a team of forward deployed creatives →

Methodology and sources

How this reference is compiled

This page covers the operating model and team context behind the forward deployed architect role, which has its own reference. The account is synthesized from public architect listings at the companies named, read as one set and checked against non forward deployed architect listings at the same companies to isolate what the prefix contributes. Discipline grounding draws on AWS's published Well-Architected Framework. Claims about any single company describe its own public postings; patterns are stated only where they recur across companies, and single-listing observations are marked as such.