Senior Forward Deployed Engineer

We need to output HTML fragment with sections: About Us, The Role (maybe "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly. We have sections: About Us (maybe "About the role"? Actually "About Us" is about company; but they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can still use "About Us" as heading? They said use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but they gave examples. Probably we should follow those examples: "About the role" for description of role, "Responsibilities" for duties, "Requirements" for qualifications, "Skills" maybe for nice-to-have, "Benefits" for benefits, maybe "Pay" if present (not present), "Schedule" if present (they gave on-site 5 days/week). That's schedule info: "Please note, this role is 5 days/week on-site in Manhattan, NYC (Union Square)". So we can include a Schedule section. We need to preserve all substantive info, remove boilerplate (EEO, etc). Also remove duplicated lines, navigation, cookie, legal, application instructions. The posting includes "Please note, this role is 5 days/week on-site in Manhattan, NYC (Union Square)" at top. Also includes "About Us" paragraph. Then "The Role" description. Then "What You'll Be Doing" (responsibilities). Then "Who You Are" (requirements). Then "Nice to Have" (skills). Then "What’s In It For You" (some bullet points). Then "Benefits & Perks:" with list. We need to not repeat job title as heading. No Job ID. We need to output only HTML fragment. Let's structure:

About the role

maybe combine The Role description? Actually "About the role" could be the summary paragraph after The Role heading. The posting says: "The RoleAs a Senior Forward Deployed Engineer, you'll work directly..." That's the role description. So we put that in

under About the role. Then

Responsibilities

with

• from "What You'll Be Doing". Then

  Requirements

  with
  • from "Who You Are". Then

    Skills

    with
    • from "Nice to Have". Then

      Benefits

      with
      • from Benefits & Perks list. Then

        Schedule

        with

        containing the on-site note. Also maybe include "About Us" as a section? Not in examples but could be included as "About the company"? But they said prefer few substantive sections over many thin ones. The About Us is substantive. Could include as

        About the company

        but not in list. Might be okay. However they said use

        for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but they gave examples. Safer to include About the company as a heading? Might be considered extra but still substantive. However they said "Prefer a few substantive sections over many thin ones." Adding About Us adds another section. Might be okay but we could incorporate About Us into About the role? Not ideal. Maybe we can treat About Us as a preamble paragraph before sections, not as a heading. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." It doesn't forbid other headings. So we can include About Us as a heading like

        About Legora

        . That seems fine. But they gave examples of headings; we can still use others. I'll include About Legora. Now we need to extract content. About Us paragraph: "Legora is redefining how legal work gets done. Not built for lawyers, built with them. We work alongside the world’s best legal teams, who expect excellence, precision, and speed, and we hold ourselves to the same bar. Our AI-native workspace lets legal professionals move faster, think more clearly, and operate with sharper precision. By analysing thousands of documents in minutes and powering end-to-end workflows, we cut through complexity, teams can focus on what matters: judgment, strategy, and outcomes. 1,000+ customers across 50+ countries trust us, including Cleary Gottlieb, Goodwin, Linklaters, White & Case, Dentons, and Barclays. We’ve scaled to $100M+ in ARR, with teams across Europe, North America and APAC, and continue to expand through acquisitions including Qura, Walter AI and Graceview. We partner with world-class performers: including Aaron Judge and the New York Yankees, Ludvig Åberg (and his caddie), and campaigns featuring Jude Law. Joining Legora means three things.We lean in: ownership over titles, outcomes over intentions.We fight for excellence: high standards, direct, ego-free feedback.We grow together: as a team and with our customers.Mission before ego. Everyone contributes. No one coasts.If you’re driven by impact, pace, and raising the bar. This is the place." We need to preserve all substantive info. Keep as paragraph(s). Could split into multiple

        but okay. Now Responsibilities: list from "What You'll Be Doing": - Work directly with enterprise customers to understand their systems, workflows, and constraints, translating their needs into clear technical requirements. - Own engineering delivery from discovery and solution design through implementation, testing, deployment, and troubleshooting. - Resolve ambiguity across customer stakeholders and internal teams. Challenge assumptions, explain tradeoffs, and align people on a realistic scope and timeline. - Build integrations between Legora and customer systems, alongside changes to our core product. Identify opportunities to turn customer-specific work into reusable capabilities. - Manage multiple engagements with a high degree of independence, sequencing work, identifying dependencies, and communicating risks early. - Diagnose and resolve complex issues where Legora meets a customer's environment, applying sound engineering judgment under time pressure. - Bring customer insights back into product and engineering decisions, and help develop reusable tooling and engineering practices as the function grows. Now Requirements: from "Who You Are": - 5-7+ years of software engineering experience, with recent, hands-on ownership of production software and clear responsibility for technical decisions and delivery. - Strong software engineering fundamentals. You can independently design, build, test, and ship reliable software, and work effectively in an existing product codebase. - Comfortable leading technical conversations with customers. You can explain decisions and tradeoffs clearly to both engineers and nontechnical stakeholders. - Experienced in taking ambiguous problems across multiple teams and turning them into working solutions. You can point to what you decided, built, and delivered. - Strong product judgment. You understand the problem behind a request and can balance immediate customer needs with maintainability and broader product value. - Able to prioritise and deliver without detailed direction. You set realistic expectations, surface problems early, and take responsibility for outcomes. - Adaptable across technologies and environments. You can learn unfamiliar systems quickly and make progress when requirements evolve. Now Skills (Nice to Have): - Experience building B2B enterprise software in a fast-moving environment. - Previous forward deployed or embedded engineering experience involving hands-on production development. - Experience working across engineering and product, particularly where you helped define what to build. - Familiarity with enterprise integrations, APIs, authentication, and data flows across systems you don't control. - TypeScript experience. We use it extensively, but welcome strong engineers from other stacks. Now Benefits & Perks: list: - Global collaboration: Partner with teams and clients across Europe, APAC, and North America. - Competitive package: Comprehensive salary, benefits, and tools for success. - Meaningful work: Your efforts shape how thousands of lawyers use AI daily. - In-person environment: Union Square office designed for ambitious builders and company provided lunch daily. - Benefits & Perks: We invest in our people with a comprehensive, thoughtfully designed benefits package: - Medical, Dental & Vision - Multiple medical plan options through Aetna and Kaiser Permanente - HSA or Healthcare FSA (based on plan selection) - Dental plans via MetLife - Vision plans via Vision Care - Family Support - Generous parental leave - Free access to Maven Clinic - Dependent Care FSA - Free One Medical membership for employees and dependents - Additional Perks - Pre-tax commuter benefits - Life Insurance + STD/LTD - 401(K) with generous company match - Unlimited PTO - Robust voluntary benefits, including identity protection (via Aura), legal coverage via MetLife, pet savings programs, and more We need to preserve all. Could flatten into

        • items. Might be long but okay. Schedule: "Please note, this role is 5 days/week on-site in Manhattan, NYC (Union Square)". We'll put in

          . Now we need to output HTML fragment only. Let's craft:

          About Legora

          ...

          About the role

          As a Senior Forward Deployed Engineer, you'll work directly with our largest enterprise customers to understand their needs and build the software that connects Legora to their systems and workflows. You'll own complex engineering projects from an ambiguous customer request through technical scoping, implementation, and production delivery. Your work will span custom integrations and contributions to Legora's core product. You'll use your technical and product judgment to determine what a customer needs, what we can deliver, and where a solution has value beyond a single engagement. This is a hands-on senior individual contributor role within Enterprise Engineering. You'll bring the engineering depth to contribute directly to our core product, alongside the communication and judgment to lead technical delivery with customers. You'll work closely with product engineers, Legal Engineers, and Engagement Managers, taking ownership of technical decisions and implementation.

          Responsibilities

          • Work directly with enterprise customers to understand their systems, workflows, and constraints, translating their needs into clear technical requirements.
          • Own engineering delivery from discovery and solution design through implementation, testing, deployment, and troubleshooting.
          • Resolve ambiguity across customer stakeholders and internal teams. Challenge assumptions, explain tradeoffs, and align people on a realistic scope and timeline.
          • Build integrations between Legora and customer systems, alongside changes to our core product. Identify opportunities to turn customer-specific work into reusable capabilities.
          • Manage multiple engagements with a high degree of independence, sequencing work, identifying dependencies, and communicating risks early.
          • Diagnose and resolve complex issues where Legora meets a customer's environment, applying sound engineering judgment under time pressure.
          • Bring customer insights back into product and engineering decisions, and help develop reusable tooling and engineering practices as the function grows.

          Requirements

          • 5-7+ years of software engineering experience, with recent, hands-on ownership of production software and clear responsibility for technical decisions and delivery.
          • Strong software engineering fundamentals. You can independently design, build, test, and ship reliable software, and work effectively in an existing product codebase.
          • Comfortable leading technical conversations with customers. You can explain decisions and tradeoffs clearly to both engineers and nontechnical stakeholders.
          • Experienced in taking ambiguous problems across multiple teams and turning them into working solutions. You can point to what you decided, built, and delivered.
          • Strong product judgment. You understand the problem behind a request and