DirectJobHub
Jobs · Engineering · New York

Forward Deployed Engineer

Anthropic · New York, NY · 3 wk ago
HybridEngineering$280k–$320k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications, Skills), Benefits, Pay, Schedule etc only if present. We need to extract content from posting. First, remove boilerplate: About Anthropic mission etc. The "About The Role" heading is present; we need to use

for section headings. The page already shows job title; we should not repeat job title as heading. So we start with

About the Role

then paragraph(s) containing the prose from that section. The "About The Role" section includes paragraphs: "As a member of the Applied AI team at Anthropic, you will be a Forward Deployed Engineer (FDE) who embeds directly with our most strategic customers to drive transformational AI adoption. You will collaborate closely with customer teams to ship advanced AI applications that solve real world business problems. Our FDEs engage with customers to accelerate the adoption of existing products and create new applications built on our models. Working closely with our Post-Sales, Product, and Engineering teams, you'll combine engineering expertise, an understanding of frontier AI applications, and customer-facing skills to understand customer workflows and develop innovative solutions that address complex business challenges while maintaining our high standards for safety and reliability. You will sit at the frontier of enterprise AI deployments and serve as one of our founding FDEs who helps to shape our forward-deployed motion. We expect our FDEs to operate autonomously, thrive under ambiguity, and represent Anthropic at the highest level in customer environments. This is a significant responsibility: you’ll play a key role in championing our mission in the enterprise." We can combine into one

. Next section: Responsibilities. The posting has a "Responsibilities" heading then bullet list (some lines). We need to extract each bullet as

  • . The bullet lines start with dash or bullet. Let's list them: - Work within customer systems to build production applications with Claude models, ensuring that these products meet customer requirements. - Deliver technical artifacts for customers like MCP servers, sub-agents, and agent skills that will be used in production workflows. - Provide white glove deployment support for Anthropic products in enterprise environments. - Identify and codify repeatable deployment patterns and contribute insights back to our Product and Engineering teams. - Maintain strong knowledge of the latest developments in LLM capabilities, implementation patterns, and AI product development stacks. - Build long term relationships with customers and proactively identify new opportunities for AI deployment throughout the lifecycle of an engagement. - Potential Travel (based on location) to customer sites to build in person with customers. - Estimated 25% - Be a champion for Anthropic’s mission in the field. Note there is a line "Potential Travel (based on location) to customer sites to build in person with customers. - Estimated 25%" It seems two parts: maybe it's one bullet with travel and estimate. We'll keep as one bullet. Now after responsibilities, there is "You May Be a Good Fit If You Have" which is qualifications/requirements. We need a section for Requirements or Qualifications. The instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose "Requirements" or "Qualifications". Since there is a list of qualifications, we can put under "Requirements". We'll need to extract the bullet list after that heading. The list after "You May Be a Good Fit If You Have" includes: - 4+ years of experience in a technical, customer facing role such as Forward Deployed Engineer, or as a Software Engineer with consulting experience. Former technical founders are also encouraged to apply. - Production experience with LLMs including advanced prompt engineering, agent development, evaluation frameworks, and deployment at scale. - Strong programming skills with proficiency in Python (and ideally in one or more additional languages like Typescript, Java, etc) and experience shipping production applications - High agency with an ability to navigate ambiguity present in complex organizations. - High cooperation mindset for cross-organizational collaboration, balancing competing priorities with integrity. - Passion for advancing safe, beneficial AI systems through creative technical applications. - Strong communication skills to conduct discovery with customers and to convey technical concepts to diverse stakeholders while maintaining a low ego and collaborative approach. - A background in financial services, healthcare/life sciences, or another enterprise vertical is a plus. - Experience with enterprise IT systems and/or AI deployment patterns is a plus. - Experience working as an FDE or in a professional services context is a plus. Also there is a paragraph about compensation: "The annual compensation range for this role is listed below. For sales roles, the range provided is the role’s On Target Earnings ("OTE") range, meaning that the range includes both the sales commissions/sales bonuses target and annual base salary for the role. Annual Salary $280,000—$320,000 USD" We need a Pay section if posting actually states them. Yes, they state annual salary range. So we create

    Pay

    and a

    with that text. Also there is "Logistics" section with items: Minimum education, Required field of study, Minimum years of experience, Location-based hybrid policy, Visa sponsorship, etc. These could be considered Requirements or maybe we could create a "Requirements" section that includes those plus the qualifications list. However we already have a qualifications list; we could incorporate logistics items into Requirements as well. But we need to avoid duplication and keep substantive info. We could create a section "Requirements" that includes both the bullet list of qualifications and the logistics items (maybe as sub-bullets). However the instruction: "Prefer a few substantive sections over many thin ones." So we could have one Requirements section that includes all requirements (education, experience, etc). The qualifications list is more like "You May Be a Good Fit If You Have". That's also requirements but maybe "Preferred Qualifications". But we can combine. We need to decide headings: About the role, Responsibilities, Requirements, Pay. Possibly also Benefits? The posting mentions benefits later: "We offer competitive compensation and benefits, optional equity donation matching, generous vacation and parental leave, flexible working hours, and a lovely office space in which to collaborate with colleagues." That's a benefits statement. So we should include a Benefits section. Also there is a mention of "Guidance on Candidates' AI Usage:" etc but that's boilerplate maybe not needed. We also have "How We're Different" etc but that's more about company; could be omitted as boilerplate? It's not about the role; but it's substantive about company culture. However instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "How We're Different" and "Come work with us!" might be considered promotional but not boilerplate; but we might keep if it's substantive? The instruction says prefer few substantive sections; we could include a Benefits section that includes that paragraph. The "How We're Different" and "Come work with us!" could be considered part of Benefits or maybe we could ignore as not directly about role. Safer to include only Benefits from that paragraph. Thus sections: - About the Role - Responsibilities - Requirements (or Qualifications) - Benefits - Pay We might also include Schedule? The posting mentions "Location-based hybrid policy: Currently, we expect all staff to be in one of our offices at least 25% of the time. However, some roles may require more time in our offices." That's schedule/hybrid expectation. Could be a Schedule section. But we could incorporate into Requirements or Benefits. Since they ask to create Schedule section only if posting actually states them. It does state location-based hybrid policy. So we could add a Schedule section. But we need to avoid many thin sections. However we already have 5 sections; adding Schedule makes 6. Might be okay but we could combine schedule into Benefits or Requirements. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine schedule into Benefits (as it's about working arrangement). However Benefits usually about compensation/benefits; schedule is about work arrangement. Could be separate but we can decide to put schedule under Benefits as a bullet about flexible working hours and office expectation. The benefits paragraph already mentions flexible working hours. So we can incorporate the hybrid policy into Benefits. Thus Benefits section will include: "We offer competitive compensation and benefits, optional equity donation matching, generous vacation and parental leave, flexible working hours, and a lovely office space in which to collaborate with colleagues." plus the hybrid policy: "Location-based hybrid policy: Currently, we expect all staff to be in one of our offices at least 25% of the time. However, some roles may require more time in our offices." We'll combine into a paragraph or maybe bullet list? Since it's prose, we can put in

    . Now Requirements section: we need to include the bullet list from "You May Be a Good Fit If You Have" plus logistics items: Minimum education, Required field of study, Minimum years of experience, Visa sponsorship. Also maybe "Minimum years of experience: Years of experience required will correlate with the internal job level requirements for the position" which is vague; we could omit as filler? It says "Years of experience required will correlate with the internal job level requirements for the position." That's not specific; maybe we should omit as filler (like "not specified"). The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). This is vague but not exactly placeholder; still it's not specific. Might be better to omit. We'll include: - Minimum education: Bachelor’s degree or an equivalent combination of education, training, and/or experience - Required field of study: A field relevant to the role as demonstrated through coursework, training, or professional experience - Visa sponsorship: We do sponsor visas! However, we aren't able to successfully sponsor visas for every role and every candidate. But if we make you an offer, we will make every reasonable effort to get you a visa, and we retain an immigration lawyer to help with this. We could also include "Minimum years of experience: Years of experience required will correlate with the internal job level requirements for the position." Might be considered filler; better to omit. Now we need to ensure we preserve ALL substantive information; do not invent or summarize away detail. So we must keep all specifics from the qualifications list and logistics. Now we need to format HTML. We'll output:

    About the Role

    ...

    Responsibilities

    • ...
      • ...

    Requirements

    • ...
      • ...

    Benefits

    ...

    Pay

    ...

    Make sure no extra whitespace? It's fine. Now craft the paragraphs. About the Role paragraph: combine the sentences. Let's write:

    As a member of the Applied AI team at Anthropic, you will be a Forward Deployed Engineer (FDE) who embeds directly with our most strategic customers to drive transformational AI adoption. You will collaborate closely with customer teams to ship advanced AI applications that solve real world business problems. Our FDEs engage with customers to accelerate the adoption of existing products and create new applications built on our models. Working closely with our Post-Sales, Product, and Engineering teams, you'll combine engineering expertise, an understanding of frontier AI applications, and customer-facing skills to understand customer workflows and develop innovative solutions that address complex business challenges while maintaining our high standards for safety and reliability. You will sit at the frontier of enterprise AI deployments and serve as one of our founding FDEs who helps to shape our forward-deployed motion. We expect our FDEs to operate autonomously, thrive under ambiguity, and represent Anthropic at the highest level in customer environments. This is a significant responsibility: you’ll play a key role in championing our mission in the enterprise.

    Now Responsibilities list items: - Work within customer systems to build production applications with Claude models, ensuring that these

    • Similar jobs