Every client setup creates improvements that we bring back into the platform as reusable modules. Over time, even Growth Managers will become engineers, closing the loop: the same people who hear client needs can immediately build the solution. This makes delivery and product the same thing — a breathing, modular platform that evolves through every engagement.

The Role: Forward-Deployed Engineer (FDE)

Forward-Deployed Engineers are the first wave of this model. You’ll work directly with clients — supported by Growth Managers — to set up accounts, configure ICPs, and connect every part of the platform:

• Data (contact enrichment, ICP setup in graph8 grid UI)
• Sequencer (multi-channel campaigns)
• Chat & voice AI
• Calendars & scheduling
• Billing & reporting

As you implement workflows, you’ll identify gaps, extend the data sources, and turn solutions into productized features. FDEs are engineers embedded in delivery: close enough to the client to capture real needs, technical enough to build solutions that scale.

Responsibilities:

Client setup as engineering

• Translate ICP and workflow requirements into structured configs and datasets.
• Connect enrichment flows using third party tools, vendor APIs, and internal tools.
• Verify and deliver high-quality data back into the client account.

Engineering reusable modules

• Convert client-specific workflows into PRDs and productized functionality.
• Implement enrichment waterfalls, scraping scripts, or connectors to expand our dataset.
• Normalize titles, industries, and data fields for reusability.

Operate across the platform

• Configure calendars, chat widgets, voice AI, sequencers, and billing systems.
• Ensure systems are tested, observable, and repeatable.

Continuous improvement

• Document workflows as modules.
• Feed learnings from client delivery back into the product team.
• Track metrics: throughput, accuracy, bounce %, cost per verified record.

Practical Example

A client needs new data points for their ICP. You’ll:

• Capture requirements and configure them in our data platform (similar to clay).
• Deliver enriched records (cleaned, verified, deduped).
• Extend with extra scraping or data sources as needed.
• Turn that solution into a PRD + functional module so the next client can use it out-of-the-box.

Requirements

• 2+ years experience in data engineering, applied research, or full-stack/data-heavy delivery.
• Python & SQL proficiency (ClickHouse/Snowflake preferred).
• Comfortable with APIs, enrichment tools (Clay, Apollo, Clearbit, etc.), and dedupe/normalization.
• Hands-on with data modeling, enrichment waterfalls, and QA.
• Strong problem-solving skills, able to move between client-facing configs and backend engineering.

Nice-to-Have:

• Workflow orchestration (Temporal, Airflow, Prefect).
• Familiarity with Segment, AG Grid, dbt, or scraping frameworks.
• Knowledge of GTM systems: sequencers, chat, voice AI, calendaring.

Who You Are

• Engineer first, operator second — you automate where others repeat.
• Forward-deployed mindset — you thrive at the edge with clients, but think in systems and modules.
• Builder DNA — you leave behind reusable workflows, not ad-hoc hacks.
• Outcome-driven — you measure success in verified data delivered, workflows stabilized, and modules shipped.

Why Join graph8

• Be at the frontline of product + delivery unification.
• Work in a small, engineering-driven culture where every client setup evolves the product.
• Build the GTM OS of the AI era — a platform that scales through every client engagement.

Application Process

• Intro call + engineering background review.
• Live coding: API enrichment wrapper + ClickHouse dedupe.
• System design: Client → Config → Enrichment → Productized module.
• Paid take-home: Deliver an ICP dataset + PRD + re-usable workflow.

 To apply: Send us your GitHub/code sample, an enrichment workflow you’ve built, and a short note on how you’d turn a client-specific request into a reusable module.