Skip to content

FDE Job Description Template

Purpose

Create role-specific job descriptions for FDE positions at different levels. These templates ensure consistent expectations and help attract candidates who understand what FDE work involves.

When to Use

  • When opening FDE positions
  • When defining role expectations for internal communication
  • When explaining FDE career progression
  • When converting existing roles to FDE model

How to Use This Template

  1. Choose the appropriate level based on your needs (see level guidance below)
  2. Fill in all [COMPANY] and [PRODUCT] placeholders with your specifics
  3. Customize the archetype section - which do you need more? (business-facing or product-facing)
  4. Adjust compensation ranges based on your market and budget
  5. Add company-specific benefits in the "What We Offer" section
  6. Keep "The Challenge" section intact - it sets realistic expectations
  7. Review with current FDEs if you have them - does this match reality?

Level Guidance: - Associate FDE: Fresh graduates or engineers with 0-2 years experience - FDE: Engineers with 2-5 years experience, some client-facing work - Senior FDE: Engineers with 5+ years, proven client success, can work independently - Staff/Principal FDE: 8+ years, can lead complex engagements, mentor FDEs


Template: Associate FDE

[COMPANY] - Associate Forward Deployed Engineer

Location: [LOCATION / REMOTE] Type: Full-time


About [COMPANY]

[2-3 sentences about your company, product, and mission. Focus on what makes your product interesting to build on and deploy.]

Example:

"[COMPANY] builds [PRODUCT], a [category] platform that [value proposition]. We work with [target customers] to deploy AI/data/SaaS solutions that [outcome]. Our clients include [notable customers if any]."


The Challenge

You'll be working at the intersection of engineering and client success. Unlike traditional engineering roles, you won't just build features—you'll own whether clients succeed with our product.

This means:

  • Working directly with clients to understand their problems
  • Building on and extending our platform for specific client needs
  • Deploying solutions in client environments (which are often messy)
  • Navigating ambiguity, missing documentation, and unclear requirements
  • Owning outcomes, not just tasks

This role is hard. It requires technical skill, client communication, and high pain tolerance. If you want well-defined tasks and stable environments, this isn't the right fit.


What You'll Do

Weeks 1-4: Learn & Shadow

  • Pair with senior FDEs on active client engagements
  • Set up development environment and learn [PRODUCT] architecture
  • Attend client calls and observe how FDEs work

Months 2-3: Supported Deployment

  • Own specific workstreams on a client engagement (with senior FDE support)
  • Build client-specific customizations and integrations
  • Participate in client meetings and explain your technical work

Months 4+: Independent Work

  • Lead technical work for pilot or production deployments
  • Build demos for prospective clients
  • Contribute to [PRODUCT] codebase based on field learnings
  • Document what you learn to help the next FDE

What We're Looking For

Must-Have:

  • Technical competence - You can write working code. We don't care which languages you know (you'll learn ours), but you should be comfortable programming.
  • Learning velocity - You pick up new technologies and domains in days, not weeks. Self-taught projects are a good signal.
  • Communication clarity - You can explain technical concepts to non-technical people without jargon.
  • Problem-solving grit - When things break (they will), you figure it out instead of waiting for help.
  • Ownership mindset - "I'll figure it out" instead of "That's not my job."

Nice-to-Have:

  • Familiarity with [RELEVANT DOMAINS - e.g., "data engineering", "ML deployment", "enterprise SaaS"]
  • Side projects or hackathons that show you can build things independently
  • Experience working through ambiguity (startups, research projects, etc.)

Explicit Non-Requirements:

  • Specific programming language expertise (you'll learn on the job)
  • Years of experience (we care about attitude and ability)
  • Top school or big tech background

What We Offer

Compensation:

  • Base Salary: [$X - $Y] (competitive with mid-level engineering roles)
  • Equity: [SPECIFY IF APPLICABLE]
  • [OTHER COMPENSATION ELEMENTS]

Why This Matters:

We pay FDEs at or above traditional engineering levels because this role requires technical skills PLUS client-facing skills PLUS pain tolerance PLUS ownership mindset. We don't lowball—good people have options.

Benefits:

  • [LIST YOUR BENEFITS - health insurance, 401k, PTO, etc.]
  • [FDE-SPECIFIC PERKS - travel budget, client visit opportunities, etc.]

What You'll Gain:

  • Learn how software actually gets used (not just built)
  • Direct impact on client outcomes
  • Exposure to diverse industries and problems
  • Faster learning curve than traditional engineering roles
  • Clear path to Senior FDE and beyond

How to Apply

[APPLICATION INSTRUCTIONS]

Include in your application:

  • Resume/CV
  • Brief note (2-3 paragraphs) on why FDE work appeals to you
  • Link to code you've written (GitHub, project, anything that shows your work)

Template: FDE (Mid-Level)

[COMPANY] - Forward Deployed Engineer

Location: [LOCATION / REMOTE] Type: Full-time


About [COMPANY]

[2-3 sentences about your company, product, and mission]


The Challenge

As an FDE, you'll own client outcomes from demo through production. You'll work at the intersection of engineering and client success, building on our platform to solve specific client problems.

This is not staff augmentation—you own whether the client succeeds. This is not pure consulting—you build working software, not slide decks. This is not support—you deploy new solutions, not maintain old ones.

What makes this hard:

  • Clients have messy data, broken environments, and unclear requirements
  • You'll need to work across frontend, backend, data, and infrastructure
  • You'll navigate ambiguity and make judgment calls
  • You'll explain technical complexity to non-technical stakeholders
  • You'll own delivery timelines and client commitments

What You'll Do

Client Deployment (60-70% of time):

  • Lead technical work for client pilots and production deployments
  • Build client-specific customizations on top of [PRODUCT]
  • Integrate [PRODUCT] with client systems and data
  • Deploy solutions in client environments (cloud or on-premise)
  • Train client teams on how to use and extend what you've built

Demo & Pre-Sales (15-20% of time):

  • Build client-specific demonstrations
  • Participate in technical discovery calls
  • Scope what's feasible given [PRODUCT] capabilities

Product Contribution (10-15% of time):

  • Identify patterns across clients that should be product features
  • Contribute code to [PRODUCT] based on field gaps
  • Document what you learn to enable future FDEs
  • Provide feedback to Product team on roadmap priorities

What We're Looking For

Must-Have:

  • 2-5 years of engineering experience - You've built production systems and know how software breaks in the real world.
  • Full-stack capability - You can work across frontend, backend, data, and infrastructure as needed. You don't have to be expert at all, but you can't say "I only do backend."
  • Learning velocity - You pick up new domains and technologies quickly. You've taught yourself things outside your core expertise.
  • Pain tolerance - You push through broken environments, missing documentation, and unclear requirements without constant escalation.
  • Client communication - You explain technical concepts clearly to non-technical stakeholders. You listen before prescribing solutions.
  • Ownership mindset - You deliver what was promised. When things go wrong, you figure it out instead of pointing fingers.

Nice-to-Have:

  • Domain expertise in [TARGET VERTICALS - e.g., "finance", "healthcare", "retail"]
  • Prior consulting, solutions engineering, or client-facing technical work
  • Experience with early-stage products or ambiguous environments
  • [SPECIFIC TECHNICAL SKILLS RELEVANT TO YOUR PRODUCT - e.g., "Python", "React", "data pipelines"]

Explicit Non-Requirements:

  • Specific programming language expertise (you'll learn our stack)
  • Pedigree (big tech, top school) - we care about ability and attitude

What We Offer

Compensation:

  • Base Salary: [$X - $Y] (at or above senior engineering levels)
  • Equity: [SPECIFY IF APPLICABLE]
  • [OTHER COMPENSATION ELEMENTS]

Philosophy:

FDEs need engineering skills + client skills + pain tolerance + ownership mindset. We pay accordingly. Underpaying attracts people who can't get better offers—that's not who we want.

Benefits:

  • [LIST YOUR BENEFITS]
  • [FDE-SPECIFIC - travel, client visits, conference budget, etc.]

What You'll Gain:

  • Ownership of real client outcomes (not just shipping features)
  • Diverse problem exposure across industries
  • Direct influence on product roadmap
  • Faster career growth than traditional engineering paths
  • Client relationships and business context

How We Compare:

  • vs. Big Tech: We offer more impact, variety, and ownership (less process)
  • vs. Consulting: We offer more technical depth and building (less PowerPoint)
  • vs. Startups: We offer more client exposure and real-world constraints (less theory)

How to Apply

[APPLICATION INSTRUCTIONS]

Include:

  • Resume/CV
  • Brief explanation of why FDE work interests you
  • Example of a time you figured something out with minimal guidance
  • Link to code or projects you've built

Template: Senior FDE

[COMPANY] - Senior Forward Deployed Engineer

Location: [LOCATION / REMOTE] Type: Full-time


About [COMPANY]

[2-3 sentences about your company, product, and mission]


The Challenge

As a Senior FDE, you'll lead complex client engagements, mentor junior FDEs, and shape how we deploy [PRODUCT] in the field. You'll own multi-month deployments, make architectural decisions under constraints, and ensure clients succeed.

This role assumes you already know how to operate as an FDE. We're looking for people who can:

  • Work independently on ambiguous problems
  • Lead technical work while managing client expectations
  • Make sound judgment calls when requirements are unclear
  • Contribute to product architecture based on field learnings
  • Help junior FDEs level up

What You'll Do

Complex Client Engagements (50-60%):

  • Lead technical work for [COMPANY]'s most strategic deployments
  • Architect solutions that balance client needs, [PRODUCT] capabilities, and maintainability
  • Navigate challenging client environments (legacy systems, data quality issues, org politics)
  • Own delivery timelines and client commitments
  • Escalate smartly when blocked (with context and attempted solutions)

Mentorship & Enablement (20-25%):

  • Pair with Associate and Mid-level FDEs on their engagements
  • Review FDE code contributions and provide technical guidance
  • Create documentation and tooling that helps future FDEs
  • Participate in FDE hiring (interviews, calibration)

Product & Platform Influence (15-20%):

  • Identify systemic gaps in [PRODUCT] that affect multiple clients
  • Contribute significant code to [PRODUCT] codebase
  • Participate in architecture discussions with Product team
  • Help prioritize roadmap based on field patterns

What We're Looking For

Must-Have:

  • 5+ years of engineering experience with demonstrated client-facing success
  • Proven independence - You've led projects with minimal oversight and delivered
  • Technical breadth - Deep in 1-2 areas, competent across the stack
  • Client management - You've navigated difficult client situations and kept projects on track
  • Teaching ability - You can explain complex concepts and help others level up
  • Judgment under ambiguity - You make good decisions when requirements are unclear
  • Systems thinking - You see patterns across problems and build reusable solutions

Nice-to-Have:

  • Experience leading deployments in [TARGET INDUSTRIES]
  • Background in [TECHNICAL AREAS RELEVANT TO YOUR PRODUCT]
  • Prior consulting, solutions architecture, or technical account management
  • Open source contributions or technical writing

What We Offer

Compensation:

  • Base Salary: [$X - $Y] (above senior engineering levels)
  • Equity: [SPECIFY IF APPLICABLE]
  • Performance bonus: [IF APPLICABLE]

This role requires the full FDE skill set (engineering + client + grit + ownership) PLUS leadership and mentorship. We pay accordingly.

Benefits:

  • [LIST YOUR BENEFITS]
  • [SENIOR-SPECIFIC PERKS]

Impact:

  • Lead [COMPANY]'s most important client relationships
  • Shape how we deploy [PRODUCT] across industries
  • Influence product roadmap directly
  • Build and mentor the next generation of FDEs
  • Clear path to Staff/Principal or FDE leadership

How to Apply

[APPLICATION INSTRUCTIONS]

Include:

  • Resume/CV with specific client engagement examples
  • Explanation of your most challenging deployment and how you navigated it
  • Links to code, writing, or projects that demonstrate your technical depth

Template: Staff/Principal FDE

[COMPANY] - Staff/Principal Forward Deployed Engineer

Location: [LOCATION / REMOTE] Type: Full-time


About [COMPANY]

[2-3 sentences about your company, product, and mission]


The Challenge

As a Staff/Principal FDE, you'll set the technical direction for how [COMPANY] deploys [PRODUCT] in the field. You'll lead our most complex engagements, define FDE practices and standards, and ensure our platform meets field reality.

This role requires:

  • Leading multi-workstream engagements across multiple stakeholders
  • Making architectural decisions with incomplete information
  • Teaching and leveling up the entire FDE team
  • Influencing product architecture based on deployment patterns
  • Representing FDE perspective in company-wide technical decisions

What You'll Do

Strategic Client Engagements (40-50%):

  • Lead [COMPANY]'s highest-stakes deployments
  • Work with C-level stakeholders and technical executives
  • Architect solutions that will scale to dozens of clients
  • Navigate complex organizational and technical constraints
  • Set the standard for how FDE work should be done

FDE Team Leadership (25-30%):

  • Define FDE practices, patterns, and standards
  • Mentor Senior FDEs and help them reach Staff level
  • Participate in FDE hiring strategy and calibration
  • Build internal tooling and documentation that scales FDE impact
  • Represent FDE needs in cross-functional planning

Product & Architecture Influence (25-30%):

  • Drive product roadmap based on field patterns
  • Make significant architectural contributions to [PRODUCT]
  • Identify and champion systemic improvements
  • Partner with Product and Platform teams on technical direction
  • Ensure [PRODUCT] is designed for real-world deployment

What We're Looking For

Must-Have:

  • 8+ years of engineering experience with substantial client-facing work
  • Proven leadership - You've led complex projects with multiple stakeholders and workstreams
  • Strategic thinking - You see patterns, identify root causes, and build scalable solutions
  • Technical depth - You're expert in multiple areas and can dive deep when needed
  • Influence without authority - You've successfully changed how teams work
  • Exceptional judgment - You make good decisions under pressure with incomplete information
  • Teaching & mentorship - You've helped multiple engineers reach senior+ levels

Nice-to-Have:

  • Experience building or scaling FDE, solutions, or consulting teams
  • Track record of technical writing, speaking, or open source contributions
  • Deep expertise in [DOMAINS RELEVANT TO YOUR PRODUCT]

What We Offer

Compensation:

  • Base Salary: [$X - $Y] (principal engineer equivalent or above)
  • Equity: [SPECIFY]
  • Performance bonus: [IF APPLICABLE]

Staff/Principal FDEs are among our most valuable employees. Compensation reflects that.

Benefits:

  • [LIST YOUR BENEFITS]
  • [STAFF-LEVEL PERKS]

Impact:

  • Define how [COMPANY] delivers [PRODUCT] to clients
  • Influence product architecture and company strategy
  • Build and shape the FDE organization
  • Work on [COMPANY]'s most important and challenging problems
  • Potential paths to VP of Field Engineering or similar leadership roles

How to Apply

[APPLICATION INSTRUCTIONS]

Include:

  • Resume/CV with emphasis on leadership and client impact
  • Description of your most complex engagement and how you led it
  • Examples of how you've influenced technical direction at previous companies
  • Links to technical writing, talks, or code that demonstrates your depth

Archetype Variants

FDEs specialize into two main archetypes. Consider which you need more when writing your job description.

Business-Facing FDE

Focus: Finding market fit, land & expand

Day-to-Day:

  • Embed with clients to identify pain points
  • Build trust with client stakeholders
  • Identify new use cases for [PRODUCT]
  • Drive adoption and expansion
  • Translate business problems into technical requirements

When to hire:

  • You have 10+ deployments and want to scale
  • You need help with land & expand motions
  • Your product is mature enough that deployment is mostly known

Traits to emphasize in job description:

  • Client relationship building
  • Business acumen and commercial awareness
  • Communication and stakeholder management
  • Use case identification
  • Adoption and change management

Product-Facing FDE

Focus: Filling product gaps, building reusable patterns

Day-to-Day:

  • Build the 15-20% [PRODUCT] doesn't cover
  • Contribute heavily to [PRODUCT] codebase
  • Create reusable components for future deployments
  • Document patterns and best practices
  • Partner closely with Product team on architecture

When to hire:

  • You have 0-10 deployments and are figuring out patterns
  • Your product has significant gaps for client needs
  • You need to build deployment infrastructure

Traits to emphasize in job description:

  • Deep technical capability
  • Systems thinking and architecture
  • Code quality and maintainability
  • Platform development mindset
  • Documentation and knowledge sharing

Most Organizations Need Both

Individual FDEs specialize, but your team needs both archetypes. Early stage: start product-facing. Scaling stage: add business-facing.

How to adapt job descriptions:

  • For business-facing roles: Add more emphasis on client relationships, business context, use case discovery
  • For product-facing roles: Add more emphasis on technical depth, architecture, platform contributions
  • For generalist roles: Keep balanced between both—most FDEs do a mix

Usage Notes

Getting Compensation Right

Don't lowball. FDE roles require:

  1. Engineering skills (write production code)
  2. Client skills (communicate effectively, manage relationships)
  3. Pain tolerance (work through ambiguity and broken systems)
  4. Ownership mindset (deliver outcomes, not just tasks)

If you pay below market, you'll attract candidates who couldn't get better offers. That's not who you want.

Benchmark against:

  • Senior/Staff engineers at your company (FDEs should be at or above)
  • Consulting firms (McKinsey, BCG) - you offer more technical depth
  • Big tech (Google, Meta) - you offer more impact and variety

Setting Realistic Expectations

Keep "The Challenge" sections. They filter out candidates who think this is a traditional engineering role. You want people who read it and think "Yes, that sounds hard and interesting."

Don't oversell. FDE work involves:

  • Broken client environments
  • Missing documentation
  • Unclear requirements
  • Stakeholder management
  • Travel (if applicable)

Be honest about this. The right candidates will find it appealing.

Common Mistakes

Mistake: Requiring specific tech stack

  • Fix: Focus on learning ability, not current knowledge
  • FDEs will work with whatever the client has—your stack is just one part

Mistake: Over-indexing on "nice" communication

  • Fix: Look for clarity and conviction, not agreeableness
  • FDEs need to push back on clients sometimes

Mistake: Vague "What You'll Do" sections

  • Fix: Be specific about client work, product contribution, and time allocation
  • Candidates should understand the job, not a generic description

Mistake: Not explaining archetype focus

  • Fix: Clarify whether this role leans business-facing or product-facing
  • Wrong archetype = poor fit even if candidate is qualified

Adaptation by Stage

Pre-Product-Market Fit:

  • Emphasize: ambiguity, building from scratch, figuring out what works
  • De-emphasize: established processes, proven playbooks
  • Consider: Product team may act as FDEs for first 1-2 clients

Early Stage (0-10 deployments):

  • Focus on product-facing FDEs
  • Emphasize: technical depth, platform contributions, documentation
  • Expect: significant code contributions to core product

Scaling Stage (10+ deployments):

  • Add business-facing FDEs
  • Emphasize: client relationships, use case discovery, adoption
  • Expect: less core product contribution, more client customization

Enterprise/Mature:

  • Need both archetypes in team
  • May have specialized roles (field CTO, solutions architect, etc.)
  • Clear career paths to FDE leadership roles