Skip to main content

Tailscale

Customer Reliability Engineer

  • Confirmed live in the last 24 hours
  • $115k–$144k
  • Mid level
  • Remote (United States)
  • 4+ yrs exp
  • Added 2 months ago

About this role

Tailscale is seeking a Customer Reliability Engineer to tackle complex, ambiguous customer escalations and bridge the gap between customer issues and engineering solutions. This role involves in-depth investigations, clear communication with customers and internal teams, and the creation of detailed handoff packages for engineering. If you enjoy problem-solving and have a strong technical background in networking and SaaS environments, this is an excellent opportunity.

What you'll do

  • Manage high-severity customer escalations from start to finish.
  • Investigate issues, reproduce bugs, and communicate with customers.
  • Create comprehensive engineering handoff packages with reproducible cases and evidence.
  • File and track issues, ensuring engineering has full customer context.
  • Identify recurring issues and propose product improvements/tooling.
  • Collaborate with Support, Customer Success, and Engineering teams.

What they're looking for

  • Networking (TCP/IP, DNS, firewalls, VPNs)
  • Overlay Networking (WireGuard, STUN)
  • Go programming
  • Linux, macOS, Windows systems administration
  • Troubleshooting
  • Packet Analysis
  • Cloud Infrastructure (IaaS, CI/CD, Kubernetes)
  • Python

Benefits

  • Remote-first environment
  • Competitive total compensation (salary, equity, commission)
  • Comprehensive group benefits (health, vision, dental)
  • Employer-funded retirement contributions
  • Company retreats and team off-sites
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

Tailscale

View all jobs at Tailscale

Likely interview questions

  • Describe a particularly challenging customer escalation you handled. What was your approach, and what was the outcome?
  • Explain a time you had to communicate a complex technical issue to a non-technical stakeholder. How did you ensure understanding?