Card 05JobsSeptember 21, 2026

Nearly two in three forward-deployed engineering openings are in the US

Name: Nearly two in three forward-deployed engineering openings are in the US
Published: 2026-09-21
License: https://creativecommons.org/licenses/by/4.0/

Open postings with "forward deployed" in the title, by country, on the Metix AI Platform on September 21, 2026.

Run it
13 API Credits to reproduce

64.8%

of 5,868 open forward-deployed engineering postings are in the US (3,801).

United States 65%
Every other country 35%

Next: India 5%, United Kingdom 5%, Germany 4%.

The US holds nearly two thirds. India is second, with 5%.

Open postings with "forward deployed" in the title, by country, drawn as a share of all 5,868 worldwide

United States3,801 · 64.8%
India309 · 5.3%
United Kingdom274 · 4.7%
Germany241 · 4.1%
Canada116 · 2.0%
Japan86 · 1.5%
Singapore82 · 1.4%
France80 · 1.4%
Australia71 · 1.2%
Spain57 · 1.0%
Netherlands39 · 0.7%
Israel19 · 0.3%
Rest of the world693 · 11.8%

What it shows

Worldwide, 5,868 open postings have "forward deployed" in the title, and 3,801 of them, 64.8%, are in the US. India is second with 309, then the United Kingdom and Germany.

Five European countries (the United Kingdom, Germany, France, the Netherlands, and Spain) have 691 together, 11.8%, about as many as every country outside the list combined (693). The title is still mostly an American one.

Method and limits

A role listed in several cities or reposted counts more than once, so these numbers measure how loudly the title is advertised, not how many seats exist.

Source: Metix AI Platform, jobs, 2026-09-21.

Queryforward-deployed.json

POST /v1/jobs/query · queries/forward-deployed.json

{  "where": {    "field": "title",    "match": "forward deployed"  },  "size": 1}

Run it

Three ways in. Each says what it costs before you start.

1 API Credit buys 25 search results or 5 full records; $1 buys 30 API Credits.

Run it in your agent

130 to 145 API Credits$4.33 to $4.83More than the 100 free API Credits

Your agent stops and asks before spending more than 150 API Credits.

Your agent follows the prompt step by step: it reads the rules, runs the counts, checks the definitions the prompt asks it to check, and writes the files and charts. Use an agent that can write files, such as Claude Code or Codex.

Set up onceKey, connection, and a free check. Skip this if your agent already reaches the Platform.

1Get a key
Create a key on the Metix AI Platform →
New accounts get 100 API Credits once, valid for 30 days. Set the key in the shell you start your agent from, or add the line to ~/.zshrc or ~/.bashrc so every new terminal has it:
Shell
```
export METIX_KEY=metix_xxxxxxxx
```
2Connect your agent
Claude Code
Registers the Platform for every project. Start claude in any folder and the ten metix tools are there.
Shell
```
: "${METIX_KEY:?run step 1 first}" &&
claude mcp add --scope user --transport http metix \
  https://mira-api.metix.ai/mcp \
  --header "Authorization: Bearer $METIX_KEY"
```
MCP setup guide →
Codex
Registers the same server. The key stays in your environment instead of the config file.
Shell
```
codex mcp add metix \
  --url https://mira-api.metix.ai/mcp \
  --bearer-token-env-var METIX_KEY
```
MCP setup guide →
Skills
Four skills that teach any agent the Platform's endpoints and query rules, for agents without MCP. The installer starts with none ticked: press space on each, then enter.
Shell
```
npx skills add MetixAI-Official/metix-skills
```
Skills install guide →
Other MCP
Point the client at this endpoint over streamable HTTP with both headers; without the Accept header the server answers 406. Older clients use /sse on the same host.
Endpoint and headers
```
https://mira-api.metix.ai/mcp
Authorization: Bearer <your key>
Accept: application/json, text/event-stream
```
MCP setup guide →

3Check the setup

Ask this first. It reads your balance and the field list, runs no search, and costs nothing:

Prompt for your agent

Use the Metix AI Platform to check my key status and read the contract; both are free. Then tell me my API Credit balance and which datasets I can query. Do not run any search.

4Paste the prompt

Start your agent in an empty folder, then paste. It writes its files there.

The question

Answer one question with the Metix AI Platform: in which countries are companies hiring forward-deployed engineers? Work only through the public Platform (REST at https://mira-api.metix.ai, the MCP server, or the metix-skills) with the key in METIX_KEY, and never print the key.

01Read before querying
Call GET /contract (free) and use only querySpecByEntity.job fields. A count with size 1 costs 1 API Credit. Check the balance with GET /auth/key/status (free) at the start and at the end, and stop and ask before the run passes 150 API Credits.
02Population
Open postings whose title matches "forward deployed". The phrase rarely means anything else; read 25 titles to confirm.
03Count the whole population first
One worldwide count, size 1.
04Find the countries
Read the country of about 500 postings to learn which countries appear. Search results come in their own order, not a random one, so this read only chooses the countries: never publish a share computed from it.
05Count each country
For the twelve largest in that read, count with location.country eq the country name, size 1 each. The rest of the world is the worldwide count minus their sum.
06Clean
Reposts and multi-city listings are not collapsed; say that the numbers measure how loudly the title is advertised, not how many seats exist.
07Group
Twelve countries and the rest of the world, the list written into the script.
08Outputs
Write data/countries.json with "unit": "jobs", the snapshot date, the worldwide count, and each country's count and share. Report the balance from GET /auth/key/status before and after as the cost.
09Chart
One bar per country scaled to the worldwide total, the US highlighted, the rest of the world plain and last. Title it with the finding.
10Limits
Titles only; the same work under another title (solutions engineer, for example) is not counted. One day, not a trend.

Read PROMPT.md →

What you get

The aggregate files and the chart, a note on what the audits found and what they changed, and the API Credits the run spent, read from the balance before and after.

A call that returns 402 insufficient_quota means the key works and the balance is empty.

Reproduce the numbers

13 API Credits$0.43Fits in the 100 free API Credits

A short standard-library Python script sends the committed queries as counts and writes the aggregate files this page is built from. It needs Python and METIX_KEY set in the shell (step 1 of the agent path); your agent can run these lines for you as well.

Shell

curl -fsSL https://platform.metix.ai/casebook/source/forward-deployed-engineers-2026.tar.gz | tar xz
cd forward-deployed-engineers-2026
: "${METIX_KEY:?set METIX_KEY first}" && python3 cases/forward-deployed-engineers-2026/fetch.py

What you get

data/*.json and data/receipt.json. Run git diff cases/forward-deployed-engineers-2026/data to see what moved: the numbers should match, apart from what changed in the data since the snapshot.

Adapt it

Costs what your version reads. Write your own ceiling into step 1 of the prompt.

The prompt is the case. Change the parts in this table and your agent answers your question instead, with the same checks and the same way of reporting cost.

To change	Edit	For example
The role	Step 2	"solutions engineer", "applied AI engineer", "AI deployment"
The breakdown	Steps 4 and 5	Cities within one country, or a list of companies
The window	Step 2	Add posted_date gte now-30d for recent postings only

What to ask before running it

Which title, and does it mean anything else?
Countries, cities, or companies?
Everything open, or only recent postings?
How many API Credits may the discovery read spend?

Read PROMPT.md →

Answer one question with the Metix AI Platform: in which countries are companies hiring forward-deployed engineers? Work only through the public Platform (REST at https://mira-api.metix.ai, the MCP server, or the metix-skills) with the key in METIX_KEY, and never print the key.

1. Read before querying. Call GET /contract (free) and use only querySpecByEntity.job fields. A count with size 1 costs 1 API Credit. Check the balance with GET /auth/key/status (free) at the start and at the end, and stop and ask before the run passes 150 API Credits.

2. Population. Open postings whose title matches "forward deployed". The phrase rarely means anything else; read 25 titles to confirm.

3. Count the whole population first. One worldwide count, size 1.

4. Find the countries. Read the country of about 500 postings to learn which countries appear. Search results come in their own order, not a random one, so this read only chooses the countries: never publish a share computed from it.

5. Count each country. For the twelve largest in that read, count with location.country eq the country name, size 1 each. The rest of the world is the worldwide count minus their sum.

6. Clean. Reposts and multi-city listings are not collapsed; say that the numbers measure how loudly the title is advertised, not how many seats exist.

7. Group. Twelve countries and the rest of the world, the list written into the script.

8. Outputs. Write data/countries.json with "unit": "jobs", the snapshot date, the worldwide count, and each country's count and share. Report the balance from GET /auth/key/status before and after as the cost.

9. Chart. One bar per country scaled to the worldwide total, the US highlighted, the rest of the world plain and last. Title it with the finding.

10. Limits. Titles only; the same work under another title (solutions engineer, for example) is not counted. One day, not a trend.

Method and limits

How the population was defined, counted, and checked, and what the numbers cannot show.

Population

Open postings on the Metix AI Platform on September 21, 2026 with "forward deployed" in the title. The phrase rarely means anything else, so no exclusions are needed.

Choosing the countries

The agent first read 500 postings to see which countries appear, and took the top 12. Search results come in their own order, not a random one, so those 500 only chose the countries; every number comes from a count per country in the replay, and everything outside the list is the rest of the world. The sample put the US at 51%; the full count says 64.8%, which is why a sample never sets a number here.

Counting

One worldwide count and one per country, one API Credit each, and no posting is read. Reposts are not collapsed. The condition is in queries/ and the country list in fetch.py.

Limits

Titles only; the same work under another title (solutions engineer, for example) is not counted. This is one day, not a trend.

The last reproduction

What reproducing this case cost the last time the script ran, read from the Platform's own balance before and after.

Ran on: 2026-09-21
Calls: 13
Search results: 13
Records read: 0
API Credits: 13

Search results are IDs returned by searches, one per count query and one per match on a full search. Records are postings or profiles read in full: this case reads none.

Making this case cost about 137 API Credits more: the agent's audits, trial queries, and earlier runs that the published replay replaced. You do not pay that again.

Case files: prompt, queries, data API Credits and pricing

The US holds nearly two thirds. India is second, with 5%.

Run it

1Get a key

2Connect your agent

3Check the setup

4Paste the prompt

What to ask before running it

Method and limits

The last reproduction