Closure
Closure

Founding Forward Deployed Engineer

$130–215kNew York, NY; San Francisco Bay Area, CA; Remote (US)On-siteSeniorFull-time

Posted 8 days ago

The role in short

Embed with law enforcement agencies to build and deploy AI-driven digital analysts and integrations that solve evidence overload in criminal investigations.

Role Description

  • Live With Users: You are thrilled to apply your engineering skills to solving real-world user problems, directly with users (and frequently in-person).

  • Pre-Scale Problem Solver: You are a strong engineer, but you are comfortable building things that do not “scale”; whether a one-off analysis or an integration.

  • Product Thinker & Tinkerer: Your experience on the frontlines with customers will directly translate into product roadmaps. You are an executor who turns customer pain into PRs, or clear understandings of what/how we must build.

About You

  • Mission-Driven: Excited to contribute to U.S. government competence and public safety.

  • Owner-Builder Mindset: Bias toward action, thrives in extremely fast-paced environments. Looking to do the best work of your life.

  • Comfort with Ambiguity: We are an early-stage startup with many exciting questions to be answered; you run toward unasked and unanswered questions.

Location

  • New York City (Preferred)
  • Bay Area, California (hybrid work arrangements available)
  • Remote with regular travel for exceptional candidates
  • Travel: 25-75% of the time

Additional Details

  • Comp

    • Salary: $130k-$215k, with potential for significant adjustments based on experience and ability
    • Equity: Meaningful ownership stake at founding-hire levels
    • Bonuses based on company performance
  • Benefits:

    • We contribute 3% to your 401(k), regardless of your own contribution
    • Unlimited PTO
    • Health, Dental (Direct or Reimbursed)
    • Short- & Long-term Disability Insurance
    • Life Insurance
    • Discounted Gym & Class Membership
  • Criminal Justice:

    • Criminal Justice Ready: Given the sensitivity of our work, we support employees through FBI background checks / CJIS clearance process as needed

Closure is an equal opportunity employer. We do not discriminate on the basis of race, color, religion, sex, sexual orientation, gender identity, national origin, age, disability, veteran status, or any other legally protected characteristic.

About Closure

Closure helps law enforcement search evidence and solve crime. We build digital analysts that support public servants at every level of criminal justice.

Public servants across the U.S. use Closure to expedite investigations into cold cases, homicides, gang conflicts, sexual assault, and other serious offenses, as well as critical administrative support.

We’re live with police departments, prosecutors, sheriffs, state investigative agencies, and other criminal justice stakeholders across the country, reducing evidence overload across the criminal justice system.

Closure is an intentionally tight-knit team of ambitious engineers and operators. We operate with high speed, high integrity, high autonomy, and low ego (or so we like to think), backed by reputable investors including Y Combinator, CRV, Pathlight, and others.

Read more about our work, here:

Prep for this interview

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

  1. 1Discovery and scoping
    They wrote: “We’re live with police departments, prosecutors, sheriffs, state investigative agencies, and other criminal justice stakeholders across the country, reducing evidence overload across the criminal justice system.”

    A senior executive and the hands-on team want different things. How do you handle it?

    How to answer

    Why they ask: Enterprise deployments have several stakeholders. Senior FDEs are expected to align them, not pick a side quietly.

    1. Meet each side to learn what they need and why
    2. Find the shared goal (usually the business metric the executive owns)
    3. Propose a plan that meets that goal and removes the team's biggest pain
    4. Get a written decision so the project doesn't stall later

    Tip: Show that you get both views on the table early and tie the plan to the goal the executive owns.

  2. 2Integrations and APIs
    They wrote: “Pre-Scale Problem Solver: You are a strong engineer, but you are comfortable building things that do not “scale”; whether a one-off analysis or an integration.”

    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. 3Cloud, deployment and security
    They wrote: “Criminal Justice Ready: Given the sensitivity of our work, we support employees through FBI background checks / CJIS clearance process as needed”

    The customer's security team sends a 200-question review. How do you handle it?

    How to answer

    Why they ask: Security reviews often block deals. FDEs help get through them.

    1. Start from your company's standard answers (SOC 2 report, past reviews)
    2. Answer clearly; don't oversell
    3. Bring in your security team for anything you're unsure of
    4. Keep the new answers for the next customer

    Tip: Reuse past answers, flag honest gaps, and offer a call for the hard questions.

  4. 4Ownership and working with customers
    They wrote: “Comfort with Ambiguity: We are an early-stage startup with many exciting questions to be answered; you run toward unasked and unanswered questions.”

    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.

  5. 5Travel
    They wrote: “Remote with regular travel for exceptional candidates”

    How do you handle being on the road with customers for weeks at a time?

    How to answer

    Why they ask: Many FDE roles involve regular travel. They check you know what you're signing up for.

    1. Your past travel or on-site experience
    2. How you stay productive away from the team
    3. What travel level works for you, said plainly

    Tip: Be honest about what works for you. A mismatch here hurts both sides later.

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.

Similar roles at other companies

Closure

$130–215k · On-site

Apply