About the role
About Clipboard Our mission is to uplift as many communities as possible. We do this through our app-based marketplace that connects healthcare professionals with the workplaces that need amazing workers. This enables hundreds of thousands of people to achieve financial stability for themselves and their families while providing essential care to millions of people across the U.S. Founded in 2016, we are a remote-first team of over 1,000 people building a top Y-Combinator company and have been profitable since 2022. We’re the leader in Long-Term Care staffing and are rapidly expanding into Home Health, Hospitals, and more, meaning we have more work to do than people to do it, and are growing our team to support millions more people and their communities. Overview 📍 Remote Global - Non U.S. Want to sit at the intersection of Support, Engineering, and Product? Clipboard is hiring Technical Support Engineers (TSEs) to act as the primary escalation layer for technical issues across our platform. You'll own the investigation, reproduction, and - where applicable- agent-assisted fix implementation that turns noisy customer reports into validated, high-signal work, so Engineering only receives production-ready problems for final review. This is a hands-on, high-ownership role for people who love digging into hard problems with real diagnostic tools, who care about getting to the root cause rather than just clearing a queue, and who want their investigations to directly protect platform reliability for hundreds of thousands of healthcare workers and the facilities that depend on them.
What You'll Do Monitor escalation channels and the Technical Support queue in Zendesk, catching early signals of systemic problems before they reach customers Investigate complex product, platform, and data-layer issues using tools like Datadog, internal dashboards, and SQL, reproducing bugs and producing evidence-backed escalations to Engineering. Handle live incidents end-to-end, from detection to closure: React to an incident with urgency, coordinate across Support, Engineering, and Product, and keep stakeholders updated with clear, structured communication Implement fixes where appropriate, testing your changes before handing off to Engineering for final review and sign-off Perform Root Cause Analysis and post-incident reviews, translating each issue into learnings that reduce recurrence and improve monitoring Maintain operational workflows (geofence, facility quizzes, NFC) accurately and quickly while spotting trends for prevention Capture investigative learnings in clear troubleshooting guides and documentation, and submit structured proposals that turn recurring patterns into actionable improvements Uphold our values such as unreasonably fast, ownership, and uncomfortably high standards in every interaction Who We're Looking For Technical Fluency - You're comfortable investigating issues with observability tools (e.g., Datadog), writing SQL to interrogate data, and reasoning about APIs, backend configurations, and feature toggles. You can tell the difference between a UI, data, and code-level problem. Diagnostic Rigor - Every investigation you produce is thorough, evidence-based, and reproducible. You rule out config and data causes before escalating, and your write-ups are clear enough for another engineer to pick up without rework. End-to-End Ownership - You own problems from first report to confirmed resolution, including stakeholder updates and follow-through, with no gaps between hand-offs. Composure Under Pressure - You stay structured and calm during live incidents, balancing speed with accuracy and communicating clearly when stakes are high. Adaptability & Prioritization - You juggle structured work (incidents, bugs, workflows) with unplanned high-priority requests without letting SLAs slip. Systems & Prevention Thinking - You treat every issue as a chance to learn, identifying gaps in monitoring, tooling, or process and proposing fixes that prevent recurrence. Fluent, professional-level English communication, both written and verbal.
