Time since we first saw it
Day 172
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.
San Francisco Bay Area
Open 5 months, first seen by us 172 days agoWork setup in the employer’s posting: IN_OFFICEFrom the employer’s posting
Employment type in the employer’s posting: FULL_TIMEFrom the employer’s posting
Build the APIs and integrations that sit between the customer's systems and our agents.
Build the interfaces the advisors actually use.
Build the runbooks, train the end users, walk advisors and admins through the product, capture feedback in real time.
Data engineering. Map the customer's data, build the pipelines, normalize messy schemas across SIS, LMS, CRM, advancement, and finance systems. You handle missing fields, deduping, write-backs, syncs, and the long tail of edge cases that always show up in real institutions. Backend services. Build the APIs and integrations that sit between the customer's systems and our agents. Production code that runs reliably inside real institutions. Frontend work. Ship the dashboard the dean actually opens. Build the interfaces the advisors actually use. Customer-facing UI is part of the deployment, and you build it.
Backend services. Build the APIs and integrations that sit between the customer's systems and our agents. Production code that runs reliably inside real institutions. Frontend work. Ship the dashboard the dean actually opens. Build the interfaces the advisors actually use. Customer-facing UI is part of the deployment, and you build it. Last-mile agents and workflows. Configure and customize agents for each customer's actual workflow. Tune prompts, define tools, set guardrails, wire up the workflows that match how this specific institution operates. Generic agents lose; customer-specific agents win.
Launching with the customer. You run the go-live. Cutover plans, dry runs, rollback plans, sitting next to the customer on launch day. When something breaks at 7am, you diagnose, prototype, and ship. Sometimes within hours. Training the customer. Build the runbooks, train the end users, walk advisors and admins through the product, capture feedback in real time. A deployment is only successful when the customer can use it without you in the room. Feeding the platform. When you see the same customer-specific problem twice, you push it back to the platform team with the right framing so the third customer never has to wait.
We build AI digital workers that handle the real operational work universities are drowning in: enrollment, advising, advancement, student services.
In the employer’s words · Read in context
Open 5 monthsWe first saw this posting 172 days ago and it is still up. Roles open this long are often slow to fill or kept open to collect applications.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 172
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
Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
A full-stack builder who actually likes customers. The kind of engineer who can sit in a working session with a dean and walk out knowing exactly what to ship by Friday. - Strong across the stack. TypeScript, Python, React, Node, SQL. You debug a data pipeline, ship a frontend tweak, and design an API in the same day. - Fluent with data. Real institutional data is messy, partial, and inconsistent. You map it, clean it, reconcile it, and turn it into something the agents can use.
Complete your application on jobs.gem.com. The employer’s form will show what is required.
Already applied? Track this application
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.
San Francisco Bay Area
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.