Member of Technical Staff; Frontend

Footprint is the agentic platform that learns your compliance program and runs it end to end.

Compliance teams at banks and fintechs are drowning in financial crimes investigations. Transaction volumes are surging, regulators keep raising the bar, and the work still runs on manual review queues stitched together from legacy vendors.

Percy, our agentic system, learns each team's procedures and makes the same calls their analysts would: clearing false positives, escalating real risk, writing the case narrative, and documenting every decision for audit. It cuts review workloads by 70%+.

The harder problem is underneath. Every investigation is grounded in the data sources compliance teams already trust, and every case commits to an organizational memory that compounds — so a pattern one analyst caught in March surfaces automatically in October, across KYC, EDD, sanctions, and monitoring. Whether the team is five analysts or 500, they share one brain. Every memory carries provenance.

Agents propose; humans approve. That's four years of identity infrastructure sitting under the agent, and it's the part nobody can bolt on later.

We're backed by QED, Index, and Box Group, and trusted by FDIC- and OCC-regulated banks plus fintechs like Bilt, Nuvei, and Moon Pay. We 5x'd revenue last year. The team is small, senior, and ships fast.

For four years, Footprint's frontend was the front door for developers: onboarding flows customers embed, SDKs they integrate, a dashboard where they configure verification.

Percy changed who lives in the product. Over the past year, compliance teams and investigators moved from configuring Footprint to working inside it: reviewing what an agent found, editing the case narrative, signing off on decisions a regulator will read. The interface became the place our users do their job, and the bar for polish, speed, and clarity rose with it.

The team that owns all of this is a small team of senior engineers. The design system, the SDKs, the monorepo tooling, the release pipeline - all of it runs through them, and they set the standards the rest of engineering ships frontend against.

You’ll report directly to Head of Frontend Engineering - Rafael Motta.

• User-facing features, end to end. From spec to build to deploy to iterate, making the product and design tradeoffs along the way. The analyst-facing surfaces are the newest part of the product and the least settled
• The SDKs external developers use to embed Footprint. Clean APIs and good docs here shape our customers' integration experience directly, and those decisions are hard to take back once someone has shipped against them
• Platform and tooling. CI/CD, releases, and our pnpm monorepo. This work has been carried alongside product work, which is why it's on this list
• Performance and observability. You own the performance budgets and the monitoring for screens people sit in all day
• The design system. Own and evolve the component library, keeping the UI consistent, accessible, and fast to build on
• Customer empathy. Talk to the people who use what you build and turn what they struggle with into the product

React

• Type Script
• Next.js
• Tailwind
• Vercel

Deep experience with most of this, and the judgment to pick up the rest, is what matters.

• 4+ years shipping production frontend in modern React and Type Script - fluent in both, and comfortable moving fast in a large shared codebase
• You ship end to end, prioritize outcomes, and make smart tradeoffs between speed, polish, and scope
• Genuine design sense - you sweat the details, and the interfaces you ship show it
• You write readable, well-structured code and can lead technical decisions without over-engineering
• You've owned the lifecycle of what you ship: the release,…