# Director of Technical Support Engineering at GrowthLoop

> Remote · North America · Director+ · Other · open. Source: https://alderhq.app/jobs/greenhouse%3Agrowthloop%3A4752922005 (read 2026-11-09).

## Facts (observed)

- Company: [GrowthLoop](https://alderhq.app/companies/growthloop)
- Location text: North America, Remote ; Remote
- Where it can be done from (inferred): Remote · North America (evidence: "Location: North America, Remote ; Remote")
- Posted: 2026-11-09 (0 days ago)
- First seen by alder: 2026-11-09 · last verified: 2026-11-09
- Reposted: 0 times · edited: 0 times
- Apply on the employer's site: https://job-boards.greenhouse.io/growthloop/jobs/4752922005
- Skills listed (inferred): SQL

## Pay and sponsorship

- Posted pay: not posted

## Description (the employer's text)

### Director of Technical Support Engineering

Customer Solutions Group \| North America

Come help us reimagine GrowthLoop’s technical support function from the ground up. You’ll own the customer support experience end to end, from the moment an issue comes in to the moment the customer confirms it’s fixed. You’ll build and coach a strong team of technical support engineers, and you’ll design AI native systems that get smarter the more they’re used.

You’ll report directly to the VP of the Customer Solutions Group and lead the Technical Support function within CSG, working closely with Product and Engineering. This is a hands-on leadership role. You’ll set the direction, and you’ll also dig into the hardest issues yourself, build tooling, and coach your team through the work.

### What You Will Do

### Build and Lead Technical Support Engineering

- Recruit, develop and lead technical support engineers who can investigate and solve problems independently. Set a high bar for SQL, APIs, debugging and cloud data systems. Stay hands-on in complex cases.
- Build a distributed team, with initial expansion focused on India. Use workload, comparable industry benchmarks and unit economics to recommend staffing, hiring models and sustainable coverage while retaining ownership of quality and customer outcomes.
### Build an AI Native Support Organization

- Build AI-assisted intake, triage, investigation and diagnostics connected to approved knowledge, logs, telemetry and authorized customer context. Enable AI agents to manage workflows, maintain knowledge and propose improvements, working toward safe, self-healing support systems.
- Evaluate against real support cases before deployment. Define permissions, privacy controls, human approval for system changes and clear escalation to human incident response. Expand automation when it improves verified resolution, quality and productivity.
### Own the End to End Support Experience

- Own intake, prioritization, technical investigation, escalation, resolution and customer communication. Establish clear L1, L2 and Engineering handoffs, and define boundaries with Services, and Customer Architects for implementation and advisory requests. Ensure every issue has a clear owner and customers retain continuity through each handoff.
- Own service levels against customer commitments, including reliable 24/7 critical incident response. Build sustainable on-call rotations across Support and Engineering with clear severity thresholds, escalation paths, handoffs, backup coverage and recovery time after overnight incidents.
- Track response, resolution, SLA attainment and team workload so coverage meets customer needs without depending on any individual’s continuous availability.
### Build Knowledge Tooling and Automation

- Overhaul customer documentation and internal knowledge as part of the support system. Manage knowledge sources and runbooks in GitHub, own review and publishing standards, and validate workflows with Product and Engineering before guidance is published.
- Turn investigations into reusable knowledge, diagnostic scripts and tools. Improve visibility into customer workloads, integrations and infrastructure so recurring issues become easier to diagnose or are eliminated. Make documentation and automation part of the team's daily work.
### Partner Deeply with Engineering and Product

- Partner with Engineering to establish shared escalation ownership, response expectations and a clear path for stalled issues. Reduce unnecessary Engineering interruptions through independent investigation and reproducible escalations, while maintaining joint accountability for incident response, root cause analysis and permanent fixes.
- Bring support trends by product area into customer and product discussions. Route internal technical questions through a clear support path, validate answers, and partner on reliability, observability, diagnosability and customer self-service.
### What You Bring

### Required Experience

- A proven record of building or transforming technical support, hiring and coaching distributed technical support engineers, and owning customer outcomes end to end while staying active in investigations.

---
Data: alder (https://alderhq.app). Cite https://alderhq.app/jobs/greenhouse%3Agrowthloop%3A4752922005 and the date you read it. Observed facts come from the employer's own listing; location reach, level, family and skills are inferences.
