Full Stack Engineer, Integrations

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 are looking for a Full Stack Engineer to build the integrations that put Nametag inside the systems our customers already use.

Nametag is rarely the application someone opens. It's the identity check that happens inside a helpdesk ticket, an HR onboarding flow, or a Slack message from someone claiming to be the CFO. Our reach is determined by how well we embed into Workday, Service Now, Slack, Okta, ICIMS, UKG, and the long tail behind them — and that embedding is engineering work.

This is a full stack role with an unusual center of gravity. You'll write backend services and APIs on our side, configuration and setup experiences in our console, and the connector code that talks to a dozen platforms that each made different decisions about authentication, extensibility, and what a webhook means. You'll join a dedicated team whose purpose is expanding Nametag into new systems and new use cases.

What makes this work interesting is that you're building into environments you don't control and can't change. Every target platform has its own auth model, its own rate limits, its own review process, and its own idea of how much UI you're allowed. Workday's extensibility surface is narrow and governed. Slack gives you modals and Block Kit, which were not designed for identity verification.

Service Now gives you enough rope to break a customer's upgrade path. Designing something that is secure, usable, and actually buildable inside those limits — and that keeps working when the vendor ships a change you didn't ask for — is the core of the job.

The breadth is real. You'll be reading someone else's API documentation most weeks, and debugging behavior that documentation doesn't describe. Engineers who like going deep on one system for a year will be unhappy here. Engineers who like landing in an unfamiliar platform and having it figured out by Thursday will do well.

You'll work closely with the product manager for integrations, who owns how each integration should work, and you'll have real influence over that design because you're the one who knows what the platform will actually permit.

Build integrations end to end

Design and build connectors into third-party enterprise platforms: authentication, data flow, event handling, and the verification experience inside the host application.

Build the Nametag-side APIs, services, and webhooks each integration depends on.

Build the console configuration and setup experience customers use to install and operate the integration.

Take integrations through marketplace and app review processes, including the requirements that gate a listing.

Work across unfamiliar platforms

Get productive fast in APIs and extensibility models you haven't seen before, and develop real expertise in the ones that matter most.

Implement against OAuth, OIDC, SAML, SCIM, and whatever a given platform does instead of those.

Handle the operational reality of depending on other people's systems: rate limits, partial outages, breaking changes, and undocumented behavior.

Own reliability across the fleet

Operate what you build. Integrations fail in production in ways that are specific to one customer's configuration, and you'll be the one who figures…