Full Stack Engineer, Integrations

Full Stack Engineer, Integrations

Remote, US

About Nametag

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.

The Role

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, ServiceNow, 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. ServiceNow 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.

What You'll Do

• 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 out why.
• Build the observability that makes a broken integration visible to us before it's visible to the customer.
• Design for versioning and backwards compatibility. Customers do not upgrade on your schedule.
• Make each one faster than the last
• Factor shared infrastructure out of individual connectors so common patterns stop being rebuilt.
• Contribute to the tooling, scaffolding, and templates that shorten time to first working integration.
• Document how each integration works well enough that support and solutions engineers can operate without you.

What We're Looking For

• 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.
• 4+ years building and operating production software, including backend services and APIs.
• Demonstrated experience integrating with third-party APIs in production — not a one-off script, but something you owned and kept running.
• Strong backend skills in Go, Node.js, Python, Java, or similar, plus enough frontend ability to build configuration and setup UI in React or a comparable framework.
• Working knowledge of OAuth, OIDC, SAML, SCIM, webhooks, and the failure modes each brings.
• Relational database experience, PostgreSQL preferred.
• Cloud experience, AWS preferred.
• The temperament for integration work: patience with other people's documentation, and the instinct to verify rather than trust it.
• Clear communication and good judgment in a remote, cross-functional team.
• Bonus Points
• Hands-on experience with Workday, ServiceNow, Slack, Okta, Entra, ICIMS, or UKG extensibility specifically.
• Experience shipping an app through a marketplace or app review process.
• Experience with identity, authentication, account recovery, fraud prevention, or compliance-heavy products.
• Experience building an integration platform or connector framework rather than individual integrations.
• Experience in a solutions engineering, professional services, or customer-facing engineering role.

What We Value

High ownership.

You see what needs doing and do it.

Technical judgment.

You make systems simpler, safer, and easier to operate.

Speed with care.

We move quickly because attackers move quickly, but we do not cut corners on trust or security.

Kindness and integrity.

Trust starts with how we work with each other.

Remote-first, US-based team

• Quarterly team offsites
• Flexible schedules
• Meaningful equity ownership
• Comprehensive medical, dental, and vision benefits
• Flexible paid time off
• New computer hardware and equipment