Senior Software Engineer, Forward Deployed

We need to output HTML fragment with sections: About the role? Actually we need to follow rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the job posting: It includes sections: About Us, The Role (What You'll Be Doing), Who You Are (requirements), Nice to Have, What’s In It For You (benefits), Benefits & Perks (list), Compensation Range. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. - About the role: Could be description of role (The Role). Use

  About the role

  with prose. - Responsibilities: Could be "What You'll Be Doing" list. - Requirements/Qualifications/Skills: Could be "Who You Are" and "Nice to Have". We need to decide which heading(s) to use. The posting includes "Who You Are" (requirements) and "Nice to Have". We could combine into Requirements (or Qualifications) and Skills. But we must not create thin sections. Perhaps we can have one section "Requirements" covering both required and nice-to-have? But we need to preserve all substantive info. Could split: Requirements (must-have) and Skills (nice-to-have). However "Skills" heading is allowed. Let's think: "Who You Are" includes required experience and fundamentals etc. That's more like qualifications. "Nice to Have" includes additional desirable experience. Could map "Who You Are" to

  Requirements

  (or Qualifications). And "Nice to Have" to

  Skills

  . But we need to avoid thin sections; each has decent content. - Benefits: There's "What’s In It For You" and "Benefits & Perks". Both talk about benefits. Could combine into Benefits section. Provide list of benefits. - Pay: Compensation Range is given: $237,150 - $320,850. So we need a Pay section. - Schedule: The posting says "Please note, this role is 5 days/week on-site in NYC." That's schedule info (on-site, 5 days/week). So we can include Schedule section. Thus we will have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. We must not include headings with filler. All have content. Now we need to format: Use

  for each heading. Then content: For prose use

  . For lists use

  • . We need to preserve all substantive information, not invent or summarize away detail. Must not omit details like specific companies, numbers, etc. We need to extract the relevant text. Let's gather 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." But "About Us" is not a section heading we need; we need "About the role". However the "About Us" is company description, not role. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It didn't say we cannot include company description. But we have limited headings; we could include "About the role" which should describe the role, not the company. However we could also include a short paragraph about the company under "About the role"? Might be okay but better to keep role description. The "The Role" section: "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." That's good for About the role. Now Responsibilities: "What You'll Be Doing" bullet list (though not bullet but sentences). We need to convert to list items. List: - 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 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. We need to preserve all detail. Ensure we keep the exact phrasing? Not required to be exact but preserve substance. We'll use list items. Now Requirements (Who You Are): Content: "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." We can turn into list items. Now Skills (Nice to Have): Content: "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." List items. Now Benefits: Combine "What’s In It For You" and "Benefits & Perks". What’s In It For You: - 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 list: - 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. We'll create a
    with items. Note: "Additional Perks" is a heading inside benefits; we could just treat as a list item with sublist? But we can't nest
    inside
    • ? Actually we can but maybe better to keep flat list. We'll just include each bullet as separate
    • . For "Additional Perks" we could include as a
    • that contains a sublist? Might be okay but we can just list the items under additional perks as separate
    • items. Thus Benefits section list items: - 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. - 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 - 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 Now Pay: Compensation Range: $237,150 - $320,850. We'll put in