Forward Deployed Engineer, Growth

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invention. Remove boilerplate like cookie/navigation/legal/EEO etc. The posting includes sections: "About" (company description), "Why Join Us", "Location", "About The Role", "What You'll Do", "Who You Are", "For candidates based in the United States, the expected base pay range...", "What We Offer". Also there is "WithCoverage: ..." at top. We need to map to headings: About the role (maybe "About The Role" heading). Responsibilities (maybe "What You'll Do"). Requirements/Qualifications/Skills (maybe "Who You Are" includes qualifications). Benefits (maybe "What We Offer"). Pay (the base pay range). Schedule (maybe location? but schedule not given; we have location: In-office, NYC HQ. That could be schedule? Actually schedule not mentioned. We should not create Schedule section unless posting actually states it. It does not. So omit Schedule. We also have "Location: In-office, NYC HQ." Could be part of a short paragraph maybe under a heading like "Location" but we only have allowed headings list; location not in list. Could fold into a short

maybe under About the role or separate? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exclusive; we could use other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should not add a Location heading. Could incorporate location into a paragraph under About the role or maybe under a generic

without heading. Probably best to include location as a paragraph after About the role heading. We must not repeat job title as heading. The job title is "customer-facing engineer". Not present as heading. We must not include Job ID/requisition numbers. We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We must preserve all substantive information. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

... description of role ...

Responsibilities

• ... items from What You'll Do ...

Requirements

• ... items from Who You Are ...

Maybe also Qualifications and Skills separate? But we can combine into Requirements. The instruction: prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Benefits, Pay. We need to include Benefits section from What We Offer. Pay section from base pay range. We need to ensure we don't include filler like "commensurate with experience". The posting includes "Competitive comp, meaningful equity, and excellent benefits." That's substantive. Also "We believe strongly in internal promotion and lay out a plan for everyone's career growth." That's part of Why Join Us maybe but we can incorporate into Benefits? Might be okay. We must not invent or summarize away detail. So we need to keep specifics: e.g., "Competitive compensation that includes equity", "Comprehensive benefit plans for medical, dental, vision, life, and disability", "Pre-tax accounts (FSA, HSAs, dependent care FSAs, commuter savings)", "Human Interest: 401(k) provider", "Time Off: Flexible time off, sick leave, family and medical leave, and major national holidays", "A curated in-office employee experience...", "Collaborative, transparent, and fun culture". Also "Competitive comp, meaningful equity, and excellent benefits." from Why Join Us. We need to preserve all substantive info; we can combine similar points but not lose detail. Let's extract sections: About the company (WithCoverage description) maybe not needed as a section? Could be part of About the role? But we have "About" section at top describing company. Could be included as a paragraph under About the role? Might be better to have a separate "About" heading but not in allowed list. However we could treat it as part of About the role? The instruction says use h3 for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings but says use h3 for section headings (e.g ...). Likely they expect those headings only. So we should not add a heading for company description; we can just include it as a paragraph before the About the role heading? But that would be orphan text without heading. Might be okay but maybe better to include it under About the role as context. The About the role section currently includes: "We’re looking for a customer-facing engineer to build AI-powered tools and workflows on WithCoverage’s Growth team and help prospective customers put AI to work in their businesses. You’ll partner closely with Product, which will define and scope much of the work, and own the engineering execution: writing code, connecting systems, testing behavior, and getting working tools into people’s hands. You should be comfortable taking a defined problem and independently making the technical decisions needed to build a practical, reliable solution. You’ll also be a technical resource our Growth and Sales teams can bring directly into prospect conversations. As an AI-native insurance brokerage, we can offer operators something valuable: access to an engineer who can answer their questions, demonstrate useful approaches, and help them apply AI to their own workflows. Hands-on building and prospect conversations are both substantial parts of the job. We’re looking for someone who enjoys writing software and can bring that same confidence and clarity to a room of nontechnical operators." We can keep that as paragraph under About the role. Responsibilities: from "What You'll Do": list items: - Own engineering execution. Partner with Product on defined projects and take responsibility for implementation. - Build AI-powered tools, applications, scripts, and integrations; make technical decisions; and own debugging, testing, deployment, and iteration. - Build AI workflows that work in practice. Connect LLMs, APIs, and business data to solve concrete workflow problems. Evaluate outputs against real examples, handle errors and edge cases, and improve reliability as people use what you build. - Help Sales secure the next call. Join prospect conversations and email threads to answer technical questions, work through specific problems, and demonstrate useful applications of AI. Help Sales turn that value into a concrete next step: a working session, a tailored demonstration, or a deeper conversation about WithCoverage. - Teach in plain language. Give nontechnical operators practical advice they can apply to their businesses. Walk them through tools, demonstrate approaches using relevant examples, and help them understand how to use AI effectively and check its work. - Be the technical expert on the call, and build after it. Understand enough of a prospect’s workflow to give sound technical guidance. When follow-up calls for a working example, build a prototype, script, or lightweight tool using relevant sample data and documents. - Keep the work useful and maintainable. Document what you build, reuse components where it makes sense, and communicate technical constraints and implementation tradeoffs to Product and Core Engineering. We can turn each sentence into

. Requirements/Qualifications/Skills: from "Who You Are": - 4+ years of technical experience, ideally including time in an AI or analytics practice at a consulting firm (QuantumBlack, BCG X, Bain Vector, Accenture, or similar) or in a forward-deployed / solutions engineering role - You've built AI-powered things that real people used. Prompt engineering, retrieval, agents, evals. It doesn't need to have been at a massive scale, but it needs to have been real. - You can explain how an LLM works to someone who has never written code, and they leave feeling capable rather than lectured to. This is the single most important qualification. - Genuinely strong client instincts. You can read a room, handle a skeptical executive, tell someone their idea won't work without losing them, and know when to stop talking. - You want to be on calls and in rooms. This is a people-facing job that happens to require an engineer, and roughly half your week looks like that. Also location: In-office, NYC HQ. Could be a paragraph after Requirements. Pay: "For candidates based in the United States, the expected base pay range for this position at the start of employment is $140,000 – $170,000/year + equity on top of it. Actual compensation will vary based on individual factors, including market location, relevant experience, and role scope. In addition to base salary, this role is eligible for variable compensation tied to performance or quota attainment, where applicable." We can put that in Pay section. Benefits: from "What We Offer:" and also "Why Join Us" includes "Competitive comp, meaningful equity, and excellent benefits." and "We believe strongly in internal promotion and lay out a plan for everyone's career growth." Also "Financial Rewards – We hire the best and invest in you. Competitive comp, meaningful equity, and excellent benefits." Actually that is under Why Join Us. We'll combine. Benefits list: - Competitive compensation that includes equity - Comprehensive benefit plans for medical, dental, vision, life, and disability - Pre-tax accounts (FSA, HSAs, dependent care FSAs, commuter savings) - Human Interest: 401(k) provider - Time Off: Flexible time off, sick leave, family and medical leave, and major national holidays - A curated in-office employee experience, designed to foster community, team connections, and innovation - Collaborative, transparent, and fun culture - Internal promotion and career growth plan (from Why Join Us) - Meaningful equity (already covered) - Excellent benefits (covered) We should avoid duplication. We'll produce HTML:

About the role

... paragraph ...

Responsibilities

• Own engineering execution. Partner with Product on defined projects and take responsibility for implementation.
• Build AI-powered tools, applications, scripts, and integrations; make technical decisions; and own debugging, testing, deployment, and iteration.
• Build AI workflows that work in practice. Connect LLMs, APIs, and business data to solve concrete workflow problems. Evaluate outputs against real examples, handle errors and edge cases, and improve reliability as people use what you build.
• Help Sales secure the next call. Join prospect conversations and email threads to answer technical questions, work through specific problems, and demonstrate useful applications of AI. Help Sales turn that value into a concrete next step: a working session, a tailored demonstration, or a deeper conversation about WithCoverage.
• Teach in plain language. Give nontechnical operators practical advice they can apply to their businesses. Walk them through tools, demonstrate approaches using relevant examples, and help them understand how to use AI effectively and check its work.
• Be the technical expert on the call, and build after it. Understand enough of a prospect’s workflow to give sound technical guidance. When follow-up calls for a working example, build a prototype, script, or lightweight tool using relevant sample data and documents.
• Keep the work useful and maintainable. Document what you build, reuse components where it makes sense, and communicate technical constraints and implementation tradeoffs to Product and Core Engineering.

Requirements

• 4+ years of technical experience, ideally including time in an AI or analytics practice at a consulting firm (QuantumBlack, BCG X, Bain Vector, Accenture, or similar) or in a forward