support-engineer

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Support Engineer

技术支持工程师

When to Use

适用场景

Investigate a customer bug or "it doesn't work" report
Reproduce issues across environments (browser, API, mobile)
Analyze logs, request IDs, and HTTP/API error payloads
Draft technical response with steps, workaround, or ETA
Escalate to engineering with minimal repro and impact
Author or update KB articles after resolved issues

调查客户反馈的产品缺陷或"无法正常工作"问题
在多环境（浏览器、API、移动端）复现问题
分析日志、请求ID和HTTP/API错误负载
撰写包含步骤、临时解决方案或预计修复时间的技术回复
向工程团队提交包含最简复现步骤和影响范围的问题升级申请
问题解决后撰写或更新知识库（KB）文章

When NOT to Use

不适用场景

Support queue SLAs, CS metrics, renewals, dunning →
```
customer-ops-specialist
```
Company-wide outage incident commander role →
```
incident-management-engineer
```
Implement product code fixes in repo →
```
fullstack-software-engineer
```
Public API reference documentation →
```
tech-writer-researcher
```
Security incident or SOC alert investigation →
```
defensive-security-analyst
```

支持队列服务水平协议（SLA）、客户成功指标、续约、催缴等 →
```
customer-ops-specialist
```
公司级 outage 事件指挥角色 →
```
incident-management-engineer
```
在代码仓库中实现产品代码修复 →
```
fullstack-software-engineer
```
公共API参考文档编写 →
```
tech-writer-researcher
```
安全事件或SOC告警调查 →
```
defensive-security-analyst
```

Related skills

Need	Skill
Support ops, health scores, billing tickets	`customer-ops-specialist`
App code fixes and PRs	`fullstack-software-engineer`
Browser auth, CORS, session issues	`web-application-developer`
Production outage process	`incident-management-engineer`
Customer-facing docs and API guides	`tech-writer-researcher`
Infra/logs on platform side	`devops`
Company-wide incident or launch messaging	`communication-lead`
Exec/VIP and public community escalation program	`community-executive-escalations-program-manager`
How-to replies, KB gaps, feature-request capture	`product-support-specialist`

需求	技能
支持运营、健康评分、计费工单	`customer-ops-specialist`
应用代码修复与PR提交	`fullstack-software-engineer`
浏览器认证、CORS、会话问题	`web-application-developer`
生产故障处理流程	`incident-management-engineer`
面向客户的文档与API指南	`tech-writer-researcher`
平台侧基础设施/日志处理	`devops`
公司级事件或发布消息撰写	`communication-lead`
高管/VIP与公共社区升级方案	`community-executive-escalations-program-manager`
操作指引回复、知识库补充、功能需求收集	`product-support-specialist`

Core Workflows

核心工作流程

1. Intake and triage

1. 工单接收与分流

Capture before deep dive:

Customer ID, environment (prod/sandbox), region
Timestamp with timezone
User role and exact URL or API endpoint
Error message verbatim; request/correlation ID
Recent changes (release, config, integration)
Severity: blocked vs degraded vs question

Route billing/access-only issues to

customer-ops-specialist

if non-technical.

See
references/ticket_triage.md
.

深入排查前需收集以下信息：

客户ID、环境（生产/沙箱）、区域
带时区的时间戳
用户角色及具体URL或API端点
完整错误信息；请求/关联ID
近期变更（版本发布、配置调整、集成改动）
严重程度：阻塞、性能下降或咨询类问题

若为非技术类的计费/权限问题，转至

customer-ops-specialist

处理。

参考文档：
references/ticket_triage.md

2. Reproduce

2. 问题复现

Follow customer steps on comparable environment
Reduce to minimal repro (fewest steps, clean account if possible)
Note deterministic vs intermittent
Capture HAR, server logs, or curl with redacted secrets

See
references/reproduction_debugging.md
.

在相似环境中按照客户步骤操作
简化为最简复现步骤（最少操作步骤，尽可能使用干净账号）
记录问题是确定性出现还是间歇性出现
捕获HAR文件、服务器日志或已脱敏密钥的curl命令

参考文档：
references/reproduction_debugging.md

3. Isolate root cause

3. 根因定位

Layer	Checks
Client	Browser, cache, extensions, version
API	Status code, body, rate limits, auth token
Config	Feature flags, tenant settings, quotas
Data	Specific record IDs, permissions
Platform	Status page, known incidents

Document hypothesis and evidence; avoid guessing in customer reply.

层级	检查项
客户端	浏览器、缓存、扩展程序、版本
API	状态码、响应体、速率限制、认证令牌
配置	功能开关、租户设置、配额
数据	特定记录ID、权限
平台	状态页面、已知事件

记录假设与证据；在给客户的回复中避免猜测。

4. Resolve or escalate

4. 问题解决或升级

If known issue: link KB, workaround, linked engineering ticket + ETA.

If new bug: file engineering ticket with:

Title:
```
[component] short failure description
```
Impact: customer count, blocked workflows
Repro steps, expected vs actual
Logs/IDs attached

See
references/escalation_engineering.md
.

若为已知问题： 链接知识库文章、临时解决方案、关联的工程工单及预计修复时间。

若为新缺陷： 提交工程工单，包含：

标题：
```
[组件] 简短故障描述
```
影响范围：受影响客户数量、阻塞的工作流程
复现步骤、预期结果 vs 实际结果
附件：日志/ID

参考文档：
references/escalation_engineering.md

5. Customer communication

5. 客户沟通

Acknowledge impact; no blame
State what is known, unknown, and next update time
Provide workaround before permanent fix when possible
After fix: confirm with customer; close loop

See
references/customer_comms.md
.

确认问题影响；避免推诿责任
说明已知信息、未知信息及下次更新时间
若可能，在永久修复前提供临时解决方案
修复完成后：与客户确认，闭环问题

参考文档：
references/customer_comms.md

6. Knowledge base

6. 知识库维护

After fix verified:

Symptom → cause → resolution → prevention
Searchable title; tags for product area
Link to public API doc if applicable

See
references/kb_article.md
.

问题修复验证完成后：

按照"症状 → 原因 → 解决方案 → 预防措施"结构撰写
标题需便于搜索；添加产品领域标签
若适用，链接至公共API文档

参考文档：
references/kb_article.md

When to load references

参考文档加载场景

Priority and intake →
```
references/ticket_triage.md
```
Repro and logs →
```
references/reproduction_debugging.md
```
Engineering handoff →
```
references/escalation_engineering.md
```
Customer updates →
```
references/customer_comms.md
```
KB template →
```
references/kb_article.md
```

优先级与工单分流 →
```
references/ticket_triage.md
```
复现与日志分析 →
```
references/reproduction_debugging.md
```
工程交接 →
```
references/escalation_engineering.md
```
客户更新 →
```
references/customer_comms.md
```
知识库模板 →
```
references/kb_article.md
```