Product Manager, Tailscale-Native Apps

About this role

<div class="content-intro"><p><strong>About Tailscale&nbsp;</strong></p> <p>Tailscale is building the new Internet by delivering software that makes it easy to securely interconnect people and their devices, no matter where they are. From hobbyists to multinational corporations, teams of every size use Tailscale each day to protect their networks, share access to internal tools, and more. We're building a future for the Internet that's easy, sensible, and safe, like it used to be. Founded in 2019 and fully distributed, we're backed by Accel, CRV, Insight, Heavybit, and Uncork Capital.</p></div><h3><span style="font-size: 12pt;"><strong>About the Role</strong></span></h3> <p>We're hiring a Product Manager to own what it's like to build a <strong>Tailscale-native application</strong> — software with Tailscale connectivity and identity built in from the start.</p> <p>You'd own the original front door to that world: <a href="https://tailscale.com/kb/1244/tsnet">TSNet</a>, the Go library that puts a Tailscale node inside an application in a few lines of code; <a href="https://tailscale.com/blog/tailscale-rs-rust-tsnet-library-preview">tailscale-rs</a>, our new Rust-based SDK family (including C++, Python, and Elixir); the tailscale CLI powering scripting, automation, and CI; and the core Tailscale client library.</p> <p>Products already get built this way, inside and outside Tailscale. <a href="https://tailscale.com/docs/aperture">Aperture</a>, our AI connectivity gateway, and <a href="https://tailscale.com/use-cases/pam">Tailscale PAM</a> run on these primitives. So do LM Studio, NVIDIA, and Namespace.co, who embed Tailscale directly into their applications to give their users secure remote access, reach into customer networks safely, and bridge cloud environments without VPN gymnastics. One of those teams went from zero to a working embedded integration in hours. Your job is to make that the normal outcome for thousands of more applications.</p> <p>Today this experience is engineering-led and the developer journey is uneven. The API is powerful, but the on-ramp from "I read a blog post" to "Tailscale is running inside my product" has real friction: auth key handling, onboarding flows designed for humans instead of embedded apps, docs and examples that don't yet tell a coherent story. You'll own that journey end to end and define, concretely, what it means to build a Tailscale-native application including the golden paths, the reference patterns, the APIs, and the developer experience that makes people say "wait, that's all it took?"</p> <p>You'll report to Ross Kukulinski, VP Product, and work closely with the Rust, Golang, and Clients engineering teams, plus the internal product teams and external partners building Tailscale-Native Applications.</p> <h3><span style="font-size: 12pt;"><strong>Key Responsibilities</strong></span></h3> <ul> <li>Own the roadmap for the native apps experience: TSNet, tailscale-rs, and the tailscale CLI</li> <li>Define what "Tailscale-native application" means — the reference architectures, golden paths, and embedding patterns, packaged as docs, examples, and sample apps developers can build from</li> <li>Own the developer experience end to end: the on-ramp from blog post to running embedded node, API ergonomics, error messages, docs that work, examples that compile, and upgrade paths that don't burn early adopters</li> <li>Set the Rust SDK family strategy: which TSNet capabilities to port, which to skip, in what order, and how to position the library to developers.</li> <li>Treat the CLI as a product in its own right: scripting ergonomics, output conventions, automation surfaces, and the experience for platform and SRE teams running tailscale in CI and infrastructure-as-code</li> <li>Run the internal dogfood loop. Aperture and Tailscale PAM are built on these primitives; make those teams your most demanding customers and turn their friction into roadmap.</li> <li>Partner with GTM and Customer Success on embedding deals — AI platforms, developer tools, and infrastructure software shipping Tailscale inside their products — and let what you learn set priorities</li> <li>Engage developers where they live (GitHub issues, Discord, office hours) and build a coherent picture of what embedded developers need</li> </ul> <h3><span style="font-size: 12pt;"><strong>What We Are Looking For</strong></span></h3> <ul> <li>6+ years in product management, or a software engineering background moving into product, with real time spent on a developer-facing product: an SDK, API, CLI, library, or developer tool</li> <li>You've shipped developer-facing features that developers used in production, and lived with the consequences of your design choices — naming, defaults, error behavior, versioning</li> <li>You can read Go and/or Rust and hold a credible technical conversation about API and SDK design&nbsp;</li> <li>You have taste in developer experience: opinions about API ergonomics, docs, error messages, and getting-started flows, with examples to back them up</li> <li>You do customer research the way developer products require it — reading GitHub issues, lurking in Discord, running office hours, and finding the pattern in the noise</li> <li>You turn ambiguous scope into shipped increments, close the loop after launch, and keep teams informed along the way</li> </ul> <h3><span style="font-size: 12pt;"><strong>Nice to Have</strong></span></h3> <ul> <li>Hands-on Go or Rust experience — you've built something real, even as a side project</li> <li>Time at a developer platform company with a strong SDK motion (e.g. Stripe, Twilio, Auth0, Vercel, Supabase, HashiCorp)</li> <li>Open-source community experience: contributor experience, issue triage, balancing commercial priorities with community needs</li> <li>Enough networking, zero-trust, or VPN familiarity to understand what embedding Tailscale does for a developer</li> <li>Experience designing CLIs or scripting surfaces for platform and S

View the original posting ↗