Choose between a forward-deployed engineer and a solutions engineer by defining where the person enters the customer journey, what they build, and what they own afterward. The titles are not standardized across companies. A clear responsibility map is more useful than assuming candidates share your definition.
This distinction matters when a founder needs both technical credibility with buyers and delivery work after a deal.
Map the customer journey
Write the work from initial technical discovery through deployment and ongoing support.
| Responsibility | Clarification needed |
|---|---|
| Technical discovery | Is the goal to qualify an opportunity, define implementation requirements, or both? |
| Demonstrations and prototypes | Are these reusable product demonstrations or customer-specific builds? |
| Deployment | Who integrates, tests, and releases the solution? |
| Production issues | Who investigates and maintains what was delivered? |
| Product feedback | How do recurring customer needs reach the core product team? |
Place an owner beside every row. A handoff cannot be “the team” if the new hire will need to negotiate it repeatedly.
Choose the primary mandate
A role centered on helping a buyer evaluate a product should describe pre-sales activities, commercial collaboration, and technical qualification.
A role centered on implementing and adapting software in customer environments should describe engineering depth, deployment constraints, and maintenance expectations.
If one person will do both, explain how priorities change when a live deployment conflicts with a new sales opportunity. Include who resolves the conflict.
Test the relevant work
Illustrative exercise: A fictional customer requests a workflow the standard product does not fully support. Provide a short product description and ask the candidate to prepare a technical discovery plan.
For a pre-sales mandate, explore how they clarify the requirement, identify gaps, and avoid promising unsupported capability.
For a deployment mandate, continue into integration boundaries, testing, failure handling, and a plan to avoid an unmaintainable one-off solution.
Do not use the same exercise result to infer both commercial judgment and production engineering depth without examining each.
Make the working conditions visible
Explain customer meeting frequency, travel expectations, time-zone coverage, access constraints, and support responsibilities. State which are firm requirements and which can be designed with the hire.
Keep candidate introductions consistent. A person attracted by hands-on engineering should not discover late in the process that most of the role is running demonstrations.
Write a title-independent opening sentence
Try: “This person owns customer integrations from technical scoping through a supported production launch.”
Then choose the title that best communicates that mandate to your target candidates. Use the forward-deployed engineer hiring guide to develop the wider search, and the role overlap worksheet if the responsibilities remain too broad.
If the offer includes variable pay connected to customer work, use the technical-hire incentive worksheet to clarify contribution, credit, quality, and timing.