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 · TypeScript · Next.js · Tailwind · Vercel

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

Member of Technical Staff (Frontend)

Responsibilities

Benefits

Company

Footprint

More roles at Footprint