DirectJobHub
Jobs · Engineering · New York

Senior Forward Deployed Engineer, Enterprise AI

Handshake · New York, NY · 2 wk ago
On-siteEngineering$220k–$300k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, there is a lot of intro about Handshake, Handshake AI, etc. That's not part of the role description. We need to extract relevant sections. The posting includes: - About The Role (description) - Embed directly with enterprise customers ... (list of bullet-like sentences) - Location: San Francisco, CA | 5 days / week in-office - Desired Capabilities (list) - Extra Credit (list) - Perks (list) - Compensation Range: $220K - $300K We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. "About The Role" -> About the role heading. Responsibilities: The bullet list after "About The Role" describing duties: embed directly, define AI-driven solutions, build and deploy agents, design and run evals, become domain expert, work closely with Product and Platform engineers, establish engineering best practices, surface insights. Requirements: Desired Capabilities list (5-6+ years experience, real-world experience building AI applications, strong understanding of agent architectures, comfort working with enterprise customers, strong systems thinking, high ownership mentality, strong communication skills). Those are requirements. Qualifications: Possibly extra credit? Or maybe we treat extra credit as Qualifications? But Qualifications often similar to requirements. Could treat extra credit as Qualifications (nice-to-have). Or we could treat extra credit as Skills? Actually Skills could be technical skills: full-stack, backend depth, agent architectures, evals, enterprise security, VPC, on-prem, multi-agent systems, etc. But we need to follow instruction: Use sections only when posting has real specific content. We can decide to include About the role, Responsibilities, Requirements, Qualifications (extra credit), Benefits, Pay. Schedule: we have location and in-office 5 days/week => schedule info. So we can include Schedule section with that. Benefits: The Perks list includes many benefits. Pay: Compensation Range. We must not repeat job title as heading. No Job ID. We must not include boilerplate like mission statement etc. We should exclude the introductory paragraphs about Handshake, Handshake AI, Why Join Handshake Now, About Handshake AI, etc. Also exclude "Explore our mission..." etc. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the bullet points as they are, but we can format as
  • . We need to ensure we don't include filler like "commensurate with experience" etc. Not present. Let's extract exact text. From posting: About The Role As a Forward Deployed Engineer at Handshake AI Enterprise, you'll embed directly inside enterprise customer environments as part of a small, expert team. You'll learn each customer's business deeply — their workflows, their bottlenecks, where the real leverage is — and translate that understanding into production-grade AI agents that measurably change how they operate. This isn't an implementation or consulting role. You'll own the full stack: defining the solution, building and deploying agents, designing evals, and iterating until performance actually moves. Over time, you'll become a genuine domain expert in your customer's vertical — and use that expertise to build AI that keeps getting better. If you've built AI that works in the real world and want to do it again at much higher stakes — with better data, closer lab relationships, and a founding team that moves fast — this is the role. Then bullet-like sentences (actually each starts with a verb): - Embed directly with enterprise customers as part of a small deployment team, developing deep understanding of their business and workflows - Define AI-driven solutions based on real business needs — not theoretical use cases - Build and deploy production-grade agents tailored to specific customer use cases, owning end-to-end delivery - Design and run evals to measure agent performance; iterate and hill-climb until results move - Become a domain expert in your customer's vertical and use that expertise to build better AI over time - Work closely with Product and Platform engineers on your team to ship cohesive, reliable solutions - Establish engineering best practices, agent patterns, and reusable frameworks that help the forward-deployed team scale output without sacrificing quality - Surface insights from deployments that inform Handshake's platform and product roadmap Location: San Francisco, CA | 5 days / week in-office Desired Capabilities - 5-6+ years of engineering experience, full-stack with strong backend depth - Real-world experience building and shipping AI applications in production — not just fine-tuning or prototyping - Strong understanding of agent architectures, evals, and how to measure and systematically improve AI performance - Comfort working directly with enterprise customers in ambiguous, high-stakes environments - Strong systems thinking — you can zoom out to the business problem and zoom in to the technical solution without losing either thread - High ownership mentality — you care about outcomes, not just outputs - Strong communication skills — you'll be in the room with senior stakeholders regularly and need to earn their trust quickly Extra Credit - Background at a company with a forward deployment or field engineering model - Experience building multi-agent systems in production - Domain expertise in a specific enterprise vertical (recruiting, finance, ops, legal, etc.) - Familiarity with enterprise security requirements, VPC deployments, or on-prem configurations - History of building evals infrastructure or AI quality measurement tooling Perks - 🎯 Ownership: Equity in a fast-growing company - 💰 Financial Wellness: 401(k) match, competitive compensation, financial coaching - 🍼 Family Support: Paid parental leave, fertility benefits, parental coaching - 💝 Wellbeing: Medical, dental, and vision, mental health support, $500 wellness stipend - 📚 Growth: $2,000 learning stipend, ongoing development - 💻 Remote & Office: Internet, commuting, and free lunch/gym in our SF office - 🏝 Time Off: Flexible PTO, 15 holidays + 2 flex days - 🤝 Connection: Team outings & referral bonuses Compensation Range: $220K - $300K We need to output HTML fragment with headings

    for each section. We need to decide mapping:

    About the role

    -> paragraph(s) from About The Role (the descriptive paragraphs). Could be multiple

    but we can combine into one

    containing the description.

    Responsibilities

    ->
    • list of the bullet sentences after About The Role.

      Requirements

      ->
      • list of Desired Capabilities.

        Qualifications

        -> maybe Extra Credit as Qualifications (nice-to-have). Or we could treat Extra Credit as Skills? But we have Skills section also. Let's think: The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have eight possible headings. We need to include only those with real specific content. We have content for About the role, Responsibilities, Requirements (Desired Capabilities), Benefits (Perks), Pay (Compensation Range), Schedule (Location and in-office). That's six sections. We still have Qualifications and Skills left. Do we have content for them? Possibly we could treat Extra Credit as Qualifications (or Skills). But we need to decide if we should include them. 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 if we don't have specific content for Qualifications or Skills, we should not include them. However, we have Extra Credit which could be considered Qualifications (nice-to-have). But the posting already has a section labeled "Extra Credit". That is specific content. So we could map Extra Credit to Qualifications (or Skills). Which is more appropriate? Usually Qualifications are the required qualifications; Extra Credit are nice-to-have qualifications. So we could put Extra Credit under Qualifications. Then Skills could be left out if we don't have explicit skills list beyond what's already in Requirements. But we could also treat the technical skills (full-stack, backend depth, agent architectures, evals, enterprise security, VPC, on-prem, multi-agent systems) as Skills. However, those are already covered in Requirements and Extra Credit. To avoid duplication, we could decide to not include Skills section, as we don't have a distinct skills list separate from requirements. The instruction says prefer a few substantive sections over many thin ones. So we can omit Skills if not distinct. Thus sections: About the role, Responsibilities, Requirements, Qualifications (Extra Credit), Benefits, Pay, Schedule. We need to ensure we don't include any filler like "commensurate with experience". Not present. Now we need to output HTML. We'll wrap each section in

        heading then content. For About the role: we can put the descriptive paragraphs into a

        . Might need to split into multiple

        if there are multiple paragraphs. The text has two paragraphs: first long paragraph describing role, then second paragraph starting with "If you've built AI...". We could combine into one

        but better to keep as two

        elements. Let's extract exactly: Paragraph 1: "As a Forward Deployed Engineer at Handshake AI Enterprise, you'll embed directly inside enterprise customer environments as part of a small, expert team. You'll learn each customer's business deeply — their workflows, their bottlenecks, where the real leverage is — and translate that understanding into production-grade AI agents that measurably change how they operate. This isn't an implementation or consulting role. You'll own the full stack: defining the solution, building and deploying agents, designing evals, and iterating until performance actually moves. Over time, you'll become a genuine domain expert in your customer's vertical — and use that expertise to build AI that keeps getting better." Paragraph 2: "If you've built AI that works in the real world and want to do it again at much higher stakes — with better data, closer lab relationships, and a founding team that moves fast — this is the role." We'll output those as

        elements. Responsibilities list: each bullet as

      • . Requirements list: Desired Capabilities. Qualifications list: Extra Credit. Benefits list: Perks (including emojis). We should keep the emojis? They are part of the text; we can keep them inside
      • . It's fine. Pay:

        Compensation Range: $220K - $300K

        Schedule:

        Location: San Francisco, CA | 5 days / week in-office

        We must not include any other text like "Explore our mission..." etc. Now produce HTML fragment. Make sure to not include or . Just the fragment. Let's craft:

        About the role

        As a Forward Deployed Engineer at Handshake AI Enterprise, you'll embed directly inside enterprise customer environments as part of a small, expert team. You'll learn each customer's business deeply — their workflows, their bottlenecks, where the real leverage is — and translate that understanding into production-grade AI agents that measurably change how they operate. This isn't an implementation or consulting role. You'll own the full stack: defining the solution, building and deploying agents, designing evals, and iterating until performance actually moves. Over time, you'll become a genuine domain expert in your customer's vertical — and use that expertise to build AI that keeps getting better.

        If you've built AI that works in the real world and want to do it again at much higher stakes — with better data, closer lab relationships

Similar jobs