Back to Details

it-role-expert

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

IT Role Expert

IT 岗位专家

Overview

概述

This skill provides concise, role-specific guidance for 26+ IT company positions. Each role has a reference file with responsibilities, technical knowledge, decision-making frameworks, and best practices.
When to use: Responding as a specific role, providing role-specific advice, understanding role priorities and workflows, or when general professional judgment is needed (use General Colleague).
此 skill 为 26+ 个 IT 公司岗位提供简洁且针对具体角色的指导。每个角色都有一个参考文件，其中包含职责、技术知识、决策框架和最佳实践。
何时使用：以特定角色身份作答、提供角色专属建议、了解角色优先级和工作流，或需要通用专业判断时（使用 General Colleague）。

Available Roles (26 total)

可用角色（共 26 个）

Engineering (8 roles)

工程（8 个角色）

  • Frontend Engineer - UI development, performance, accessibility, browser compatibility
  • Backend Engineer - APIs, databases, scalability, security, server-side logic
  • DevOps Engineer - CI/CD, infrastructure as code, monitoring, reliability, cloud
  • Data Engineer - Data pipelines, ETL/ELT, data quality, warehouses
  • Mobile Engineer - iOS/Android native or cross-platform apps
  • QA Engineer - Testing strategy, automation, quality assurance
  • Security Engineer - Security assessments, vulnerability management, compliance
  • AI Engineer (ML Engineer) - Production ML systems, MLOps, model deployment, optimization
  • 前端工程师 - UI 开发、性能、可访问性、浏览器兼容性
  • 后端工程师 - API、数据库、可扩展性、安全性、服务端逻辑
  • DevOps 工程师 - CI/CD、基础设施即代码、监控、可靠性、云服务
  • 数据工程师 - 数据管道、ETL/ELT、数据质量、数据仓库
  • 移动端工程师 - iOS/Android 原生应用或跨平台应用
  • QA 工程师 - 测试策略、自动化、质量保障
  • 安全工程师 - 安全评估、漏洞管理、合规
  • AI 工程师（ML 工程师） - 生产级 ML 系统、MLOps、模型部署、优化

Product & Design (4 roles)

产品与设计（4 个角色）

  • Product Manager - Strategy, roadmaps, prioritization, metrics, requirements
  • UX Designer - User research, wireframes, prototypes, usability testing
  • UI Designer - Visual design, design systems, branding, iconography
  • Product Designer - End-to-end design (UX + UI combined)
  • 产品经理 - 战略、路线图、优先级排序、指标、需求
  • UX 设计师 - 用户研究、线框图、原型、可用性测试
  • UI 设计师 - 视觉设计、设计系统、品牌、图标设计
  • 产品设计师 - 端到端设计（UX + UI 相结合）

Data & Analytics (2 roles)

数据与分析（2 个角色）

  • Data Analyst - SQL, visualization, statistical analysis, dashboards, A/B testing
  • Data Scientist - Machine learning, predictive modeling, feature engineering, deployment
  • 数据分析师 - SQL、可视化、统计分析、仪表板、A/B 测试
  • 数据科学家 - 机器学习、预测建模、特征工程、部署

Marketing & Sales (4 roles)

营销与销售（4 个角色）

  • Marketing Manager - Campaign management, multi-channel strategy, metrics, budget
  • Content Marketer - Content creation, SEO, distribution, engagement
  • Growth Marketer - Rapid experimentation, funnel optimization, viral growth
  • Sales (Account Executive) - Lead qualification, demos, closing deals, consultative selling
  • 营销经理 - 活动管理、多渠道策略、指标、预算
  • 内容营销人员 - 内容创作、SEO、分发、互动
  • 增长营销人员 - 快速实验、漏斗优化、病毒式增长
  • 销售（客户经理） - 销售线索筛选、演示、成交、顾问式销售

Operations (2 roles)

运营（2 个角色）

  • Customer Success Manager - Onboarding, retention, expansion, customer health
  • Operations Manager - Process optimization, resource allocation, vendor management
  • 客户成功经理 - 入门引导、留存、增购、客户健康度
  • 运营经理 - 流程优化、资源分配、供应商管理

HR & Admin (2 roles)

HR 与行政（2 个角色）

  • HR Manager - Recruitment, performance, compensation, compliance, culture
  • Recruiter - Sourcing, screening, candidate experience, hiring efficiency
  • HR 经理 - 招聘、绩效、薪酬、合规、企业文化
  • 招聘人员 - 人才寻访、筛选、候选人体验、招聘效率

Finance & Legal (2 roles)

财务与法务（2 个角色）

  • Legal Counsel - Contracts, compliance, IP protection, data privacy, risk management
  • Finance Manager - FP&A, budgeting, forecasting, financial reporting, cash flow
  • 法律顾问 - 合同、合规、IP 保护、数据隐私、风险管理
  • 财务经理 - FP&A、预算、预测、财务报告、现金流

Leadership (2 roles)

领导力（2 个角色）

  • CEO - Vision, strategy, fundraising, board management, culture, stakeholder communication
  • CTO - Technology strategy, engineering leadership, architecture, technical hiring
  • CEO - 愿景、战略、融资、董事会管理、企业文化、利益相关者沟通
  • CTO - 技术战略、工程领导力、架构、技术招聘

Academic (1 role)

学术（1 个角色）

  • Research Paper Writer - Academic writing, paper structure, methodology, peer review
  • 学术论文撰写者 - 学术写作、论文结构、方法论、同行评审

General (1 role) - DEFAULT

通用（1 个角色）- 默认项

  • General Colleague - Use when no specialized expertise is needed. Applies general professional skills, common sense, and cross-functional awareness. The default fallback for general workplace scenarios.
  • General Colleague - 无需专业专长时使用。适用于通用专业技能、常识和跨职能意识，是一般职场场景的默认回退选项。

Usage Instructions

使用说明

Step 1: Identify the appropriate role based on the query or user's request.
Step 2: Read the corresponding reference file in 
references/[category]/[role].md
Step 3: Apply the role's knowledge, decision frameworks, and best practices to formulate the response.
Examples:
  • "How should we prioritize these features?" → Read 
    product-design/product-manager.md
  • "Act as a frontend engineer and review this code" → Read 
    engineering/frontend-engineer.md
  • "What should our hiring process look like?" → Read 
    hr-admin/hr-manager.md
  • "Help me draft this vendor contract" → Read 
    finance-legal/legal-counsel.md
  • "Help me write the introduction for my research paper" → Read 
    academic/research-paper-writer.md
  • "General advice on workplace communication" → Read 
    general/general-colleague.md
第 1 步：根据查询或用户请求确定合适的角色。
第 2 步：读取 
references/[category]/[role].md
中对应的参考文件。
第 3 步：应用该角色的知识、决策框架和最佳实践来制定回复。
示例：
  • “我们应该如何确定这些功能的优先级？” → 读取 
    product-design/product-manager.md
  • “扮演前端工程师并审查此代码” → 读取 
    engineering/frontend-engineer.md
  • “我们的招聘流程应该是什么样的？” → 读取 
    hr-admin/hr-manager.md
  • “帮助我起草这份供应商合同” → 读取 
    finance-legal/legal-counsel.md
  • “帮助我撰写研究论文的引言” → 读取 
    academic/research-paper-writer.md
  • “有关职场沟通的通用建议” → 读取 
    general/general-colleague.md

Reference File Locations

参考文件位置

references/
├── engineering/
│   ├── frontend-engineer.md
│   ├── backend-engineer.md
│   ├── devops-engineer.md
│   ├── data-engineer.md
│   ├── mobile-engineer.md
│   ├── qa-engineer.md
│   ├── security-engineer.md
│   └── ai-engineer.md
├── product-design/
│   ├── product-manager.md
│   ├── ux-designer.md
│   ├── ui-designer.md
│   └── product-designer.md
├── data-analytics/
│   ├── data-analyst.md
│   └── data-scientist.md
├── marketing-sales/
│   ├── marketing-manager.md
│   ├── content-marketer.md
│   ├── growth-marketer.md
│   └── sales.md
├── operations/
│   ├── customer-success.md
│   └── operations-manager.md
├── hr-admin/
│   ├── hr-manager.md
│   └── recruiter.md
├── finance-legal/
│   ├── legal-counsel.md
│   └── finance-manager.md
├── leadership/
│   ├── ceo.md
│   └── cto.md
├── academic/
│   └── research-paper-writer.md
└── general/
    └── general-colleague.md (DEFAULT)
references/
├── engineering/
│   ├── frontend-engineer.md
│   ├── backend-engineer.md
│   ├── devops-engineer.md
│   ├── data-engineer.md
│   ├── mobile-engineer.md
│   ├── qa-engineer.md
│   ├── security-engineer.md
│   └── ai-engineer.md
├── product-design/
│   ├── product-manager.md
│   ├── ux-designer.md
│   ├── ui-designer.md
│   └── product-designer.md
├── data-analytics/
│   ├── data-analyst.md
│   └── data-scientist.md
├── marketing-sales/
│   ├── marketing-manager.md
│   ├── content-marketer.md
│   ├── growth-marketer.md
│   └── sales.md
├── operations/
│   ├── customer-success.md
│   └── operations-manager.md
├── hr-admin/
│   ├── hr-manager.md
│   └── recruiter.md
├── finance-legal/
│   ├── legal-counsel.md
│   └── finance-manager.md
├── leadership/
│   ├── ceo.md
│   └── cto.md
├── academic/
│   └── research-paper-writer.md
└── general/
    └── general-colleague.md (DEFAULT)

Important Notes

重要说明

  • Focus on expertise, not persona: Provides professional knowledge and decision-making frameworks, not communication styles or tone
  • Multiple roles may apply: Some questions benefit from multiple perspectives (e.g., PM + UX for product design)
  • General Colleague as default: When no specialized expertise is needed, use the General Colleague perspective for practical, common-sense guidance
  • Adapt to context: Apply role knowledge to specific situations and constraints
  • Cross-functional awareness: Understand how roles interact and their different priorities
  • 专注于专业能力，而非角色扮演：提供专业知识和决策框架，而非沟通风格或语气
  • 可能适用多个角色：某些问题受益于多个视角（例如，产品设计中的 PM + UX）
  • 以 General Colleague 为默认项：无需专业专长时，使用 General Colleague 视角提供实用且符合常识的建议
  • 适应具体情境：根据具体场景和约束应用角色知识
  • 跨职能意识：理解角色之间的协作方式及其不同的优先级