Skip to content

Handbook: add Forward Deployed Engineer job description #5966

Closed as not planned

Description

@MichaelBDavis

Overview

Add a Forward Deployed Engineer page to the FlowFuse handbook under People Ops → Job Descriptions, using the supplied Google Doc as the source of truth. This is a new handbook role page.

Content

Use the current Job Descriptions conventions: a Markdown page with title front matter, one H1 role title, and H2 sections for Job Description, Skills, 90 Day Plan, and Hiring Plan. Use ordinary paragraphs and Markdown lists, with H3/H4 subsections where helpful. Preserve the supplied role scope and qualifications.

The repository now stores handbook content under nuxt/content/handbook/. Follow the existing handbook layout and sidebar behavior; do not add a new page design or a global website navigation item.

Content mapping and editorial notes

  • Map “Role Overview” and all four responsibility groups to Job Description: Pre-Sales Support, Forward Deployed Customer Delivery, Customer Success and Expansion, and Partnership with Product and Engineering.
  • Map “What We’re Looking For” and “Nice to Have” to Skills, keeping required and preferred experience distinct.
  • Correct the duplicated “forward deployed engineering” in the first experience requirement. Retain the five-year experience requirement and the other listed disciplines.
  • Preserve the role's GTM placement, hands-on delivery and customer ownership/handover responsibilities. Retain Product ownership of roadmap priorities and Engineering guidance on technical standards. Do not invent a reporting line.
  • Put all six screening questions and their goals under Hiring Plan → Screening Questions, followed by Evaluation Criteria, matching the existing Solutions Engineer page.
  • Remove the screening appendix's emoji and visual separators, repair the Go Forward/No-Go list nesting, and change the stale “hybrid SE role” reference to “forward deployed engineer role”. No evaluation criteria are otherwise changed.
  • The source contains screening material but no full hiring process or 90-day plan. Complete these with the hiring owner; the Solutions Engineer page is a formatting reference, not authority to copy its interviewers or onboarding commitments.
  • “Why Join FlowFuse?” is job-posting material. Keep it in the recruiting source rather than adding compensation/equity or recruiting boilerplate to this role page, consistent with the handbook's optional About FlowFuse section.
  • Add a new Forward Deployed Engineer page. Leave the existing Solutions Engineer page and URL in place; renaming or replacing that role is outside this request.

Handbook content draft

The draft below preserves the supplied role content while applying the handbook structure. HTML comments identify missing content to resolve during implementation. Do not publish those comments, empty sections, or invented hiring commitments.

Expand the Markdown page draft
---
title: "Forward Deployed Engineer"
---

# Forward Deployed Engineer

## Job Description

We’re hiring an experienced forward deployed engineer to work across the full customer lifecycle, from pre-sales discovery and demos to hands-on customer delivery and long-term solution expansion. This is a senior, customer-facing role within our go-to-market organization, requiring strong domain expertise in industrial automation and the ability to build and deploy working solutions for enterprise customers.

You’ll work directly with customer teams in a forward deployed capacity, turning operational needs into solutions that deliver measurable value. You’ll also identify opportunities to expand across use cases and sites, and bring practical insights from customer deployments back to Product and Engineering.

You’ll be a key technical advisor, hands-on delivery partner, and trusted collaborator to both prospective and existing customers.


### Pre-Sales Support

* Partner with Account Executives during discovery to understand customer goals and technical environments
* Deliver tailored demos, solution architecture walkthroughs, and lead technical proof-of-concepts (PoCs)
* Help prospects align FlowFuse to their broader industrial and digital transformation goals
* Collaborate on pricing proposals and technical responses to RFPs and security reviews

### Forward Deployed Customer Delivery

* Work alongside customer operations, IT, and OT teams to define a focused use case, delivery scope, milestones, and measurable success criteria
* Build and deploy solutions using FlowFuse and Node-RED, connecting industrial data and enterprise systems and developing workflows, integrations, and custom logic where needed
* Carry successful demos and proofs of concept into production use, working with customers to test functionality, validate operational results, and meet security and reliability requirements
* Take ownership of technical delivery within the agreed scope, communicate progress and blockers, and align changes with the customer and Account Executive
* Document solution design, configuration, and custom development; provide training and agree ongoing ownership and support responsibilities with customer teams

### Customer Success and Expansion

* Guide technical onboarding and help customer teams adopt and extend the solutions delivered
* Partner with customers to assess results, resolve blockers, and optimize solution design
* Actively explore and surface additional use cases within the customer organization
* Facilitate roadmap alignment and strategic planning discussions with technical champions
* Deliver ongoing best practices, architecture reviews, and training to ensure long-term success

### Partnership with Product and Engineering

* Work closely with Product and Engineering to share recurring customer needs, deployment lessons, and reusable components developed in the field
* Help evaluate what should become a supported product capability, a repeatable solution, or customer-specific development, with Product owning roadmap priorities and Engineering guiding technical standards

## Skills

### What We’re Looking For

* 5+ years in forward deployed engineering, sales engineering, solution engineering, or industrial systems integration
* Deep industry expertise in MES, industrial automation, IIoT, smart manufacturing, or related fields
* Track record of identifying additional solution opportunities within enterprise accounts
* Hands-on experience building and deploying working solutions in customer environments, including integrations, workflow logic, testing, and troubleshooting
* Ability to translate an operational problem into a scoped delivery plan and work with customer teams through deployment, validation, and handover
* Experience with technologies such as Node-RED, MQTT, OPC-UA, SCADA systems, PLCs, or edge computing
* Strong communication skills - comfortable engaging engineers, architects, and executive stakeholders
* High degree of initiative and ability to manage customer relationships across the lifecycle
* Willingness to travel occasionally for key customer engagements

### Nice to Haves

* Hands-on experience deploying Node-RED at scale
* Familiarity with Unified Namespace or other modern industrial data architectures
* Experience with containerization, cloud (AWS/Azure), or Linux-based edge devices
* Multilingual skills (e.g., German, French, Spanish)

## 90 Day Plan

<!-- Complete with the hiring owner before publication. This plan is not supplied in the source. -->

## Hiring Plan

<!-- Confirm the interview stages, interviewers and assessment format with the hiring owner before publication. The supplied screening questions are retained below. -->

### Screening Questions

1. Can you briefly walk me through your recent experience in a customer-facing engineering or solutions role?
   * Goal: Confirm they have relevant experience in pre-sales or post-sales technical roles (e.g., forward deployed engineer, Sales Engineer, Customer Success Engineer).
1. Have you worked with industrial technologies like SCADA, PLCs, MQTT, or Node-RED?
   * Goal: Confirm basic exposure to the industrial automation ecosystem. If not Node-RED specifically, check for adjacent tech like OPC-UA or IIoT platforms.
1. Can you share an example of a time when you helped a customer expand or deepen their use of a solution over time?
   * Goal: Gauge if they’ve played a role in post-sale expansion, solution discovery, or upsell enablement, key traits for this forward deployed engineer role.
1. How comfortable are you leading technical conversations with both engineers and business stakeholders?
   * Goal: Evaluate communication range and confidence in dealing with mixed audiences, an essential skill for FlowFuse’s customer base.
1. Have you ever delivered a proof of concept (PoC) or demo as part of a sales process?
   * Goal: Validate they’ve led or contributed to technical pre-sales motions.
1. Do you have experience working remotely and managing your own schedule across multiple customers?
   * Goal: Confirm self-management and comfort with autonomy in a remote startup environment.

#### Evaluation Criteria

* Go Forward if they:
  * Have customer-facing technical experience (especially in IIoT or automation).
  * Can communicate clearly across technical and business audiences.
  * Show signs of proactivity and comfort with ambiguity.
* No-Go if they:
  * Lack relevant experience (pure dev, sysadmin, etc.).
  * Struggle to articulate impact in customer engagements.
  * Are uncomfortable with remote work or startup dynamics.

Visuals

Use the existing handbook page template. No new illustrations, screenshots, buttons, or custom layout are required.

Proposed URL slug

/handbook/peopleops/job-descriptions/forward-deployed-engineer/

Include in main navigation?

No.

Navigation section

Handbook → People Ops → Job Descriptions. Ensure the new page appears in the existing handbook sidebar, using the current navigation mechanism.

Notes

Acceptance criteria

  • Add the new Markdown page at the target path with the correct front matter and role title.
  • Preserve the supplied responsibilities, requirements and role boundaries, allowing the documented formatting and copy corrections.
  • Complete the role-specific 90-day plan and any missing hiring-plan details with the hiring owner before publication. Do not infer these from another role or treat first-year outcomes as a 90-day plan.
  • Match the existing handbook hierarchy, typography, lists, breadcrumbs, table of contents and sidebar navigation.
  • Preserve all six screening questions and the Go Forward/No-Go evaluation criteria with readable list nesting.
  • Keep the existing Solutions Engineer page and URL unchanged.
  • Verify the page and navigation links in the site preview and run the repository's applicable content/build checks.
  • Remove implementation-only comments and ensure no empty sections or unresolved placeholders are published.

Activity

  1. added
    taskA piece of work that isn't necessarily tied to a specific Epic or Story.
    area:docsImprovements or additions to documentation
    on Oct 20, 2026
  2. MichaelBDavis commented on Oct 20, 2026

    @MichaelBDavis
    ContributorAuthor

    Superseded by draft PR #5968. The handbook page, remaining 90-day and hiring-plan details, and review are now tracked in that PR. Closing this separate tracking issue as requested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:docsImprovements or additions to documentationtaskA piece of work that isn't necessarily tied to a specific Epic or Story.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions