Back to jobs

Forward Deployed Engineer

Pay
Pay not listed
Work setting
On-site — work setting source
Work setup in the employer’s posting: IN_OFFICE
From the employer’s posting
Employment
Full-time — employment source
Employment type in the employer’s posting: FULL_TIME
From the employer’s posting

What you’ll work on

Full 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.

From the employer’s posting
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.

About Risely-Ai

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

Apply at Risely-Ai

Posting record

Report an error

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.

Status in our records
Live
First seen by us
Jun 2, 2026172 days ago
Recorded sightings
64
Last seen by us
Nov 22, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

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.

Risely-Ai is hiring

1 open job

  • No new data jobs since June
Hiring record

See how this role fits your experience

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.

  • Python
  • SQL
  • TypeScript
  • React
Where the posting names them
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.

Your next step

Complete your application on jobs.gem.com. The employer’s form will show what is required.

Already applied? Track this application

Job description

View original posting ↗

Forward Deployed Engineer
Location: Downtown San Francisco, in-person 5 days a week, with travel to customers
Comp: $120-180K total cash (incl. variable) plus founding-level equity

Risely is the AI workforce for higher education. We're growing rapidly amidst massive customer demnad.

We're hiring a Forward Deployed Engineer to own customer deployments end to end.

The role


You own the customer from the moment a contract is signed to the day the product is working inside their institution. Every layer of the stack that has to come together for that to happen is yours.

Every university is different. Their systems are messy, their data is partial, their workflows live in people's heads. The job is to walk into that environment, figure out what is actually true, and ship working software against it. Sometimes that means a Salesforce integration. Sometimes it means a custom React dashboard for a dean. Sometimes it means rewriting an agent's workflow at 11pm because tomorrow's launch needs it. You do all of it.

The pace is hours and days. A deployment that takes a quarter elsewhere takes us weeks here, and you are the reason that's true.

What you'll own

  • Customer deployments end to end. You own the kickoff, the discovery, the technical design, the build, the launch, and the first weeks of usage. A deployment is yours from week one to working product.
  • 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.
  • 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.

Who we're looking for

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.
  • A shipper. A working version this week beats a perfect version next month. You move at the pace of the customer conversation and close loops fast.
  • Customer-fluent. You translate institutional pain into code, and code back into something the customer trusts.
  • AI-native. You orchestrate Claude Code agents alongside your own work. You have a real point of view on where agents add leverage and where humans still have to drive.
1-5 years of building full-stack production systems. You're joining the founding team and the upside reflects that.

What it's like to work here

Risely is a startup in the truest sense. We are all in. The pace is intense and the work is demanding, and the impact is real.
  • In-person commitment. We're in the office together. Building at this stage takes full presence and full focus, and that often means evenings and the occasional Saturday.
  • Speed and impact. Your work ships fast and reaches students and staff in days, not quarters.
  • Mission clarity. Every line of code, every late night, every customer trip ties back to one purpose: helping students stay enrolled and helping colleges survive a generational shift.
  • Ownership from week one. You'll make critical decisions and drive real outcomes from the start.
  • Deep, meaningful work. You'll wrestle with data complexity, privacy regulations, and decades-old legacy systems. The problems are hard, and solving them changes how universities run.
If this excites you, join us at the ground floor. The work will stretch you and demand your best. It will also be the most meaningful work of your career.

About Risely


Colleges are in trouble. One in three students drops out today, even after schools spend millions to recruit them. Overburdened staff comb through fragmented data by hand and miss the warning signs until it's too late.

We founded Risely to back the mission of higher education through the biggest systemic and technological shift the industry has ever faced. We build AI digital workers that handle the real operational work universities are drowning in: enrollment, advising, advancement, student services. We deploy them inside the systems institutions already use, and we make them work.

We're live and growing fast. Our customers include R1 research universities and various private colleges around the US. We're a small team, YC-backed, well-funded, and building like the future of higher ed depends on us.

How to apply

Apply here and if you're really interested, email shahryar@risely.ai with a paragraph on why this role and a link to something you've built.

Demand for Forward Deployed Engineer roles

New Forward Deployed Engineer postings at the employers we follow are up 225% over the last 6 weeks compared with the 6 before.

Weekly new Forward Deployed Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 51, the most 267, and the latest week had 217.
August 17Last week

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.

About the role

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.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

San Francisco Bay Area

Working pattern and location restrictions need checking in the full posting.

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.