客户技术支持负责人 客户服务部门 - 远程
Customer Tech Care Lead Customer Care Department - Remote
StellarTech正在构建一个客户技术关怀团队——一个嵌入在客户支持部门的专业工程小组,其唯一目的是技术性地解决所有无法由普通支持人员解决的用户问题。作为负责人,你将担任技术权威和组织核心:处理升级的工单,指导自动化工程师团队,与产品和基础设施工程团队协调,并亲自设计或批准每一个发布的解决方案。
这并不是一个传统的支持负责人职位。你将大部分时间花在系统上——查询数据库、在测试环境中复现错误、阅读日志、设计自动化流程,并评估大语言模型代理。你是支持团队所观察到的问题与工程团队所构建解决方案之间的桥梁。
你将负责:
1. 团队领导与团队运营
• 负责日常运营:容量规划、冲刺结构、任务分配和质量标准。
• 指导和培养自动化工程师;定义代码和架构评审流程。
• 建立并跟踪团队KPI:工单回避率、自动化覆盖比例、重复问题预防。
• 向管理层汇报团队表现;根据数据提出人员和工具投资建议。
2. 升级工单分析与技术调查
• 作为所有升级问题的主要技术入口:复现问题、定位根本原因、确定解决路径。
• 访问生产/测试系统、内部仪表盘和数据库(SQL/NoSQL)直接进行问题调查。
• 分析日志、事件流、支付记录、订阅状态和用户旅程数据。
• 主导诊断流程,确保团队成员遵循结构化的调查手册。
3. 自动化解决方案架构
• 设计并监督自动化解决方案,以无需人工干预的方式解决重复性问题。
• 构建跨Zendesk触发器、内部API调用和数据库状态变化的多步骤流程。
• 定义解决方案分类(宏、API、LLM代理、数据库脚本),并在整个团队中执行。
• 在生产部署前批准所有自动化流程;严格执行回滚和监控标准。
4. 大语言模型与AI代理交付
• 领导设计和部署基于大语言模型的代理,能够自主诊断和解决问题。
• 定义代理架构用于上下文注入:用户资料、订阅状态、事件、从数据库中的工单历史。
• 监督训练循环质量:收集和标注高质量数据,优化模型性能。
查看英文原文
StellarTech is building a Customer Tech Care unit - a specialised engineering squad embedded within Customer Care, whose sole purpose is to technically resolve every user issue that cannot be solved by a standard support agent. As the Lead, you will be the technical authority and organisational backbone: triaging escalated tickets, directing your team of automation engineers, coordinating with product and infrastructure engineering, and personally architecting or approving every solution shipped.
This is not a traditional support lead role. You will spend the majority of your time in systems - querying databases, reproducing bugs in staging, reading logs, designing automation flows, and evaluating LLM agents. You are the bridge between what support teams observe and what engineering teams build.
What You’ll Do:
1. Team Leadership & Unit Operations
• Own day-to-day operation: capacity planning, sprint structure, task distribution, and quality standards.
• Mentor and grow automation engineers; define code and architecture review processes.
• Establish and track unit KPIs: ticket deflection rate, automation coverage ratio, recurrence prevention.
• Report unit performance to management; propose headcount and tooling investments backed by data.
2. Escalation Triage & Technical Investigation
• Serve as the primary technical intake point for all escalated issues: reproduce problems, isolate root causes, scope resolution paths.
• Access production/staging systems, internal dashboards, and databases (SQL/NoSQL) to investigate issues directly.
• Analyse logs, event streams, payment records, subscription states, and user journey data.
• Own the diagnostic protocol and ensure team members follow structured investigation runbooks.
3. Automation Solution Architecture
• Design and oversee automation solutions that resolve recurring issue categories without human intervention.
• Architect multi-step pipelines spanning Zendesk triggers, internal API calls, and database state changes.
• Define the solution taxonomy (macro vs. API vs. LLM agent vs. DB script) and enforce it across the team.
• Approve all automation flows before production deployment; enforce rollback and monitoring standards.
4. LLM & AI Agent Delivery
• Lead design and deployment of LLM-based agents capable of diagnosing and resolving issues autonomously.
• Define agent architecture for context injection: user profile, subscription state, events, ticket history from DB.
• Oversee training loop quality: curate high-quality resolved tickets to improve agent accuracy.
• Evaluate agent performance quantitatively; own escalation decisions vs. further automation.
5. Engineering–Support Interface
• Act as authoritative translator between support teams (who observe symptoms) and engineering teams (who own systems).
• Maintain a shared escalation taxonomy and SLA matrix agreed with both Support Director and Engineering leads.
• Own the feedback loop: unit diagnostic output becomes the engineering bug report that ships a fix.
• Coordinate with Product, Backend Engineering, and Data teams to secure required system access and API endpoints.
6. Documentation & Knowledge Management
• Maintain a live runbook library: automation flows, escalation paths, investigation procedures.
• Ensure every automation has a documented failure mode and rollback path.
• Create onboarding materials for new automation engineers.
What We’re Looking For:
• 5+ years in automation engineering, technical support engineering, or platform engineering - with 1–2 years in a team lead or tech lead capacity.
• Demonstrated ability to investigate production issues via direct system access: logs, SQL/NoSQL databases, API responses, event streams.
• Hands-on experience building LLM-based agents or AI-driven automation (OpenAI API, function calling, embeddings, or equivalent).
• Strong Python skills; production-quality scripts for automation, data remediation, and API orchestration.
• Experience designing Zendesk automation pipelines (triggers, automations, ZAF apps) or equivalent support platforms.
• Event-driven architecture and API integration patterns (REST, webhooks, async queues).
• Track record owning support metrics: deflection rate, FCR, CSAT, time-to-resolution.
Nice to have:
• Low-code/no-code orchestration tools (n8n, Zapier, Make, Rivet) in hybrid architectures.
• B2C or subscription-based product background with high user volume and complex billing/access state.
• CI/CD pipelines and production-level monitoring for automation systems.
• Data engineering concepts: pipeline design, idempotency, retry logic, dead-letter queues.
• RAG architectures, vector databases, or knowledge-base-augmented LLM agents.
• Experience in a regulated environment (GDPR, PCI-DSS, SOC 2).
Why You'll Love Working With Us:
- Innovative Environment: We're all about trying new things and pushing the envelope in EdTech.
- We are global remote
- Health: company-provided medical expense compensation.
- AI solutions: АІ subscription and other tools.
- Balance: Flexible paid time off, you get 21 days of annual leave + 10 bank holidays.
- Collaborative Culture: Work alongside passionate professionals who are as driven as you are.
Interview Stages:
- HR Screen/Introduction
- Technical Interview
- Technical Assignment
- Final Interview
Originally posted on Himalayas