Forward Deployed Engineer

New Form is building the creative intelligence layer for paid advertising. We pair an in‑house creative pod with Framework
, our proprietary statistical testing engine that instruments every ad it ships, to build a creative ontology for each brand: a living map of what works, why it works, and how to make more of it. The service we sell is the creative your paid spend needs. The asset we build is yours to keep.

We work with brands like Kalshi, Babbel, Acorns, and Western Union
. We oversee north of $100M in annual ad spend
, ship 3,000+ ads a month
, and Framework has run 6,000+ structured creative tests to date. We're at $7M ARR, doubling YoY for two years running.

This is a Palantir-style Forward‑Deployed Engineer role adapted for the creative supply chain. You won't be writing tickets handed to you by a PM. You'll be in the room when a strategist hits a workflow ceiling, deciding in real time whether the answer is a new Framework feature, a one‑off automation, or a data pipeline that didn't exist yesterday. Then you build it.

You'll embed with our services pods: strategists, creators, media buyers, Creative Intelligence Leads and build the software they need to run faster, learn more, and ship more winning ads.
You own a roadmap, not a ticket queue. The roadmap is generated by what you observe sitting next to operators in real client work.

The work compounds in two directions. The bespoke things you ship for one client become the next generalized Framework feature. The patterns you spot across the services team become the roadmap.

• Embed with one or two pods at a time. Sit in their reviews, briefs, and post‑mortems. Understand the work end to end before you write code.

• Build into Framework when the problem is structural. Build bespoke when the problem is one client's. Make the call on which is which.

• Own the end‑to‑end technical lifecycle for client deployments: onboarding, ad account integrations (Meta, Tik Tok, Google), data reconciliation, custom dashboards, and the tooling that closes the gap between platform APIs and how strategists actually want to work.

• Translate field signal into product. Every workaround a strategist invents is a feature waiting to be written. Surface those patterns to the core engineering team and to leadership directly.

• Run your own roadmap. We'll set direction; you set sequence. You should be able to defend why the thing you shipped this week mattered more than the thing you didn't.

• 30 days: You've embedded with at least one pod, mapped where their workflow is breaking, and shipped your first piece of useful tooling to production. Small is fine. Real is what matters.

• 60 days: You've shipped meaningful client tooling end to end, identified two or three patterns that should become Framework features, and the pod you're embedded with treats you as part of the team.

• 6 months: You've shipped at least one of those patterns into core Framework, built repeatable deployment runbooks for new client onboardings, and the services team is asking for you by name. The playbook for the next FDE hire is yours.

• 3+ years building software, with real time in client‑facing, deployment, or solutions engineering work. You've shipped things that lived inside someone else's company.

• Fluent in Type Script and Next.js, comfortable in modern React, and have built non‑trivial backends.

• You've worked with LLM APIs (OpenAI, Anthropic, Gemini) at the application layer.

• You can hold a real conversation with a non‑technical operator without losing precision. You can sit in a media review and understand what's actually broken. You can also write the PR that fixes it.

• You're scrappy in the way that ships, not the way that accumulates tech debt. The…