Technical Support Engineer

The Team + The Role

Pendo’s Technical Support Engineers are the diagnostic and strategic layer between customers and the product. This small, global team sits within Engineering and partners daily with Product, Engineering, and Customer Engineering across the US, EMEA, and APAC. The team does not operate like a help desk; it solves technical problems, strengthens customer outcomes, and turns customer signal into product insight.

As a Sr. Technical Support Engineer, you will own customer issues end-to-end across Pendo’s web and mobile products, from triage and debugging to resolution, documentation, and feedback loops. You will handle break/fix issues, how-to questions, configuration guidance, bug reproduction, and complex escalations while using AI tools to accelerate research, drafting, troubleshooting, and knowledge capture. At the senior level, you will also serve as a go-to technical resource for peers and contribute to the cross-functional work that makes the support function stronger.

This role is based in our Raleigh office.

What this looks like day-to-day

• Support queue ownership: You triage, diagnose, and resolve technical issues across Pendo’s web and mobile products, including break/fix, how-to, best practice, and configuration questions. You manage urgency based on customer impact and own each case until the customer’s problem is actually solved.
• Technical guidance: You provide targeted technical assistance on platform usage, configuration, and best practices for customers in your segment. Each engagement is scoped to the issue at hand, with clear resolution, documentation, and a path forward that helps the customer move independently.
• Customer signal: You translate customer pain into reproducible test cases, clear bug reports, and prioritized feedback for Product and Engineering. You also surface customer health signals and strategic gaps to Account Owners and Customer Success so the right teams can act.
• Knowledge at scale: You create and maintain internal knowledge base content so the team does not solve the same problem repeatedly. When you resolve something novel, you document it and use AI tools to draft, organize, and surface knowledge faster.
• Resolution follow-through: You work directly with developers on fixes and workarounds, pushing cases through to close without dropping hard problems or waiting to be chased. Customers and internal partners know where things stand because you communicate clearly and proactively.
• Continuous improvement: You identify recurring customer confusion, tooling gaps, workflow friction, and process issues that slow the team down. When you see a pattern, you propose the fix, write the doc, or build the internal resource that helps the team move faster.