
Data & notes
| Company | Employed | Open | Employed per open role |
|---|---|---|---|
| IBM | 116 | 14 | 8.3× |
| Salesforce | 243 | 109 | 2.2× |
| Databricks | 163 | 91 | 1.8× |
| Microsoft | 35 | 0 | not captured |
Read the multiple first
Name the destination wire you want covered when you ask for the list. Keep the request inside the companies and titles already shown.
Key takeaway · How to cite
Who holds the deepest Forward Deployed Engineer bench? Salesforce at 243
Start with who already employs the most, as of 2026-11-15 PT.

Data & notes
| Name | Value |
|---|---|
| Salesforce | 243 |
| Databricks | 163 |
| IBM | 116 |
| Microsoft | 35 |
| Host | Employed | Open |
|---|---|---|
| IBM | 116 | 14 |
| Salesforce | 243 | 109 |
| Databricks | 163 | 91 |
| Microsoft | 35 | not captured |
Get the named Forward Deployed Engineer list behind this table
Point the list request at the employers and wires already counted here. Name the same employers and experience cut this page measured.
Which host has the highest employed-vs-open ratio? IBM 8.3× (116 employed / 14 open)
Multiple = employed ÷ captured open. IBM 8.3× (116 employed / 14 open); Salesforce 2.2× (243 employed / 109 open); Databricks 1.8× (163 employed / 91 open); Microsoft 35 employed, open roles not captured. The ratio chart above ranks every host.
Absolute employed beside opens: ratio lead IBM, bench lead Salesforce
The two rankings can diverge: bench volume and door density are different decisions.

Data & notes
| Category | Employed | Open roles |
|---|---|---|
| IBM | 116 | 14 |
| Salesforce | 243 | 109 |
| Databricks | 163 | 91 |
| Microsoft | 35 | 0 |
What it means for Forward Deployed Engineer employed vs open: what to do this week / how to use it
For door density this week: prefer the IBM multiple at 8.3× (116 employed / 14 open).
- For bench volume: prefer the Salesforce pool of 243 employed.
- For live reqs: prefer Salesforce's 109 captured open roles.
What the ratio leaves out
Open roles were not captured at Microsoft. Those hosts are listed in grey, with the employed count and no bar, and they are excluded from employed per open role. There is no five-host peer-pack ladder here: the comparison is employed per open role on one seat.
As of 2026-11-15 PT · Source: Metix AI
Notes & method
Methodology
Employed counts Forward Deployed Engineer on the company homepage record at 2026-11-15 PT. The open cell counts postings still open for this title family. A recorded 0 means open roles were not captured, not that demand is zero. Source: Metix AI.
FAQ
- Does an uncaptured Forward Deployed Engineer host get a bar?
- If open roles were not captured, that host is shown without a ratio bar. Not captured is the reading of an open cell at 0.
- Is the Forward Deployed Engineer page a peer-pack ladder?
- It is an employed-per-open reading for Forward Deployed Engineer, not a five-company ladder. Uncaptured hosts are excluded from the multiple.
- Who leads the Forward Deployed Engineer multiple?
- Lead with IBM 8.3× (116 employed / 14 open) when you name the top multiple. Read it as of 2026-11-15 PT.
- Where do the Forward Deployed Engineer figures come from?
- 2026-11-15 PT dates both the employed cell and the open cell. Published by Metix AI.
Request the Forward Deployed Engineer open-req list
Point the list request at the employers and wires already counted here. The scope line is the whole request.
Optional: try Mira
