Get more replies from employers
Send a job-specific resume in minutes.
Closure is seeking a Forward Deployed Engineer to own pilots, ingest evidentiary data, configure the product per agency, and write scripts as needed while detectives and prosecutors work cases. Time on engagements ranges 2–6 weeks, with a mix of on-site work and collaboration across teams.
Typical workload includes 60% customer-facing activity, 30% building/configuring, and 10% internal work. This is not a pure sales role; you’ll work inside customer codebases to deliver real outcomes for law
Type: Full-time | On-site (in-hub) | New York City, NY · San Francisco, CA Compensation: $115,000–$175,000 + founding-hire equity (competitive) Hiring count: 1 Visa sponsorship: None available Reports to: Not specified on role page (works alongside Tina — existing FDE, Judith — technical CS, and engineering; interviews with Aaron and Gilad)
Closure helps law enforcement search evidence and solve crime — police and prosecutors across the US use it to accelerate investigations into homicides, cold cases, and other major offenses by cutting through digital evidence overload. The founding team includes ex-Palantir and ex-IDF engineers who have built national-scale systems before.
Roughly 10 active customer deployments today, with a path to 25–40 over the next 9 months. Primary customer geography is California and Alaska, expanding through other Western states and the Southeast (Florida heating up).
Founded: 2025 | Team size: 1–10 | Total funding: Not disclosed (Seed) Industry: Public safety / law enforcement AI · legal & gov-tech Website: closure-intel.com Office: NYC (primary) · SF Bay Area (secondary)
Own customer outcomes end-to-end as a Forward Deployed Engineer: scope pilots, ingest messy evidentiary data, configure the product per agency, write scripts and integrations when the product doesn't quite fit, and sit with detectives and prosecutors while they work cases — feeding learnings straight into the roadmap.
Typical engagement is a 2–6 week pilot annual contract in-agency expansion. Time split is roughly 60% customer-facing (calls, onsite, async), 30% building/scripting/configuring, 10% internal (product feedback, playbooks, hiring loops). This is not a sales-engineering seat — you live inside customer codebases, dig through real evidence data, and write the scripts that make the product work per agency.
Tech stack: Python and/or TypeScript · APIs · data pipelines
Stage 1 — Pending Approval — Candidates awaiting initial approval. Stage 2 — Intro with Aaron — Intro conversation. Stage 3 — 60‑min Technical and Scenario with Gilad — Technical + scenario interview. Stage 4 — Take‑Home or Live Exercise — Practical exercise. Stage 5 — 60‑min Customer Simulation — Simulated customer interaction. Stage 6 — Onsite in NYC or SF — In-person round. Stage 7 — Reference Calls — 2–5 references, including at least 2 people they've deployed alongside. Stage 8 — Offer Extended Stage 9 — Candidate Hired — Candidate accepts and starts.
Not present as a dedicated section on the role page. Reference companies named in Closure's outreach: Palantir, Anduril, Magnet Forensics (or comparable FDE / solutions / implementation orgs selling into non-tech-native customers).