Skip to content

Data and integration FDE job description template

A template for an FDE role that builds customer integrations and data systems.

Replace every [EMPLOYER: ...] field with the company’s actual information. This template fits a role that connects a product to customer systems, data, APIs, or workflows. It assumes the engineer owns technical delivery. Adjust the ownership section when a delivery manager, solutions architect, or customer team owns part of the work.

[EMPLOYER: company name] — Forward Deployed Engineer, Data and Integrations

Location: [EMPLOYER: location or approved remote region]

Work arrangement: [EMPLOYER: office, hybrid schedule, or approved remote arrangement]

Travel: [EMPLOYER: expected customer travel]

Employment: [EMPLOYER: status]

Compensation: [EMPLOYER: base range, bonus/equity, and location rules]

Work authorization: [EMPLOYER: policy and sponsorship details]

The role

[EMPLOYER: company name] helps [customer type] use [product] with [systems, data, or workflow]. As a Forward Deployed Engineer, you will take an integration from [source discovery and feasibility] through [production cutover and handoff]. You will work with [customer technical teams] to understand schemas, access methods, constraints, and the result they need.

[EMPLOYER: State the split of responsibility. For example: “The implementation manager owns timeline and stakeholder communication. You own technical design, build, validation, and production readiness.”]

What you will do

  • Inventory and sample [EMPLOYER: source systems] and agree on the data or workflow scope.
  • Design mappings, transformations, validation rules, and failure handling for [EMPLOYER: data types or APIs].
  • Build and maintain [EMPLOYER: services, pipelines, connectors, automations, or migration tools] using [EMPLOYER: languages and platforms].
  • Integrate with REST APIs and other interfaces using [EMPLOYER: authentication methods, webhooks, queues, or file exchange].
  • Test with representative data, run a pilot or dry run, and support production cutover and reconciliation.
  • Debug issues across code, data, permissions, infrastructure, and customer configuration.
  • Write technical documentation, runbooks, and an operational handoff for [EMPLOYER: owning team].
  • Turn recurring integration work into reusable components and clear implementation patterns.
  • Bring verified customer constraints and repeated requests to product and engineering.

What success looks like in the first [EMPLOYER: 90 days / six months]

  • [EMPLOYER: The first integration has an agreed scope, mapping, test plan, and owner for each dependency.]
  • [EMPLOYER: Validation catches named data-quality or access failures before production cutover.]
  • [EMPLOYER: The production handoff includes monitoring, rollback or remediation steps, and documentation.]
  • [EMPLOYER: A reusable connector, test utility, or runbook reduces repeated work on the next integration.]

Required experience

  • Experience owning a production integration, migration, data pipeline, or technical implementation through testing and rollout.
  • Strong experience with [EMPLOYER: Python / SQL / TypeScript / other actual tools].
  • Working knowledge of relational data, schemas, transformations, APIs, authentication, and error handling.
  • Experience diagnosing mismatched data, failed requests, permission problems, or performance issues.
  • Ability to explain technical constraints and trade-offs to customer engineers and non-technical stakeholders.

Useful additional experience

  • [EMPLOYER: cloud platform and data services]
  • [EMPLOYER: healthcare, finance, logistics, or other domain requirements]
  • [EMPLOYER: observability, data-quality checks, or compliance controls]
  • [EMPLOYER: migration, ETL, event-driven systems, or agent workflows]

We consider backgrounds in backend engineering, data engineering, integration engineering, implementation engineering, consulting, or solutions engineering when the work shows the required production ownership.

Scope and working conditions

[EMPLOYER: Explain customer contact, typical project length, number of concurrent implementations, on-call or incident expectations, office schedule, travel, and who approves production changes.]

Benefits and application

[EMPLOYER: benefits, accommodations, interview process, and application instructions]

Apply: [EMPLOYER: application link]

Related reading