# Reddit is hiring FDEs to serve its own Sales, Marketing and Finance teams

> In two new Reddit FDE listings, the customers are colleagues in other departments, and a core requirement is to reduce those departments' long-term dependency on the FDE team.

Original: https://fdetimes.net/en/analysis/reddit-internal-fde-ai-enablement/

Reddit is hiring two Forward Deployed Engineers, one Senior and one Lead, both carrying the label "AI Enablement". Their customers are not outside the company. The Senior listing names Sales, Marketing, Business Development and Finance, along with the AI Platform team.

What stands out is how the listings describe a finished job. Both the Senior and the Lead postings require the engineer to transfer maintainable workflows to the owners of each function, and to reduce those functions' long-term dependency on the FDE team.

A role defined by sitting next to the customer is now being hired with a requirement to make the customer steadily need it less.

The market context makes this detail worth noting. According to the Financial Times, as cited by PYMNTS, monthly FDE job postings rose by more than 800% between January and September 2025.

When a job title spreads that fast, the way each company defines it determines what you are judged on, and Reddit has written the ability to hand over directly into the job description.

## The customer is now a colleague down the corridor

Reddit keeps the "embed" part of the FDE job but changes who it applies to. The Senior listing describes working closely with internal functions, embedding with them when needed to understand how they work, and building trust with AI champions and domain experts in each team.

Customer discovery skills therefore keep their full value. The difference is that the person you interview is a finance specialist doing month-end reconciliation, not the technical lead of a partner company.

The table below sets the external-customer FDE model, as introductory material on the profession usually describes it, alongside Reddit's listings, to show that the structure stays the same while the audience changes.

| Aspect | FDE with external customers | AI Enablement FDE at Reddit |
|---|---|---|
| Customer | The customer's organisation | Sales, Marketing, Business Development, Finance, AI Platform |
| Who takes over | The customer's own engineers, once value has been proven | The owner of each business function |
| Where shared needs go | The product team, so the solution can serve other customers | The central AI Platform Hub |
| Measure of success | The customer owns the solution | Maintainable workflows, less long-term dependency on the FDE team |

The second row is the hardest part. According to a guide from the services firm And Above, the common handover pattern is for the customer's engineers to take over once the solution has proven its value.

At Reddit, the recipient is the owner of a business function, not necessarily an engineer, so you most likely cannot just hand over a codebase and leave.

## Done means the department can run it alone

The listing also sets a demanding pace: prototypes within days, and priority workflows into production within weeks where feasible. A hypothetical case shows how heavy that pace becomes when it comes with a handover requirement.

Each month the finance team spends a lot of effort matching invoices against advertising contracts. You sit with them for a few days, then build an agent that reads invoices, compares them with contract terms and flags discrepancies.

On a demo project, you would stop once the agent ran correctly on last month's data. Under Reddit's requirements, that is only half the job. The real question is: three months after you have moved on to marketing, who in finance will know when the agent is wrong, how to switch it off, and how to adjust it when the contract template changes?

The answer shapes how you build from day one. You will choose an architecture that non-coders can still understand, write documentation for finance specialists rather than engineers, and name a single process owner who is accountable.

**Key point:** A good internal FDE builds things a department can keep running after the engineer has left.

## "Maintainable" is the part you have to define

The listing uses a single word: maintainable. It does not spell out how. But if an AI workflow is to keep running after its builder has gone, a few things are close to mandatory, and this is where you should propose them rather than wait to be asked.

Go back to the reconciliation agent. A minimal test set could be a few dozen invoice-and-contract pairs for which finance already knows the answer, rerun every time the prompt or the model changes. An approval threshold could require that any discrepancy above a set amount be signed off by a person before it is booked.

The rest is visibility. The process owner should be able to open one page and see how many cases the agent flagged this week and how many a human overruled. When someone asks why a payment was approved, finance needs to be able to point to the trail, so design the logs as a real feature.

## A solution per team, shared needs in one place

The obvious risk of this model is that every department ends up owning its own set of scripts that nobody consolidates. Reddit addresses this with two requirements. FDEs must send recurring needs, bottlenecks and infrastructure requests to the AI Platform Hub.

At the same time, whatever works well in one department must be packaged into something the whole company can reuse: agents, skills, templates, connectors, playbooks or platform patterns.

Suppose you notice that both finance and sales need to read contract PDFs. The right move then is to tell the hub this is a shared need and package the first parser as a connector, rather than write a second parser. This loop is what separates an FDE from someone who writes scripts on request.

It is the internal version of a familiar part of the job. A guide from You.com treats spotting which custom solutions could help other customers as an important part of FDE work. At Reddit, the lessons go to an internal platform, and that platform's users are also your colleagues.

## Senior and Lead: same handover, different level

The handover line appears word for word in both the Senior and the Lead listings. In other words, moving up a level does not exempt you from handing work over; it is core to the role at both levels.

For anyone comparing levels: base salary for the Senior role on Greenhouse is $180,200 to $252,300, and for the Lead role $194,600 to $272,400. For reference, Levels.fyi records median total compensation for FDEs in the US at $220,000, although total compensation and base salary are not directly comparable.

## Your CV needs to show the handover

The practical consequence is that you do not need to join an AI lab to gain FDE-style experience. If your company has a department doing a repetitive task by hand, that is a complete exercise: sit with them, prototype quickly, ship to production, then hand over.

On your CV, describe the whole loop, not just the build. A line such as "built a reconciliation agent for the finance team, set up a test set and approval thresholds, handed it over to the team lead to run independently" says more than ten lines listing frameworks.

When reading job descriptions, look for phrases such as "transfer", "function owners", "reduce dependency" and "reusable": they signal an employer that values durability over demos. In interviews, be ready to tell the story of a time you deliberately made others need you less.

That story is harder to tell than rescuing a project at midnight, but it answers exactly the question Reddit's listings pose. If this approach spreads, much of an FDE's value will lie in what keeps working well after they have moved on to another department.

**Try this week:**

- Pick a manual process in a non-technical department at your company, watch someone do it for 30 minutes and write down every step they take.
- For an internal tool or automation script you have written, draft a one-page handover document for someone who cannot code: how to run it, when to stop it, who approves, where to find the logs.
- Change one line on your CV from 'built tool X' to 'built tool X and handed it to team Y to run themselves', with a measurable figure for how much dependency fell.

## Sources

- [Senior Forward Deployed Engineer (AI Enablement) – Reddit (Greenhouse)](https://job-boards.greenhouse.io/reddit/jobs/8301784)

- [Lead Forward Deployed Engineer (AI Enablement) – Reddit (a16z jobs)](https://jobs.a16z.com/jobs/reddit/8301736--lead-forward-deployed-engineer-ai-enablement)

- [Senior Forward Deployed Engineer (AI Enablement) – Reddit (a16z jobs)](https://jobs.a16z.com/jobs/reddit/8301784--senior-forward-deployed-engineer-ai-enablement)

- [Forward-Deployed Engineers Emerge as One of AI’s Fastest-Growing Jobs](https://www.pymnts.com/artificial-intelligence-2/2026/forward-deployed-engineers-emerge-as-one-of-ais-fastest-growing-jobs/)

- [What is a forward deployed engineer (And Above)](https://www.andabove.com/feed/what-is-a-forward-deployed-engineer)

- [What is a forward deployed engineer (You.com)](https://you.com/resources/what-is-a-forward-deployed-engineer)

- [Tech's secret weapon: The complete 2026 guide to the forward deployed engineer (role, salary, and interviews)](https://hashnode.com/blog/a-complete-guide-to-the-forward-deployed-engineer)