Time since we first saw it
Day 3
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.
Seattle, Washington, United States
Actively hiring, first seen by us 3 days agoEmployment type in the employer’s posting: FullTimeFrom the employer’s posting
Triage customer issues and fix them directly, escalating only with a clean repro
Run in-person onboarding at customer offices, including workflow design
Own customer-reported items from bug to merged PR, and small features to shipped
Write a daily and weekly customer digest covering issues, trends and verbatim quotes
Turn recurring questions into docs, how-tos and office hours
triage everything; fix some directly and escalate only what genuinely needs deeper core-engineering context — with a clean repro and context
Run onboarding in person at the customer's office — setup, workflow design with their team, first-value moments witnessed and secured.
They own customer-reported items end-to-end: bug to merged PR, small feature to shipped.
A daily and weekly customer digest for the whole team — issues, trends, feature friction, use-case patterns, verbatim quotes.
turn recurring questions into reusable teaching — docs, how-tos, office hours.
Actively hiringFirst seen by us 3 days ago, still listed, and not a repost of an earlier posting.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 3
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 recordAdd 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.
SageOx Today $15M seed led by Canaan, with A.Capital, Pioneer Square Labs, and Founders' Co-op. Founded by Ajit Banerjee (AWS EC2/EBS, XetHub → Hugging Face), Ryan Snodgrass (early Amazon, Kindle/AWS-scale cloud systems), and Milkana Brace (EVP Product at Remitly). Small on purpose. More about the team → Compensation
Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.
Already applied? Track this application
SageOx is a well-funded, early-stage startup building the hivemind for human-AI teams: shared memory and collaboration tools that keep people and AI coworkers genuinely aligned and productive as one team. We're hiring our first Forward Deployed Engineer to be our builder at the customer boundary.
Be SageOx's builder at the customer boundary — the first line of partnership for every team we serve. Embedded where customers live (their Slack, their office), this engineer turns friction into shipped product: educating teams, unlocking value, and building the fixes and features that customer experience demands. Customers reach daily-active use because this person exists — and the roadmap stays directly aligned to customer needs because of the feedback they synthesize.
First line of engagement: Live where customers live; catch issues as they arrive; triage everything; fix some directly and escalate only what genuinely needs deeper core-engineering context — with a clean repro and context. Today the engagement surface is shared Slack channels — right for now, while we're under ~30 teams and know every one by name — but over time it may shift. This person helps identify the best way to stay engaged and meets customers where they are.
Onboard new customers onsite: Run onboarding in person at the customer's office — setup, workflow design with their team, first-value moments witnessed and secured.
Build on the core product. This is not a support role with a code editor nearby — this person IS a builder. They own customer-reported items end-to-end: bug to merged PR, small feature to shipped. The customer-reported queue is their backlog into the core codebase, and their commits are how customer pain becomes product, fast.
Create value, not just fixes: Design solutions and workflows with customer teams, educate users into power users, and turn recurring questions into reusable teaching — docs, how-tos, office hours. The job is measured in value unlocked, not tickets closed.
Own the signal loop: A daily and weekly customer digest for the whole team — issues, trends, feature friction, use-case patterns, verbatim quotes. This is how the team stays connected to customer truth without carrying the response traffic; it's a first-class deliverable, not a side note.
Shorten time-to-value every week: Each onboarding and each recurring issue should produce a fix, a doc, or a product suggestion that makes the next customer faster.
Profile in one line: An engineer who chooses people — a builder with real technical chops who discovered they're happiest at the customer boundary: sharing, educating, helping, unlocking value.
Experience: Software engineer who migrated toward customers, or a solutions/support/sales engineer at a dev-tool or infra startup who ships fixes themselves. Early-startup exposure strongly preferred over big-co support orgs.
Technical bar: Debug an integration end-to-end and ship small features — not only bug fixes — unsupervised. Fast, pragmatic; moves independently but knows when to flag, ask for help, or request review.
Cultural fit: Energized (not drained) by customer pings and onsite visits; patient teacher; writes clearly — the digest and the onboarding materials are writing deliverables, and good ones compound: every improvement lets more teams self-onboard or self-unblock, easing this person's own load over time; embraces transparency; focused on making the team win.
AI-native: Comfortable with agent workflows and AI tooling; they'll be teaching customers to work with AI coworkers, so they must work that way themselves.
Logistics: Onsite onboarding makes travel a real constraint — genuinely travel-willing.
Same as every role here. In person, five days a week, in Seattle. FDE travel to customer sites happens occasionally — think a few days a quarter, not permanent road-warrior life.
One narrow exception: Bay Area-based candidates we can get to Seattle at least two weeks a month, through end of 2026.
No traditional interviews. We'll clear an initial assessment and invite you to a work trial: 3–5 days in Seattle, working on something real alongside the team, the way the team actually works. Most of what matters shows up there faster than any interview loop could reveal.
Ajit wrote up why we hire this way: Read the post →
$15M seed led by Canaan, with A.Capital, Pioneer Square Labs, and Founders' Co-op. Founded by Ajit Banerjee (AWS EC2/EBS, XetHub → Hugging Face), Ryan Snodgrass (early Amazon, Kindle/AWS-scale cloud systems), and Milkana Brace (EVP Product at Remitly). Small on purpose. More about the team →
Competitive salary and meaningful equity. We'll talk specifics once we know it's a real mutual fit.
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.
Seattle, Washington, United States
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.