Forward Deployed Engineer
or drop it." So location is minor metadata; we can include a short p. We need to preserve all substantive information. So we need to extract sections: About the role (intro paragraph), Responsibilities (list of duties), Requirements/Qualifications/Skills (maybe combine). Benefits (list). Pay and Schedule: not mentioned, so omit those sections. We must not create sections with filler. So we will have sections: About the role, Responsibilities, Requirements, Skills, Benefits. Possibly Qualifications separate? The posting includes "What you’ll do here" (responsibilities), "You’ll love this job if you are…" (skills/qualities), "How you’ll grow within one month..." etc. Also "What we do" (about the company). Could treat "About the role" as the intro paragraph describing role. Could also have "About the company" but not required. We'll follow headings: About the role, Responsibilities, Requirements, Skills, Benefits. We need to use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. Not include navigation etc.
Let's craft:
Locations: San Francisco (Hybrid), New York (Hybrid), Columbus (Hybrid), or Remote (US)
Then About the role
with paragraph summarizing role: The Forward Deployed Engineer ... etc.
Then Responsibilities
with list items from "What you’ll do here" and other duty bullets.
Then Requirements
maybe combine "You’ll love this job if you are…" and technical requirements.
Then Skills
maybe list specific technical skills: OpenAPI spec, HTML/CSS/JS, SSO/auth, Git, CLI, AI tools.
Then Benefits
with list from benefits section.
Make sure to preserve all substantive information: include details like unlimited PTO with three-week minimum, fully covered medical dental vision, One Medical membership, wellness stipend for therapy up to $350 per month for up to 6 months, wellness stipend up to $150 per month, one-to-one donation matching up to $1,000 per year, twelve weeks paid parental leave, work from home office stipend $500, offsite retreats, etc.
Also include mention of investors Accel, culture, etc maybe in About the role.
Let's extract responsibilities bullet points:
- 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.
- 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.
Also earlier: "You'll be on calls with enterprise engineering and docs teams every week, you'll own a book of accounts end to end, and you'll be the person who figures out how to make ReadMe work for whatever they're trying to do, not the person who files the ticket and waits." Already covered.
Now requirements/qualities:
From "You’ll love this job if you are…":
- Passionate about working with others; collaborating with lots of new customers, and our Sales, Product, Support and Enterprise Engineering teams.
- 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.
Also growth expectations: within one month, three months, six months could be considered requirements? Might be under "How you’ll grow". Could be part of Responsibilities or a separate section "Growth milestones". But we only have set headings; we could include under Responsibilities or maybe a separate section "Expectations". But we must only include sections when posting has real specific content. The growth milestones are specific; we could create a section "Expectations" but not in allowed headings. Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put growth milestones under Requirements or Skills? Probably under Requirements (what is expected). We'll include them as part of Requirements.
Now Skills: list technical skills: OpenAPI spec, HTML/CSS/JS, SSO/auth flows, Git, CLI, AI tools (prompt engineering, workflow automation), maybe also CI/CD syncing via ReadMe CLI/API, custom JS/CSS, prototyping.
Now Benefits: list as above.
Now we need to ensure we don't include boilerplate like EEO etc. Remove that.
Now produce HTML.
Let's craft:
Locations: San Francisco (Hybrid), New York (Hybrid), Columbus (Hybrid), or Remote (US)
About the role
The Forward Deployed Engineer is a perfect role for someone who is technical enough to sit in a customer's codebase and docs, curious enough to become the deepest product expert in the room, and wants to own the customer relationship at a fast‑moving startup. You'll be on calls with enterprise engineering and docs teams every week, own a book of accounts end to end, and be the person who figures out how to make ReadMe work for whatever they're trying to do, not the person who files the ticket and waits. At ReadMe the Sales team finds companies that we can solve problems for, and you take over from there. Your role is to oversee a swift and effective implementation, partner with the customer to have a successful first year, identify opportunities for growth and optimization, and make sure the right resources get tapped in to support whatever the customer needs to be successful with ReadMe. You'll solve most technical questions yourself, and know when and how to pull in Engineering or Solutions Architects for the rest. ReadMe helps more than 5,000 leading startups and tech companies build beautiful, personalized, and interactive developer hubs. If you’ve ever visited the developer docs for Amazon, Samsara, or Nvidia, you’ve used ReadMe! We’re providing tools for teams to build a better developer experience and make their products and APIs easier to use. We’ve got great support from our investors at Accel who led our Series A, and our interview process reflects the open, caring, and whimsical culture we want to maintain as we scale.
Responsibilities
- Own a book of enterprise accounts end to end – onboarding, adoption, renewal assistance, and expansion.
- Be the primary technical and strategic contact for each account.
- Be on customer calls regularly, including implementation kickoffs, working sessions, QBRs, and escalations.
- 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, triage and summarize customer requests, prototype scripts, and automate repetitive parts of the job.
- 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.
Requirements
- Passionate about working with others; able to collaborate with lots of new customers and cross‑functional teams (Sales, Product, Support, Enterprise Engineering).
- 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 should be able to hold your own with one).
- Uses AI as a working tool: has built prompts, workflows, or small automations that changed how work gets done and is eager to keep doing that.
- A problem solver who prefers to figure out the answer rather than escalate it; enjoys the puzzle of making a product bend to a customer's real‑world constraints.
- Within the first month: learn and collaborate across the org, start developing relationships with enterprise accounts, sit in on customer calls and run your own kickoffs, complete a hands‑on ReadMe build (set up a hub from an OAS file, configure SSO, ship a custom page).
- Within three months: be the first line of technical resolution for your accounts, answer and debug most questions yourself, and have built at least one AI‑assisted workflow that saves you or the team meaningful time each week.
- Within six months: perform to the role’s KPIs (time to implementation, NPS scores, NRR, etc.), consult on positioning the roadmap to maximize the enterprise experience, and identify expansion conversations to forward to Sales.
Skills
- OpenAPI Specification reading and editing.
- HTML, CSS, JavaScript troubleshooting and customization.
- SSO and authentication flow understanding.
- Git and command‑line interface proficiency.
- Experience with ReadMe CLI or API for CI/CD syncing.
- Ability to prototype solutions and hand them off to Engineering.
- Prompt engineering and AI‑assisted workflow creation.
- Strong communication and organizational skills.
Benefits
- Unlimited PTO with a three‑week minimum.
- Fully covered medical, dental, and vision insurance for you and your dependents.
- One Medical
for prose. We must not repeat job title as heading. Not include navigation etc. Let's craft:
Locations: San Francisco (Hybrid), New York (Hybrid), Columbus (Hybrid), or Remote (US)
ThenAbout the role
with paragraph summarizing role: The Forward Deployed Engineer ... etc. ThenResponsibilities
with- list items from "What you’ll do here" and other duty bullets.
Then
- Own a book of enterprise accounts end to end – onboarding, adoption, renewal assistance, and expansion.
- Be the primary technical and strategic contact for each account.
- Be on customer calls regularly, including implementation kickoffs, working sessions, QBRs, and escalations.
- 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, triage and summarize customer requests, prototype scripts, and automate repetitive parts of the job.
- 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.
- Passionate about working with others; able to collaborate with lots of new customers and cross‑functional teams (Sales, Product, Support, Enterprise Engineering).
- 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 should be able to hold your own with one).
- Uses AI as a working tool: has built prompts, workflows, or small automations that changed how work gets done and is eager to keep doing that.
- A problem solver who prefers to figure out the answer rather than escalate it; enjoys the puzzle of making a product bend to a customer's real‑world constraints.
- Within the first month: learn and collaborate across the org, start developing relationships with enterprise accounts, sit in on customer calls and run your own kickoffs, complete a hands‑on ReadMe build (set up a hub from an OAS file, configure SSO, ship a custom page).
- Within three months: be the first line of technical resolution for your accounts, answer and debug most questions yourself, and have built at least one AI‑assisted workflow that saves you or the team meaningful time each week.
- Within six months: perform to the role’s KPIs (time to implementation, NPS scores, NRR, etc.), consult on positioning the roadmap to maximize the enterprise experience, and identify expansion conversations to forward to Sales.
- OpenAPI Specification reading and editing.
- HTML, CSS, JavaScript troubleshooting and customization.
- SSO and authentication flow understanding.
- Git and command‑line interface proficiency.
- Experience with ReadMe CLI or API for CI/CD syncing.
- Ability to prototype solutions and hand them off to Engineering.
- Prompt engineering and AI‑assisted workflow creation.
- Strong communication and organizational skills.
- Unlimited PTO with a three‑week minimum.
- Fully covered medical, dental, and vision insurance for you and your dependents.
- One Medical
Requirements
maybe combine "You’ll love this job if you are…" and technical requirements. ThenSkills
maybe list specific technical skills: OpenAPI spec, HTML/CSS/JS, SSO/auth, Git, CLI, AI tools. ThenBenefits
with list from benefits section. Make sure to preserve all substantive information: include details like unlimited PTO with three-week minimum, fully covered medical dental vision, One Medical membership, wellness stipend for therapy up to $350 per month for up to 6 months, wellness stipend up to $150 per month, one-to-one donation matching up to $1,000 per year, twelve weeks paid parental leave, work from home office stipend $500, offsite retreats, etc. Also include mention of investors Accel, culture, etc maybe in About the role. Let's extract responsibilities bullet points: - 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. - 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. Also earlier: "You'll be on calls with enterprise engineering and docs teams every week, you'll own a book of accounts end to end, and you'll be the person who figures out how to make ReadMe work for whatever they're trying to do, not the person who files the ticket and waits." Already covered. Now requirements/qualities: From "You’ll love this job if you are…": - Passionate about working with others; collaborating with lots of new customers, and our Sales, Product, Support and Enterprise Engineering teams. - 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. Also growth expectations: within one month, three months, six months could be considered requirements? Might be under "How you’ll grow". Could be part of Responsibilities or a separate section "Growth milestones". But we only have set headings; we could include under Responsibilities or maybe a separate section "Expectations". But we must only include sections when posting has real specific content. The growth milestones are specific; we could create a section "Expectations" but not in allowed headings. Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put growth milestones under Requirements or Skills? Probably under Requirements (what is expected). We'll include them as part of Requirements. Now Skills: list technical skills: OpenAPI spec, HTML/CSS/JS, SSO/auth flows, Git, CLI, AI tools (prompt engineering, workflow automation), maybe also CI/CD syncing via ReadMe CLI/API, custom JS/CSS, prototyping. Now Benefits: list as above. Now we need to ensure we don't include boilerplate like EEO etc. Remove that. Now produce HTML. Let's craft:Locations: San Francisco (Hybrid), New York (Hybrid), Columbus (Hybrid), or Remote (US)
About the role
The Forward Deployed Engineer is a perfect role for someone who is technical enough to sit in a customer's codebase and docs, curious enough to become the deepest product expert in the room, and wants to own the customer relationship at a fast‑moving startup. You'll be on calls with enterprise engineering and docs teams every week, own a book of accounts end to end, and be the person who figures out how to make ReadMe work for whatever they're trying to do, not the person who files the ticket and waits. At ReadMe the Sales team finds companies that we can solve problems for, and you take over from there. Your role is to oversee a swift and effective implementation, partner with the customer to have a successful first year, identify opportunities for growth and optimization, and make sure the right resources get tapped in to support whatever the customer needs to be successful with ReadMe. You'll solve most technical questions yourself, and know when and how to pull in Engineering or Solutions Architects for the rest. ReadMe helps more than 5,000 leading startups and tech companies build beautiful, personalized, and interactive developer hubs. If you’ve ever visited the developer docs for Amazon, Samsara, or Nvidia, you’ve used ReadMe! We’re providing tools for teams to build a better developer experience and make their products and APIs easier to use. We’ve got great support from our investors at Accel who led our Series A, and our interview process reflects the open, caring, and whimsical culture we want to maintain as we scale.