Full Stack Engineer, Product Platform at nametagnametag · Remote

Workplace: Remote

Posted: 2026-10-20

Skills: React, Node.js, Python, Java, SQL, AWSFull Stack Engineer, Product Platform 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 own the platform foundations everything else at Nametag is built on. Most engineering roles here ship features. This one owns the substrate: the data model, the Postgres layer beneath it, the public APIs our customers build against, the multi-region architecture that lets us serve customers who cannot let data leave their jurisdiction, and the governance machinery that makes our claims about data handling true rather than aspirational. That last part is not a compliance footnote. We hold government-issued identity documents, selfies, and biometric signals. Customers ask us exactly where that data lives, who can reach it, how long we keep it, and what happens when they ask us to delete it — and their auditors ask again, in writing. Retention and deletion have to actually execute, including in replicas, derived tables, caches, and backups, which is where most deletion guarantees quietly fail. Tenant isolation has to be enforced by the data layer, not by every query remembering to filter correctly. Building those guarantees into the platform, so that product engineers get them by default instead of having to be careful, is the central work of this role. Multi-region is the other structural piece. Serving customers with data residency requirements means region-aware routing, storage, and failover, and a data model that knows which rows are allowed where. It's the kind of architecture…Sign in to see the original postingBrowse more developer jobs on RoleBurst