> Markdown version of [/jobs/ext/3075643-forward-deployed-engineer](https://www.wearedevelopers.com/jobs/ext/3075643-forward-deployed-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Forward Deployed Engineer - **Company:** README LLC - **Location:** United States (Remote available) - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Cascading Style Sheets (CSS), Continuous Integration, Software Debugging, Openapi, Git - **Published:** September 25, 2026 - **Apply:** https://startup.jobs/forward-deployed-engineer-readme-10170628 ## About the Role * Passionate about working with others; you'd be collaborating with lots of new customers, and our Sales, Product, Support and Enterprise Engineering teams! * An outstanding communicator, very organized, and able to manage multiple projects at once. * Technical enough to read an OpenAPI spec, poke at a customer's HTML/CSS/JS, understand SSO and auth flows, and use Git and a CLI comfortably. You don't need to be a software engineer, but you should be able to hold your own with one. * Someone who uses AI as a working tool. You've built prompts, workflows, or small automations that changed how you actually get work done, and you're eager to keep doing that. * A problem solver who'd rather figure out the answer than escalate it. You enjoy the puzzle of making a product bend to a customer's real-world constraints. ## Description * Own a book of enterprise accounts end to end. Onboarding, adoption, renewal assistance, and expansion. Be the primary technical and strategic contact for each. * Be on customer calls regularly, including: implementation kickoffs, working sessions, QBRs, and escalations. This is a customer-facing role, not a ticket-queue role. * Act as the product SME for your accounts. Know ReadMe deeply enough to answer product questions in real time, and debug alongside customers when something isn't working. * Get hands-on with the technical implementation. Review OAS files, help wire up CI/CD syncing via the ReadMe CLI or API, troubleshoot custom JS/CSS and auth setups, and prototype solutions before handing off to Engineering. * Build AI into how you work. Use AI tools to draft implementation plans, analyze account health across your book, triage and summarize customer requests, prototype scripts, and automate the repetitive parts of the job so you spend more time solving real problems. * Identify expansion and growth opportunities across your book and partner with Sales to close them. * Advocate for customers internally, surface health risks early, and feed structured product and bug feedback to Product and Engineering., * Learn and collaborate from people around the ReadMe org about our product and what it can do for customers. * Start to develop relationships with your book of enterprise customers * Sit in on customer calls with the team and start running your own kickoffs with new customers * Complete a hands-on ReadMe build i.e., set up a hub from an OAS file, configure SSO, ship a custom page, so you've done what customers do. Within three months, you'll… * Be the first line of technical resolution for your accounts. You answer and debug most questions yourself. * Have built at least one AI-assisted workflow that saves you or the team meaningful time each week. Within six months, you'll... * Be performing to the KPIs of the role - time to implementation, NPS scores, NRR, etc. * Consult on how we can position our roadmap to maximize the enterprise experience in the long term. * Identify expansion conversations in your book to forward to Sales ## Related Videos - [Lessons learned from observing a billion API requests](https://www.wearedevelopers.com/videos/1574-lessons-learned-from-observing-a-billion-api-requests) - [For the REST of us: API First and Conway’s Law](https://www.wearedevelopers.com/videos/1932-for-the-rest-of-us-api-first-and-conway-s-law) - [Using AI Without Losing Your Skills](https://www.wearedevelopers.com/videos/2045-using-ai-without-losing-your-skills) - [How a Small Team Shrank a Microsoft Monorepo by 94%](https://www.wearedevelopers.com/videos/1236-how-a-small-team-shrank-a-microsoft-monorepo-by-94) - [Contract-First Frontend: Scaling Reliable UIs with OpenAPI and AI](https://www.wearedevelopers.com/videos/1995-contract-first-frontend-scaling-reliable-uis-with-openapi-and-ai) - [Throwing off the burdens of scale in engineering](https://www.wearedevelopers.com/videos/608-throwing-off-the-burdens-of-scale-in-engineering) ## Related Articles - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Dev Digest 132 - Binging WADFlix?](https://www.wearedevelopers.com/magazine/473-dev-digest-132-binging-wadflix) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [WeAreDevelopers Dev Digest Issue 116 - The new search wars…](https://www.wearedevelopers.com/magazine/445-wearedevelopers-dev-digest-issue-116-the-new-search-wars) - [Dev Digest 131 - AI'm not sure about OSS](https://www.wearedevelopers.com/magazine/472-dev-digest-131-ai-m-not-sure-about-oss)