Time since we first saw it
Day 59
Up longer than most. Similar jobs usually come down between day 3 and day 42.
From 633 similar postings that came down. Coming down is not always a hire.
Location not stated
Live, first seen by us 59 days agoEmployment type in the employer’s posting: Full-TimeFrom the employer’s posting
What you'll actually do: 🔹 Run discovery sessions to find the 1–3 processes worth automating (and say no to the rest) 🔹 Turn a messy, undocumented process into a real spec 🔹 Build the agent on our deepagents-based harness — tools, subagents, memory, human-in-the-loop approvals 🔹 Wire it into the client's real data, safely, with tenant isolation intact 🔹 Run shadow-review until the client trusts it, then ship the runbook and train their team Who we're looking for: ✅ 2+ years in MSP operations (or 1+ year at MSPbots in a client-facing/delivery seat) — you can read a ticket flow or collections process and know where the pain is ✅ Code-literate — you don't need to write Python from scratch, but you need to catch when AI-generated code or SQL is wrong even though it runs ✅ Comfortable with ambiguity — you can turn "our dispatch is a mess" into a spec without being handed a perfect ticket ✅ You've automated something yourself before, even informally — a script, a workflow rule, a bot ✅ Confident on camera with a skeptical client, including when the answer is "this isn't ready to automate" ✅ Willing to work between 8 AM - 5 PM CST
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 59
Up longer than most. Similar jobs usually come down between day 3 and day 42.
From 633 similar postings that came down. Coming down is not always a hire.
1 open job
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordCheck the employer’s posting for the current role and application details.
Already applied? Track this application
Forward Deployed Engineer, AI Staff — MSPbots
Most MSPs know their processes are a mess. They can't write a usable SOP, don't know which of their workflows would actually make a good AI agent, and won't self-serve their way to one.
That's where you come in.
You'll sit inside the client's operation, extract the real process from the chaos, and ship a working agent on our stack — in days, not months.
What you'll actually do:
🔹 Run discovery sessions to find the 1–3 processes worth automating (and say no to the rest)
🔹 Turn a messy, undocumented process into a real spec
🔹 Build the agent on our deepagents-based harness — tools, subagents, memory, human-in-the-loop approvals
🔹 Wire it into the client's real data, safely, with tenant isolation intact
🔹 Run shadow-review until the client trusts it, then ship the runbook and train their team
Who we're looking for:
✅ 2+ years in MSP operations (or 1+ year at MSPbots in a client-facing/delivery seat) — you can read a ticket flow or collections process and know where the pain is
✅ Code-literate — you don't need to write Python from scratch, but you need to catch when AI-generated code or SQL is wrong even though it runs
✅ Comfortable with ambiguity — you can turn "our dispatch is a mess" into a spec without being handed a perfect ticket
✅ You've automated something yourself before, even informally — a script, a workflow rule, a bot
✅ Confident on camera with a skeptical client, including when the answer is "this isn't ready to automate"
✅ Willing to work between 8 AM - 5 PM CST
New Forward Deployed Engineer postings at the employers we follow are up 225% over the last 6 weeks compared with the 6 before.
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
We file this job under Forward Deployed Engineer, by the work the posting describes.
Forward deployed engineers are placed with their employer's customers: they learn a customer's problem and write the code that makes the employer's product solve it inside the customer's own systems.
Postings ask for strong software engineering, most often in Python, ease with customers and their executives, often travel, and in about three of four cases work with large language models or AI agents.
An AI engineer or data engineer builds for their own employer's product team; a forward deployed engineer does similar work inside a customer. We give this role to every posting whose title says forward deployed.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
Location not supplied.
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.
We couldn’t identify enough role detail in this saved description to support an AI answer. Read the full posting