Now hiring FDEs

Become a Forward Deployed Engineer.

We're hiring a small number of Forward Deployed Engineers (FDEs) to run their own customer book — shadow the operator, author the kit, install Hueks, and coach. You'd be the one whose name ends up on the SKILL.md.

The pitch

An FDE owns the kit, the customer, and the coaching relationship.

Workflow Kits ships bespoke agent kits to the person who owns a domain of knowledge — a GM, a practice owner, a workshop manager — with information flowing to, from, and through them, and the judgement theirs alone. We don't do platforms. We don't do delivery teams. Every kit is hand-authored by one person who sat next to that customer the week before.

A Forward Deployed Engineer (FDE) embeds with one operator at a time — the term comes from deploying an engineer into the field, next to the customer. That's the whole job: you'd run your own book of three to five operators, take each through the discovery sprint, author their SKILL.md, install Hueks on their machine, and hold the coaching that keeps the kit sharp.

This is not a junior role. It is a hybrid of strategist, ops engineer, and product builder. The customer is a GM, a practice owner, a workshop manager — they already know their business better than you do. Your job is to map it, harness it, and ship a kit they trust to run unattended between coaching sessions.

If you've spent a decade collecting careers in strategy, operations, and engineering — and you've quietly been building things with Claude on the side — this is the role that finally uses all of it at once.

Open role

Forward Deployed Engineer · Workflow Kits.

Forward Deployed Engineer (Kit author)
Cape Town · remote-friendly · Full-time or fractional · Direct report: Kahueka
Now open

What you'd own

One FDE runs one customer book. We'd hand you three to five operators across the industries we serve, and you'd own each engagement end to end.

  • Discovery sprint — shadow the operator, map the four information sources that feed their workflow.
  • Kit authoring — write the SKILL.md by hand. What Hueks owns, what he does NOT touch, the slash commands, the memory.
  • Installation — set the kit up on the operator's machine. Author the first workflow into the kit.
  • Coaching — front-loaded then tapering on a schedule agreed upfront, refining what Hueks knows and retiring skills that aren't earning their keep.
  • Customer relationship — you are the studio to them. Their trust is yours to earn and keep.

What you'd need

Three things are non-negotiable. The fourth is the tell.

  • A career across strategy, operations, and tech. Not one of the three — all three, in some order, at some depth. Consulting, in-house ops, founding teams, engineering, design — we read the mosaic, not the title.
  • Receipts in production. Real customers, real revenue, real shutdowns, real outages. You've shipped, broken, and fixed things in the world.
  • Comfortable in the file system. Terminal, git, markdown, Claude Code. You don't need to be a senior engineer; you do need to be at home where a kit lives.
  • A portfolio of things you've built with Claude. Skills you've authored. Tools you've vibe-coded. Workflows you've automated for yourself before anyone paid you to. This is the tell — see below.
Who we're looking for · three pillars

A diverse career, on purpose.

FDEs sit at the intersection of three disciplines. The job is impossible if you've only done one of them.

01 — Strategy

You can see the whole business in one sitting.

Consulting, founder, product lead, COO — somewhere you've had to read a business top-to-bottom and decide what's worth doing. You can tell the difference between a workflow worth automating and one that's a vanity project.

Read the business. Pick the lever.
02 — Operations

You've actually run things, not just advised on them.

You've owned a P&L line, a delivery team, a rollout, or a function. You know the difference between a process on a slide and a process at 5pm on Friday. You respect the prep sheet pinned by the line.

Ship the thing. Hold the bag.
03 — Tech

You build with your hands.

You write code, even if it's not your day job. You've vibe-coded internal tools, you live in the terminal, you have opinions about file structure. You've written a SKILL.md, even if you didn't call it that.

Type. Ship. Iterate.
The tell · your portfolio

Show us what you've already built with Claude.

The single fastest way to skip the small talk. Send a short index of things you've shipped — skills, agents, internal tools, weekend hacks, anything you've vibe-coded that actually does work.

portfolio.md · what we're looking for
— at least 3 things you've built. ideally 6+. doesn't matter if they're rough.
— for each one: name · what it does · who used it · the link or the screenshot

+ a Claude Code skill you authored — even a personal one
+ an agent or workflow you ran on your own data
+ a vibe-coded internal tool that replaced a spreadsheet
+ an MCP server, a CLI, a script that automates the boring part of your week
+ a side project you ship from on weekends — yours or someone else's

heuristic: if you'd be embarrassed for us to see it, you're probably the right candidate. send it anyway.
Signal & anti-signal

Honest sorting, both ways.

+ You probably fit.

  • Your CV reads like four careers stitched together and you can't quite explain the through-line in one sentence.
  • You've started a thing, run a thing, sold a thing, or shut a thing down.
  • You have a GitHub or a Notion or a folder of half-built things that nobody asked you to make.
  • You've used Claude Code or the Anthropic SDK on something real, however small.
  • You like sitting next to operators and asking how they actually do the thing.
  • You're allergic to slide-ware.

You probably don't.

  • You want a defined role with a clean job description and a quarterly OKR cascade.
  • You've never owned a customer relationship end-to-end.
  • Your relationship with AI is screenshotting ChatGPT into slides.
  • You think "shadowing the operator" is a euphemism for being a consultant.
  • You want to be a platform PM more than you want to ship a kit on Friday.
  • You haven't built anything outside of a corporate stage gate in a long time.
How we hire

Five steps. No take-home busywork.

The process is shaped like the work. You'll spend most of it actually building, not interviewing.

01

Send your portfolio.

Email hello@workflowkits.ai with the things you've already shipped. CV optional, links preferred.

Step 1 · async
02

30-minute call with Kahueka.

We walk through your three careers — strategy, operations, tech — and the through-line you've never quite named.

Step 2 · 30 min
03

Shadow a real discovery sprint.

You sit in on a live customer engagement — not a mock interview. You watch how a kit gets shaped from a real desktop. Paid.

Step 3 · half-day
04

Author a kit for a fictional customer.

We give you a fictional brief (think: Nightingale Kitchen). You ship a SKILL.md, a folder structure, and a first workflow. Two days max.

Step 4 · ≤ 2 days
05

Co-run a coaching session.

You join Kahueka on a real coaching session with an existing customer. If the customer would happily have you back, the offer follows the same week.

Step 5 · 1 hr
Apply as an FDE

Send the portfolio first.
The CV can come later.

One email, one paragraph about you, and the links to the things you've actually built. We read every one.