Newcode
Newcode2 open roles

Head of Forward Deployed Engineering

Chicago, ILHybridSeniorFull-time

Posted 19 days ago

The role in short

Lead and build a team of Forward Deployed Engineers who embed with law firm clients to design, implement, and support production AI workflows and integrations on the Aurora platform.

Build the team that makes legal AI work in practice

Newcode helps legal organizations build, govern, and deploy AI workflows connected to their knowledge and existing systems. Our Aurora workflow platform enables teams to turn firm expertise into repeatable workflows that operate within the firm’s technology environment.

We are hiring a Head of Forward Deployed Engineering to build and lead the software engineers who bring those workflows into production. You will combine engineering leadership, practical delivery experience, and a deep understanding of law-firm technology to help clients move from a promising use case to a reliable, supported deployment. This role reports to the CEO. The aim is to have this role have 5 people reporting to it over the next 6 months.

The Opportunity

At Newcode, engineering and client delivery are central to the business. You will shape the FDE function, develop its people and delivery methods, and use client experience to influence the platform. This is a hands-on leadership role: you must be able to assess architecture, review code, debug difficult integrations, and lead important client conversations while building a team that can deliver without depending on you for every decision. We expect roughly 40% of your time to be hands-on technical work: design reviews, code reviews, and debugging critical integrations.

How the team works

Client delivery takes place in pods comprising a senior legal engineer, a forward-deployed engineer, and an account manager focused on retention and expansion. The senior legal engineer leads the pod and owns the legal problem, workflow requirements, and legal acceptance criteria. The FDE translates those requirements into working software, integrations, and deployable components.

You will manage the FDEs across pods and own engineering quality, staffing, coaching, and technical delivery practices. You will partner with the head of legal engineering, commercial leaders, and core engineering to align client priorities, technical feasibility, and platform investment.

You will also serve as the FDE in the pods for our most strategic and complex US firms, and you will set the standard for forward deployment at Newcode: the Aurora playbook, the AI Academy for Aurora users, and the field patterns that make it into the product.

What you will own

  • Build and lead the FDE team: recruit strong engineers, coach their development, set expectations, and establish clear technical standards.
  • Lead technical discovery with law-firm technology teams; map data flows, integrations, access controls, dependencies, and deployment constraints.
  • Guide implementation of Aurora workflows, connectors, and client-specific extensions; stay close enough to the work to review designs and unblock delivery.
  • Run the AI Academy for each firm's Aurora users, which is where every engagement starts.
  • Configure Aurora flows around each firm's use cases, starting with the ones agreed in the tailored demo, and join tailored demos when a firm's needs call for Aurora.
  • Map how practice groups such as litigation, M&A, regulatory, and knowledge management work, and turn that into flow designs lawyers trust.
  • Design evals with each firm so quality is measured in lawyers' terms, not just model metrics.
  • Earn the trust of CIOs, innovation leaders, and firm engineers through specific deployment experience, candid tradeoffs, and dependable follow-through.
  • Establish a repeatable path from discovery and scoping through evaluation, release, monitoring, support, and handoff. Define ownership before work goes live.
  • Protect client confidentiality and access boundaries. Ensure solutions have appropriate testing, traceability, observability, and human review for their intended use.
  • Set realistic estimates and delivery commitments with legal engineering and account management; surface scope changes, risks, and dependencies early.
  • Partner with core engineering on missing capabilities. Identify extensions worth reusing and ensure shared platform changes have a named owner and support plan.
  • Be the field's voice in roadmap decisions. Bring patterns, not anecdotes, with a view on how often a need comes up and what it would take to build it into the product.
  • Partner with our Oslo Product and Engineering teams across time zones, and represent the US customer in core platform decisions.
  • Track delivery speed, reliability, workflow adoption, engineering effort, and reuse; use the results to improve client outcomes, estimates, and delivery economics.

Requirements

What you bring

  • Demonstrated experience hiring, managing, and developing software engineers who deliver and support production systems.
  • Direct experience deploying technology within law firms, either as an internal technology leader or a vendor delivery leader with substantial firm exposure.
  • Practical fluency in law-firm systems and operating constraints, including document management, matter permissions and ethical walls, identity, knowledge systems, and billing or practice-management integrations.
  • An understanding of how law-firm work gets done, from document review and due diligence to litigation support and knowledge management, and how lawyers judge quality.
  • A strong engineering background: 5+ years building production software, with a computer science or engineering degree or equivalent experience.
  • Strong software engineering judgment across APIs, integration design, data access, cloud deployment, testing, incident handling, and maintainability. You can interrogate implementation details, you still write production code (Python or TypeScript), and you are comfortable debugging in a client environment.
  • Hands-on experience taking LLM-based or agentic workflows into production, including retrieval, agents and tool use, structured outputs, guardrails, evaluation design, permission-aware data access, failure handling, and monitoring.
  • Experience turning ambiguous client needs into scoped, measurable delivery plans and explaining technical tradeoffs to executives and implementation teams.
  • The range to earn the trust of a managing partner and pair with an engineer on the same day, explaining tradeoffs in plain language.
  • A record of building repeatable delivery practices and reusable components rather than relying on individual heroics. Comfort building a function in an evolving company.

Additional experience we value

Microsoft Azure and Microsoft 365; iManage or comparable document management systems; ethical-wall and matter-security tooling; Elite, Aderant, or similar finance platforms; and experience building a customer-facing engineering function. A law degree is not required; direct law-firm technology deployment experience is. A law degree (JD, LLM, or equivalent), or experience practicing law or working in legal operations or legal innovation, is a plus. We value demonstrated capability over a particular degree or job title.

What success looks like

In your first 30 days, you will map active deployments, team capabilities, and delivery risks, and set baselines for delivery time, effort, adoption, and production issues. By 60 days, a delivery playbook is running on at least two active deployments, with staffing plans, technical reviews, release criteria, and support ownership in place. By 90 days, the team delivers across at least three client engagements, including at least one led day to day by an FDE other than you, and at least one component has been reused. By 180 days, you lead a team of five people that delivers repeatably across multiple clients, and firm technology leaders trust the team. You will see these milestones from your first day, and we will review your progress against them with you at 30, 60, 90, and 180 days.

Location: Chicago, hybrid, 3 days per week in the office. Expect client travel of roughly 30%, typically for discovery workshops and go-live support, with occasional trips to Oslo. Collaboration with distributed colleagues is part of the role.

Why join Newcode

At Newcode.ai, we specialize in making law firms AI-native through a configurable AI harness designed for the realities of legal work. Achieving that mission takes more than powerful technology: it requires exceptional people who can understand how lawyers work, configure solutions around their needs, and help them realize the immense value AI can create. As part of our collaborative, high-growth team, you'll work side by side with visionary founders at the forefront of AI and legal innovation, shaping both our product and the definition of AI native legal work.

We believe in being transparent about what it's like to work at Newcode.ai. As a fast-growing startup, we're building and evolving every day. That means not every process, playbook, or framework is already in place, and priorities can shift quickly.

The people who thrive here are comfortable with ambiguity, take ownership, and don't wait for perfect direction. They are resourceful, proactive, and able to "figure it out", solving problems, creating structure where needed, and helping build the company as they go. If you are good with this then, great! Keep reading to learn more.

Company stage. Newcode is a growth-stage legal AI company founded in 2021. It has moved beyond early product validation into scaling deployments and expanding in the U.S. The company describes its product as a configurable AI platform that connects a firm’s data, systems, and workflows, with controls for permissions, models, and deployment.

Funding. Newcode has a total funding of $20 million. The Series A was led by OnDean Forward, with participation from The LegalTech Fund, Antiportfolio Ventures, Relativity’s investment arm Rel Labs, and existing investors.

Traction and deployments. Today Newcode serves more than 100 law firms and government agencies in Europe and the United States, with annual recurring revenue more than tripling over the prior 12 months. Check out our webpage for our most recent customers.

Why now is a compelling time to join.

Newcode is at an exciting stage of growth. With fresh Series A funding and strong customer and revenue growth, we are investing in the next chapter of our U.S. expansion.

Our platform is moving beyond standalone AI tools and into the everyday workflows of leading legal teams. From firmwide deployments to integrated legal research, we are helping customers put AI to work on meaningful, real-world challenges.

As we expand our product, customer support, go-to-market, and U.S. partnerships, you will have the opportunity to take on important work and help shape how we grow. You will join a global team of more than 60 people, with the scale to serve major organizations and the agility to make a visible impact.

If you are excited to build practical AI for the legal industry and help shape a company’s next stage of growth, this is a great time to join Newcode.

Benefits

Competitive base salary with equity and bonus. Benefits include health, dental, and vision insurance; 401(k); paid time off; and parental leave.

Newcode is an equal opportunity employer and welcomes applicants of all backgrounds

Visa Sponsorship:

At this time, Newcode is unable to provide visa sponsorship. Candidates must be authorized to work in the applicable country without employer sponsorship.

Prep for this interview

5 questions likely to come up at Newcode, each matched to a line in this posting.

  1. 1Discovery and scoping
    They wrote: “Establish a repeatable path from discovery and scoping through evaluation, release, monitoring, support, and handoff. Define ownership before work goes live.”

    A customer says “we want AI in our claims process.” What do you ask in the first meeting?

    How to answer

    Why they ask: Most FDE work starts this vague. They want to hear you find the real problem before you pick a tool.

    1. Map the current process: who touches a claim, in what order, with which systems
    2. Find the slowest or most error-prone step and ask what it costs them
    3. Agree on one measurable goal (for example time per claim, or error rate)
    4. Ask what data you can access, and who signs off on security

    Tip: Ask about the work, not the technology. Who does it today, how long it takes, what a mistake costs, and how they'd know it got better.

  2. 2Integrations and APIs
    They wrote: “Lead technical discovery with law-firm technology teams; map data flows, integrations, access controls, dependencies, and deployment constraints.”

    Walk me through connecting our product to a customer's internal system that has no documentation.

    How to answer

    Why they ask: This happens weekly in the job. They want a calm, step-by-step method.

    1. Find who owns the system and get read access to a test environment
    2. Watch real traffic or logs to learn the data shapes
    3. Build a thin adapter with logging around every call
    4. Agree on how failures get reported, and who fixes what

    Tip: Talk about finding the owner of the system first. The code is the easy part.

  3. 3LLMs, RAG and agents
    They wrote: “Design evals with each firm so quality is measured in lawyers' terms, not just model metrics.”

    How do you know an LLM feature is good enough to ship?

    How to answer

    Why they ask: Evals are what separate a demo from production. Many roles list them by name.

    1. Write 50–200 real examples with expected outcomes, with customer experts
    2. Agree on a pass bar and the errors that are never acceptable
    3. Score automatically where possible; review a sample by hand
    4. Re-run on every prompt or model change, and watch live traffic after launch

    Tip: Describe a test set built with the customer, a pass bar agreed up front, and checks that run on every change.

  4. 4Coding
    They wrote: “Demonstrated experience hiring, managing, and developing software engineers who deliver and support production systems.”

    How do you keep quality high when you ship fast at a customer site?

    How to answer

    Why they ask: Speed is the job, but broken code at a customer is costly. They want your guardrails.

    1. Tests for the parts that touch customer data or money
    2. Code review even when it's fast, ideally by someone on the product team
    3. Feature flags and an easy way to roll back
    4. Clean up the shortcuts in the next release, and write them down

    Tip: Name the few checks you never skip, and what you skip on purpose.

  5. 5Ownership and working with customers
    They wrote: “Experience turning ambiguous client needs into scoped, measurable delivery plans and explaining technical tradeoffs to executives and implementation teams.”

    Tell me about a project where the requirements kept changing. What did you do?

    How to answer

    Why they ask: Ambiguity is the norm. They want proof you can keep moving without a clear spec.

    1. The project and why requirements kept moving
    2. What you did to pin them down (short demos, written decisions)
    3. The trade-offs you made to keep shipping
    4. The result, with a number if you have one

    Tip: Show how you reduced the change, beyond how you coped with it.

Not the one? Get the next one by email

New roles land here every day. Pick what you want to hear about.

FDE Info

Want the job, not just the posting? Learn how FDEs work.

FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.

Free. One email a week. Unsubscribe in one click.

More at Newcode

Similar roles at other companies

Newcode

Hybrid

Apply