A demo can work, yet the handoff to the team that must operate it can still fail. The integration may be unclear, nobody may own the fallback, or the team may not know what "ready for production" means.
In brief: a solutions engineer typically helps a customer evaluate technical fit; a consultant provides advisory or implementation capacity under a defined engagement; and a forward deployed engineer, or FDE, works alongside the customer to build, deploy, and hand over a production workflow.
These labels are not standardized, and they are not mutually exclusive. A consultant can work in a forward-deployed way, and some solutions engineers remain involved through launch. The useful comparison is lifecycle stage, code ownership, and accountability, not the title alone.
This guide is written for product and engineering leaders choosing help for an AI deployment, although the role distinctions apply more broadly.
Quick comparison
This Lucent Lab heuristic compares common patterns; titles are not standardized. The same person may cover more than one row on a small team.
| Role | Typical lifecycle coverage | Primary accountability | Code ownership | Best fit |
|---|---|---|---|---|
| Forward deployed engineer | Discovery through rollout and handoff | A working deployment, adoption, readiness, and a clear operational handoff | Usually substantial production code | Requirements are ambiguous and the blockage crosses product, integration, and operations |
| Solutions engineer | Evaluation and solution design; sometimes through launch | Technical fit, architecture, validation, and customer confidence | Varies: demos, prototypes, integration guidance, sometimes production work | A customer needs to evaluate or adopt an existing product |
| Advisory consultant | Problem framing and decision-making | Diagnosis, recommendation, roadmap, and stakeholder alignment | Usually limited | The decision, strategy, or operating model is unclear |
| Technical or implementation consultant | After a platform or direction has been selected | Delivery of a defined integration, configuration, or project | Often, depending on the engagement | The broad direction is known and a defined implementation needs to be delivered |
- Evaluation
- Solution design
- Implementation
- Production
- Adoption
- Solutions engineer: evaluation through solution design, sometimes launch
- Consultant: varies by advisory or implementation engagement
- FDE: discovery through production and operational handoff
These labels overlap: compare the operating model
The titles describe different things. "Forward deployed" usually signals close customer involvement and end-to-end delivery responsibility. "Solutions engineer" commonly describes a customer-facing technical role at a product company. "Consultant" is a much broader category spanning advice and implementation.
In Lucent Lab's usage, forward deployed engineering describes the delivery model rather than the employment relationship. An independent FDE is still a consultant commercially, but the engagement centers on production code, rollout, readiness, and handoff rather than advice alone.
Solutions engineering varies too. OpenAI's pre-sales role focuses on discovery, demos, architecture, evaluation, and purchasing decisions, while Stripe describes solutions engineering as owning the technical customer journey from evaluation through launch and beyond. Read OpenAI's pre-sales role description and Stripe's broader model.
What a forward deployed engineer owns
The work starts before code. Someone has to name the user, the decision the workflow supports, and the evidence that would make the result useful.
- Discover the real workflow. Trace what the user does now, where data enters, who approves an action, and what happens when the system is wrong.
- Make the scope testable. Write a small outcome, acceptance criteria, constraints, and a list of unknowns. For example, test whether a reviewer can approve a draft within the agreed workflow.
- Build the path that matters. Connect the product to the customer's systems, add the model or automation step, and make failures observable and recoverable.
- Run it with the people who own it. A rollout includes permissions, monitoring, a fallback, documentation, and a handoff. It is not finished when a local demo works.
- Return the lesson to the product. A repeated integration or failure pattern may belong in a product capability instead of another one-off adapter.
Example: taking an AI support assistant from demo to production
Imagine a company that wants to generate draft replies from incoming support tickets.
Solutions engineer: demonstrates the product using representative tickets, validates integrations and security constraints, and proposes an architecture.
Advisory consultant: maps the support process, estimates the expected benefit, identifies governance risks, and recommends whether to proceed.
Forward deployed engineer: connects the ticketing and knowledge systems, builds an evaluation set, implements access controls and fallback behavior, adds monitoring, runs the initial rollout, and hands the workflow to its operational owner.
Technical consultant: implements a known ticketing integration after the product, architecture, and broad requirements have been selected.
For a deeper treatment of evaluation, failure handling, ownership, and rollout, see AI Demo to Production: Readiness Checklist.
When to choose each role
As a practical hiring heuristic:
- Choose a solutions engineer when the main question is whether an existing product fits and how to adopt it.
- Choose an advisory consultant when the decision, strategy, or operating model needs diagnosis and alignment.
- Choose a technical consultant when the direction is known and you need a defined integration or implementation delivered.
- Choose a forward deployed engineer when the blockage crosses product, integration, evaluation, rollout, and operational ownership.
Customer proximity need not mean being physically on-site. Some employers expect on-site work or travel, while the model can also operate remotely. Lucent Lab works remotely by default, with on-site work by agreement; the important part is access to the people, systems, and decisions that shape the workflow.
If the workflow still needs its original author to explain what happened, it is not ready to hand off.
Questions to ask before hiring
- Who can describe the user's current workflow and the desired change?
- Who can grant the minimum access required to the systems involved?
- Who will decide whether the result is good enough to release?
- Who will operate the workflow after the engagement ends?
- Which part needs implementation, and which part only needs a decision?
If those answers are missing, changing the job title will not remove the blockage. The first useful step is usually to make the workflow and its boundaries explicit.
Frequently asked questions
Is a forward deployed engineer a consultant?
Often commercially, yes. "Forward deployed" describes how the work is delivered; "consultant" describes the external engagement or a broad category of work. The useful distinction is whether the engagement owns production delivery and handoff.
Does a solutions engineer write production code?
Sometimes. The role may focus on demos, prototypes, architecture, and integration guidance, or it may continue through launch. Ask which code, environments, and operational outcomes the role owns.
Does "forward deployed" mean working on-site?
Not necessarily. "Forward deployed" describes close involvement with the customer's workflow, systems, and decisions. Some employers expect on-site work or travel, but the delivery model can also operate remotely.
When should a product team hire an FDE instead of another product engineer?
When the blockage is customer-specific and crosses integration, evaluation, rollout, and operational ownership. Hire a product engineer when the main need is a reusable product capability with a clear internal owner.
Sources and further reading
- OpenAI's Forward Deployed Engineer role description, an example of one employer's scope.
- OpenAI's Solutions Engineer role description, a pre-sales model.
- Stripe's Solutions Engineer role description, a broader evaluation-through-launch model.
- Accenture's technical consultant role description, an implementation-oriented example.
- Palantir's account of a forward deployed software engineer, another company-specific example.