Forward Deployed Engineer at Code and Theory

About Forward Deployed Engineering at Code and Theory

The Machine is the agentic operating system for marketing, built by Code and Theory. It plugs into the tools marketing teams use and turns disconnected workflows into a single intelligent system, connecting brand strategy, creative production, and media performance. The Machine helps power agencies across Stagwell's network and world\-leading brands. Born in 2001, Code and Theory is a digital\-first creative agency that sits at the center of creativity and technology. We pride ourselves on not only solving consumer and business problems, but also helping to establish new capabilities for our clients. With a global client roster of Fortune 100s and start\-ups alike, we crave the hardest problems to solve. We have teams distributed across North America, South America, Europe, and Asia. The Code and Theory global network of agencies is growing and includes Kettle, Instrument, Left Field Labs, Create Group, Current, and TrueLogic.

Companies like Code and Theory typically structure FDE teams around a build-team model, where engineers join an existing customer engineering function and deploy the product across a portfolio of accounts. Based on FDE Pulse data across 1183 active postings, 1% of FDE roles are build-team positions and 0% are "first hire" situations where the engineer defines the function. Code and Theory's 2 active postings fall into the first hire category based on role count.

FDE roles across the market are 1% North America-focused based on 1183 active postings. 0% of FDE roles are classified as growth hires, meaning the company is expanding its customer base rather than backfilling an existing position. This context matters for FDE candidates evaluating Code and Theory: growth hire roles often come with more pressure to ramp quickly but also clearer performance metrics tied to customer success.

What FDEs Do at Code and Theory

Forward Deployed Engineers at Code and Theory own the technical success of customer deployments. This means designing integration architectures specific to each customer's infrastructure, writing and maintaining production code that runs in customer environments, and serving as the primary technical point of contact for enterprise accounts. The role sits at the intersection of product engineering and customer success without being either.

Day-to-day work for an FDE at Code and Theory varies by customer complexity and deployment stage. In the early phases of a new customer engagement, FDEs focus on environment setup, data mapping, and building the first integrations. As deployments mature, the work shifts toward performance tuning, expanding use cases, and training customer teams on new capabilities. Some FDE roles also feed product insights back to internal engineering, effectively acting as a bridge between customer needs and the roadmap.

Career Path for FDEs at Code and Theory

FDE careers typically progress along one of three paths: deepening technical specialization within the FDE function (moving from mid-level to senior to staff FDE), transitioning into engineering management (leading FDE teams or broader customer engineering organizations), or lateral moves into product management (where customer-facing FDE experience is highly valued). All three paths are available at companies with established FDE programs.

The FDE market median of $180,000 base salary across 134 active postings reflects a market that prices the role at a premium over equivalent-seniority software engineers at the same companies. Total compensation including equity, particularly at venture-backed companies, can be 20 to 50 percent higher than base salary. FDEs considering opportunities at Code and Theory should evaluate total compensation, rather than only base salary, when comparing offers.

Interview processes for FDE roles at most companies include a technical coding round, a system design round specific to customer deployment scenarios, and a customer scenario exercise where candidates are asked to scope a deployment, communicate trade-offs, and handle technical objections. Strong candidates combine engineering depth with the ability to explain complex systems to non-technical stakeholders clearly and without jargon.

Frequently Asked Questions