Two tracks, one pod

The people who embed AI in how a company actually works

Models are the easy part. The hard part is the customer harness: the company's logic, processes and data mapped and built around the AI so it does the job correctly. Alteus Connect staffs that work as pods of Forward Deployed Consultants and Forward Deployed Engineers.

Join as an FDC Join as an FDE

FDC

Forward Deployed Consultant

Business and technology people who understand a workflow, a process and the logic behind it: business analysts, process and operations consultants, functional consultants, product owners and industry specialists.

In a pod they

·Runs discovery with the client's operators and maps how the work really happens, exceptions included
·Writes the business rules and decision logic the harness must follow
·Maps the client's data: sources, fields, matching rules and the cases that need a person
·Defines 'correct' as acceptance tests and evaluation sets, and signs off with the client

How you prove it: Map a claims-intake workflow, reconcile a CRM and an ERP, or turn a refund policy into rules and test cases.

Join as an FDC

FDE

Forward Deployed Engineer

Engineers who are comfortable inside someone else's stack: full-stack, data, ML and platform engineers who ship working systems with the client in the room.

In a pod they

·Builds the customer harness: integrations, agents, retrieval and data pipelines
·Implements the FDC's rules and mappings in the client's systems
·Makes the acceptance tests pass, then adds monitoring and evaluations for production
·Hands over a runbook the client's team can operate

How you prove it: Build a RAG evaluation harness, ship a forecasting endpoint, or fix a flaky end-to-end suite.

Join as an FDE

How a pod works

One outcome, two kinds of expertise

The Alteus team assembles each pod from verified members, opens a private pod room on Alteus Connect, and stays accountable to the client for delivery.

Stage	FDC	FDE
Discover	Interviews operators, collects SOPs, samples and edge cases	Reviews systems, access, data sources and constraints
Map	Process map, business rules, data mapping	Harness design against the map; flags what can't be automated
Build	Writes acceptance tests and eval sets; answers logic questions	Builds integrations, agents and pipelines to pass the tests
Accept	Runs acceptance with the client; signs off the logic	Fixes, hardens, adds monitoring
Run	Updates rules as the business changes	Operates and improves the harness; hands over the runbook

Can you do both?

Choose "Both" on your profile. You will see challenges for each track and can be placed in either role.

How we vet Open roles