Developer Relations Engineer

Tailscale is building the new Internet by delivering software that makes it easy to securely interconnect people and their devices. They are seeking a Developer Relations Engineer to enhance the developer experience across Tailscale’s product portfolio, helping developers understand and build with their core VPN/connectivity product while contributing to the evolution of new product areas.

Responsibilities:

• Build and maintain demos, sample apps, reference architectures, tutorials, and technical tools that help developers understand what they can do with Tailscale
• Create technical content for developers, including blog posts, docs, videos, talks, workshops, livestreams, and conference sessions
• Represent Tailscale at events, conferences, meetups, community moments, and developer-facing conversations
• Work closely with engineering, product, marketing, support, and community teams to identify developer friction and turn that feedback into better product experiences
• Help developers understand Tailscale’s core connectivity product, as well as newer product areas such as secure AI access, privileged access management, identity, infrastructure security, and developer tooling
• Contribute to open source projects, examples, and integrations where it makes sense
• Participate in public technical conversations through GitHub issues, pull requests, community forums, social channels, and other developer feedback loops
• Help define what great developer experience looks like at Tailscale, from first touch to production usage

Requirements:

• Strong software engineering background, with demonstrable experience building, debugging, and shipping real projects
• Ability to write clear, useful code samples, demos, tutorials, and technical content for developer audiences
• Deep curiosity about how systems work, especially across networking, infrastructure, security, identity, cloud, open source, or developer tooling
• Excellent written and verbal communication skills, with the ability to explain complex technical ideas clearly and creatively
• Experience speaking to technical audiences, whether through conferences, meetups, livestreams, workshops, podcasts, videos, or internal engineering forums
• Comfortable working in public via GitHub issues, pull requests, community forums, social channels, open source projects, and developer feedback loops
• Strong developer empathy, emotional intelligence, and product sense. You notice friction, understand why it matters, and can help turn that insight into better docs, APIs, examples, workflows, and product experiences
• Ability to work cross-functionally with engineering, product, marketing, support, community, and other technical stakeholders
• Comfortable operating independently, choosing high-impact projects, and following them through from idea to execution
• Ability to manage multiple workstreams and meet regular publishing, event, or launch deadlines
• Comfortable presenting on stage and on camera to developer audiences
• Willingness to travel for events, conferences, and community moments
• Bachelor's degree in Computer Science, Computer Engineering, Electrical Engineering, or a related technical field, or equivalent practical experience
• Strong software engineering fundamentals, whether gained through formal education, professional experience, open source work, self-directed learning, or building ambitious projects on your own
• A track record of building and explaining technical systems. This could include production software, developer tools, infrastructure projects, open source contributions, homelab experiments, local AI setups, networking projects, or anything else that shows how you think
• If your background is less conventional, we still want to hear from you. Bring us your GitHub repos, blog posts, diagrams, configs, talks, demos, lab notes, or the deeply specific story of why your homelab is built the way it is
• Comfort discussing technical tradeoffs in detail such as explaining what you built, why you built it, what broke, what you learned, and what you would do differently next time
• Experience with Go, networking, VPNs, WireGuard, identity, access controls, infrastructure automation, or security products
• Experience building developer education programs, sample apps, workshops, technical video content, or conference talks
• A visible history of technical writing, talks, demos, open source contributions, or community work
• Experience with homelabs, self-hosting, local AI models, infrastructure experiments, or other 'I wanted to understand how this works, so I built it' projects
• Familiarity with secure AI access, privileged access management, zero trust, or modern infrastructure security patterns
• Familiarity with open source contribution workflows and technical collaboration in public