Forward Deployed Engineer
or drop it. So location can be a short p. Now sections: About the role: The first paragraph after location: "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, 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. 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." That's about the role. Then "🦉 What we do" paragraph: "We're a small team of humans (and one owl) working together to do big things, and that’s where you come in. In this role you’ll have a transformational impact on ReadMe across both the trajectory of the business and our thriving culture. 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 love what we do because it’s so much more than just documentation. 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." That could be part of About the role or separate "About the company". But we only have headings list; we could put this under About the role as well, or maybe "About the role" includes that. We'll keep it under About the role. Then "✅ What you’ll do here" list: bullet points. We need to map to Responsibilities. So Responsibilities section with
- items.
List items:
- 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.
That's responsibilities.
Then "💙 You’ll love this job if you are…" list of traits: could be Requirements or Qualifications or Skills. Let's map: "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."
These are qualifications/skills. Could be Requirements (must-have) and Skills (nice-to-have). We'll put them under Requirements (or Qualifications). Since we have both headings, we need to decide. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Skills into one section? But we have separate headings allowed. We could put Requirements for must-have and Skills for nice-to-have. However the text mixes both. Could split: Requirements: technical enough to read OAS, understand SSO/auth, use Git/CLI, collaborate, communicator, organized, manage multiple projects, use AI as tool, problem solver. Skills: maybe "Passionate about working with others", "outstanding communicator", etc. But it's overlapping.
Given instruction to prefer few substantive sections, we could just have one section "Requirements" covering all. Or we could have "Qualifications" and "Skills" but risk thin sections. Let's combine into "Requirements". Then we can omit Qualifications and Skills headings.
Next: "🌱 How you’ll grow within one month" list: could be under "Growth" but not in allowed headings. Could be part of Responsibilities? Not exactly. Could be under "About the role"? Might be better to include as a separate section "Growth" but not allowed. Since we must only use allowed headings, we could incorporate into Responsibilities or About the role? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we cannot create a heading not in list. So we need to fit that content somewhere else. Perhaps under "About the role" as a paragraph about growth expectations. Or under "Responsibilities" as expectations? Might be okay.
Similarly "🪴 Within three months, you’ll…" and "🌳 Within six months, you’ll..." could be placed under same paragraph.
Then "🛣️ What’s the hiring process like?" This is about process; we should remove application instructions per instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The hiring process description is basically application instructions; we should remove it. So we omit that.
Then "✨ Our Benefits Include…" list: we need Benefits section with those items.
Benefits list:
- Unlimited PTO with a three-week minimum.
- Fully covered medical, dental, and vision insurance for you, and your dependents.
- A One Medical membership.
- A wellness stipend for therapy of up to $350 per month for up to 6 months.
- A wellness stipend of up to $150 per month.
- One-to-one donation matching of up to $1,000 per year.
- Twelve weeks of paid parental leave after the birth or adoption of a child.
- Work from home office stipend of $500.
- Offsite retreats to get together with coworkers and plan for the quarter ahead.
Also mention "Take a look at our handbook for more information on our benefits!" That's a reference; could be included as a sentence.
Pay and Schedule: Not mentioned. So we should NOT create Pay or Schedule sections because no specific content. So omit those.
Now we need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Benefits. Possibly also include a short p for location metadata.
We must not repeat job title as heading. So no h3 for Forward Deployed Engineer.
We'll structure:
Locations: San Francisco (Hybrid), New York (Hybrid), Columbus (Hybrid), or Remote (US)
About the role
... (combined description)
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...
- . Ensure we keep all details. Let's list them: - 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