Want to know if this job is worth applying to?
Remote
Remote only
Not Available
Remote, US
Nametag helps companies verify the real person behind high-risk workforce actions, from account recovery to identity checks, before attackers can exploit the gap.
Deepfakes, social engineering, and stolen credentials have made "who is actually on the other side of this request?" a critical infrastructure problem. We are building the identity verification and account protection layer companies use to answer that question quickly, securely, and with less friction for real users.
We're looking for a Technical Product Manager to own how Nametag gets into the systems our customers already live in.
Nametag is rarely the application someone opens. It's the identity check that happens inside the helpdesk ticket, the HR onboarding flow, the Slack message from someone claiming to be the CFO. That means our growth is gated less by what our platform can do than by how well we embed it into other people's software — Workday, ServiceNow, Slack, Okta, ICIMS, UKG, and the long tail behind them.
This role exists to run that work as a discipline rather than a series of one-offs. You'll join a dedicated team whose entire purpose is expanding Nametag into new systems and new use cases, and you'll own the question that decides whether each one succeeds: how, concretely, will this integration work?
That question is harder than it sounds, because the environments we integrate into are tightly constrained. Workday's extensibility surface is narrow and governed. Slack gives you modals, slash commands, and a Block Kit vocabulary that was not designed for identity verification. ServiceNow gives you a lot of rope and a lot of ways to hang a customer's upgrade path. Many of these platforms give you almost no UI to work with, strict review processes, and no appetite for anything that looks like a redirect to a third party. Designing a verification flow that is secure, legible to the end user, and actually buildable inside those limits is the core intellectual work of this role.
You'll do that work end to end: research the target platform and its extension model, decide what the integration should look like, spec the Nametag-side APIs and the target-side calls, design the admin and console experience with our designers, and hand engineering something they can build without having to re-derive your reasoning. You'll also own the marketplace and listing path, which is often the real constraint on timeline.
We're an AI-forward team and this role is one of the clearest cases for it. The research, spec, mockup, and handoff work behind each connector is substantially agent-assisted, and we expect you to push that further — the goal is for one strong PM to produce well-researched, buildable integration plans at a rate that used to require a team. You own the judgment and the accuracy; the tooling is what gives you the reach.
Design how each integration actually works
Develop real expertise in each target platform's extension model — its APIs, webhooks, UI surfaces, auth model, app review process, and limits.
Design the verification flow inside those constraints: where the user is prompted, what they see, how the result comes back, and what happens when it fails.
Make the hard calls explicit — embedded versus redirect, synchronous versus asynchronous, what degrades gracefully when the host application gives you three fields and a button.
Identify the constraint that will kill the integration early, rather than three weeks into the build.
Own the plan from research to handoff
Research the target product, its market position, and the customer workflows it sits in.
Define the architecture: the Nametag-side APIs required, the target-side calls, the deployment and configuration model.
Produce specs engineering can build from — API design, integration spec, build milestones — and partner with design on admin console and setup experiences.
Write the customer-facing setup and admin documentation, or the source material for it.
Drive the roadmap for the integration surface
Turn customer demand, sales signal, and partnership context into a prioritized, defensible build order.
Own the marketplace and listing path for each platform, including the business and technical requirements that gate it.
Track what shipped, what adoption looks like, and what the next integration should learn from the last one.
Partner across Nametag
Work with Engineering through build and launch, staying close enough to help resolve design questions as they surface.
Partner with Go-to-Market on positioning, enablement, and the technical conversations that close enterprise deals.
Work with partnerships on the relationships that unlock listings and co-selling.
Push the AI-forward practice
Use agent tooling to compress research, spec writing, and documentation, and build repeatable workflows rather than one-off prompts.
Treat the output as yours. You're accountable for whether an integration plan is correct, not for how fast it was drafted.
Improve the shared playbook so the next connector is faster than the last.
Work authorization required: Applicants must be legally authorized to work in the United States for any employer without current or future need for visa sponsorship.
You do not need to match every bullet. We care most about breadth, pragmatism, and comfort working against systems you don't control.
Nametag is a founding member of the Open Imperative and is committed to pay equity in technology. Final compensation is based on role, level, skills, experience, and education. Your recruiter or hiring manager can share more during the process.
Nametag is a remote-first team with regular in-person time to stay connected.
