领域
Architecture & System Design
技能档案
Scalability, availability, consistency, partitioning, replication, CAP theorem
角色数
70
包含此技能的角色
级别数
5
结构化成长路径
必要要求
89
其余 257 个可选
Architecture & System Design
System Design
2026/3/17
选择当前级别并对比期望。下方卡片显示晋升所需掌握的内容。
表格展示从初级到首席的技能深度变化。点击行查看详情。
| 角色 | 必要性 | 描述 |
|---|---|---|
| 1C Developer | Understands basic architectural concepts for 1C:Enterprise systems: three-tier architecture (client-server-database), managed forms architecture, and data composition system design. Follows team architectural decisions for configuration structure and subsystem organization. | |
| AI Product Engineer | Learns basic distributed system design principles for AI products. Understands concepts of scalability, availability, and fault tolerance as applied to ML services and inference pipelines. | |
| Analytics Engineer | Studies basic system design principles applied to analytical platforms. Understands scalability, partitioning concepts, and differences between OLTP and OLAP architectures for analytical systems. | |
| Android Developer | Understands basic Android application design principles: layer separation (UI, Domain, Data), ViewModel's purpose for UI state management, Repository as a data source abstraction. Knows why multi-layer architecture is needed, understands unidirectional data flow in MVVM, draws simple application component diagrams under mentor guidance. | |
| Application Security Engineer | Understands basic system architectural components and their impact on security. Knows typical attack surfaces in client-server architectures and microservice applications. | |
| AR/VR Developer | Understands system design basics for XR applications: client-server architecture for multiplayer XR, spatial computing data flow, and real-time rendering pipeline components. Follows team architectural patterns for XR content delivery and device interaction handling. | |
| Backend Developer (C#/.NET) | Understands ASP.NET Core architecture: middleware pipeline, DI container, controller/minimal API. Knows monolith vs microservices. Designs CRUD modules. | |
| Backend Developer (Elixir) | Understands basic principles of Elixir system design: separation into contexts in Phoenix, application layers through OTP applications. Creates modular structure with supervision trees, uses Application behavior for initialization and configuration. | |
| Backend Developer (Go) | Understands basic Go system design principles: package separation by responsibility, configuration via envconfig, Go project structure following Standard Layout. Designs simple CRUD services with clear handler/service/repository separation. | |
| Backend Developer (Java/Kotlin) | Understands Spring Boot application architecture: request lifecycle, DispatcherServlet, controller → service → repository. Knows the difference between monolith and microservices. Designs simple CRUD modules. | |
| Backend Developer (Node.js) | Understands Node.js architecture: event loop, request lifecycle (middleware → handler → response), Express/Fastify request pipeline. Knows differences between monolith and microservices. | |
| Backend Developer (PHP) | Understands basic PHP application architecture: request lifecycle, routing, controllers, services, repositories. Knows the difference between monolith and microservices. Designs simple CRUD modules following project architecture. | |
| Backend Developer (Python) | 必要 | Understands client-server architecture. Knows HTTP request lifecycle. Understands basic concepts: latency, throughput, availability. Knows what a load balancer and CDN are. |
| Backend Developer (Rust) | Understands basic architectural patterns for Rust services: modular organization through workspace, layer separation (handler, service, repository). Applies dependency injection through trait objects and constructor patterns. | |
| Backend Developer (Scala) | Understands basic system design principles: client-server architecture, REST API, basic data flow in Scala application. Knows stateless/stateful service concepts, reads architectural diagrams and participates in simple component design discussions. | |
| BI Analyst | Understands basic system design concepts for contextual analysis of data architecture. Knows main data infrastructure components: source systems, ETL, warehouse, BI tools. Can describe a simple analytical system architecture: sources, storage, dashboards. | |
| Blockchain Developer | Understands basic system design concepts: latency, throughput, consistency, partitioning. Applies to blockchain context: block time, finality, state size. Draws simple architectural diagrams. | |
| Cloud Engineer | Understands basic cloud architecture concepts: VPC networking design, compute/storage/database service selection, and availability zone placement strategies. Follows team architectural decisions for cloud resource organization and landing zone patterns. | |
| Compiler Engineer | Understands basic system design concepts: components, interfaces, dependencies. Views the compiler as a system of connected modules: parser, analyzer, optimizer, code generator. | |
| Computer Vision Engineer | Understands basic system design concepts and can draw a simple CV pipeline diagram. Knows client-server architecture for inference services. | |
| Data Analyst | Understands basic system design concepts — client-server architecture, REST API, databases. Can draw a simple analytical system diagram. | |
| Data Engineer | Understands system design for data: distributed systems basics, CAP theorem, data replication. Evaluates scalability requirements. | |
| Data Scientist | Understands basic system design principles: client-server, REST API, databases. Knows how ML models integrate into production systems. Understands scalability challenges when deploying ML models and working with large data. | |
| Database Engineer / DBA | Understands basic system design concepts. Knows the database's role in application architecture: access patterns, load characteristics, consistency requirements. | |
| Desktop Developer (.NET WPF/WinUI/MAUI) | Studies basic system design principles for .NET desktop application architecture. Understands MVVM concepts, modularity and component interaction in WPF/MAUI applications with server backend. | |
| Desktop Developer (Electron/Tauri) | Understands basic system design principles in the context of Electron applications. Knows Electron main/renderer process architecture and interaction with server components. | |
| Desktop Developer (Qt/C++) | Studies basic system design principles as applied to Qt application architecture. Understands modularity concepts, separation of concerns and component interaction in desktop applications with server-side components. | |
| DevOps Engineer | Understands basic system design patterns: client-server, load balancing, caching, replication. Knows scaling fundamentals (vertical vs horizontal), understands the role of each infrastructure component in overall architecture. | |
| DevSecOps Engineer | Understands basic system design principles: modularity, separation of concerns and loose coupling. Applies these principles when creating simple DevSecOps utilities and automation scripts. | |
| Embedded Developer | Understands basic system design principles: modularity, loose coupling and separation of concerns. Applies these principles when structuring embedded applications and separating HAL from business logic. | |
| Flutter Developer | Understands basic architectural concepts of System Design Fundamentals. Follows team architectural decisions. Understands fundamental patterns. | |
| Frontend Developer (Angular) | Understands system design basics for Angular applications: component architecture, service layer patterns, and module organization. Follows team guidelines on state management approaches (NgRx/signals) and API integration patterns. Understands basic client-server interaction design. | |
| Frontend Developer (React) | Understands basic system design principles in the React frontend context. Knows how React applications interact with APIs, CDNs, caches and backend services at a high level. | |
| Frontend Developer (Svelte) | Understands basic system design concepts and can draw a simple frontend architecture diagram for a Svelte application. Knows the client-server model. | |
| Frontend Developer (Vue) | Understands client-server architecture and the frontend role in the overall system. Knows how Vue application interacts with API, CDN, load balancer and caching layers. | |
| Fullstack Developer | Understands basic fullstack application architecture: client-server model, REST API as the connecting link, relational database. Draws simple component diagrams and understands each layer's responsibility — from React component to SQL table. | |
| Game Designer | Understands basic system design concepts: client-server, databases, caching in the gaming context. Knows main online game architecture components: game server, matchmaking, persistence layer. Can describe a simple casual mobile game architecture. | |
| Game QA Engineer | Understands basic game system architecture: client-server model, game loop, main subsystems (rendering, physics, networking). Uses knowledge for more effective testing. | |
| Game Server Developer | Understands basic system design principles and client-server game architecture. Knows the roles of core components — game server, lobby server, matchmaking, persistence layer. | |
| Infrastructure Engineer | Understands basic system design principles and infrastructure components: DNS, load balancers, CDN. Knows the difference between horizontal and vertical scaling and use cases for each. | |
| iOS Developer | Understands basic iOS application design principles: layer separation (UI, business logic, data), navigation structure. Creates simple architecture with separate screens and data models, understands UIViewController and SwiftUI View lifecycle. Knows main iOS patterns: MVC, delegates, and notifications for inter-component communication. | |
| IoT Engineer | Understands basic system design concepts: client-server, abstraction layers, communication protocols. Views IoT system as a combination of devices, gateways, and cloud platform. | |
| Language Tooling Engineer | Understands basic system design principles and applies them when developing language tool components. Knows client-server interaction patterns in the LSP context. | |
| LLM Engineer | Knows system design basics: client-server, REST API, databases. Understands simple LLM application architecture: API gateway, inference server, vector database. | |
| ML Engineer | Understands basic system design principles and their application to ML infrastructure. Knows ML pipeline components: feature store, training pipeline, model registry and serving infrastructure. | |
| MLOps Engineer | Understands basic system design concepts: components, interfaces, scalability. Views the ML platform as a system of connected components: storage, pipelines, serving. | |
| Network Engineer | Understands basic system design principles — client-server, DNS, load balancing. Knows how network infrastructure components interact with each other at a high level. | |
| NLP Engineer | Understands basic system design principles and applies them when developing NLP components. Knows model-serving architecture and basic batch/online inference patterns. | |
| Penetration Testing Engineer | Understands basic system design concepts for evaluating attack surface. Can draw a simple network architecture diagram and identify entry points. | |
| Performance Testing Engineer | Understands basic system design concepts: client-server, load balancers, caches, databases. Knows how system architecture affects its performance. | |
| Platform Engineer | Understands basic platform system design principles: client-server, REST API, databases. Creates simple architecture diagrams for platform components. Understands CAP theorem and trade-offs when choosing storage. Participates in design review meetings. | |
| Product Manager | 必要 | Understands basic architectural concepts: client-server, REST API, database. Can communicate with developers using technical language. Reads architectural diagrams. |
| QA Automation Engineer | Understands basic application architecture — client-server, microservices, queues. Uses this knowledge to identify integration points and write meaningful test scenarios. | |
| QA Engineer (Manual) | Understands basic system design concepts for contextual analysis of tested application architecture. Knows main infrastructure components and their interactions relevant to testing. | |
| QA Security Engineer | Understands basic system architectural components for effective security testing. Knows typical attack surfaces in different architectural patterns: monolith, microservices, serverless. | |
| React Native Developer | Understands basic React Native application architecture — separation into screens, components, services. Follows project file structure — screens, components, hooks, services, navigation. Understands client-server architecture and the mobile app's role as a REST/GraphQL API client. | |
| Release Engineer | Understands system design basics for release infrastructure: CI/CD pipeline architecture, artifact repository design, and deployment environment topology. Follows team patterns for release workflow configuration and environment management. | |
| Security Analyst | Understands system design basics from a security perspective: network architecture components, trust boundaries, and data flow diagrams for threat analysis. Follows team practices for security architecture documentation and review participation. | |
| Site Reliability Engineer (SRE) | Understands production system architecture: load balancer → app servers → database, caching layer, message queues. Knows failure modes of each component. | |
| Smart Contract Developer | Understands basic system design concepts in the smart contract context: state management, composability, upgrade patterns. Draws contract diagrams and describes interaction flows. | |
| Systems Programmer (C/C++) | 必要 | Understands basic system design principles: modularity, abstraction, encapsulation, separation of concerns. Applies them when designing simple system components. |
| Technical Product Manager | 必要 | Understands system design basics for product decision-making: high-level architecture diagrams, API-first design principles, and scalability considerations. Follows team practices for technical requirements documentation and architecture discussion participation. |
| Technical Writer | Understands basic system design concepts: client-server, load balancing, caching, database types. Knows main architectural patterns. Can document high-level system architecture based on engineer descriptions. | |
| Telecom Developer | Understands basic telecom system design principles: high availability, low latency, and scalability. Knows core telecom architecture components: SBC, media server, signaling gateway. | |
| Unity Developer | Understands basic game system design principles in Unity: modularity, loose coupling through events, separation of concerns. Designs simple systems: inventory, quest tracker. | |
| Unreal Engine Developer | Understands basic game system design principles in Unreal: Gameplay Framework hierarchy, Components vs Inheritance, DataAssets for configuration. Designs simple gameplay systems. | |
| XR Unity Developer | Understands basic system design principles: client-server, request-response, load balancing. Knows how XR application interacts with backend components at a high level. |
| 角色 | 必要性 | 描述 |
|---|---|---|
| 1C Developer | Applies system design principles to 1C:Enterprise solutions: designs subsystem boundaries, plans data register structures for scalability, and implements proper separation between business logic and presentation. Understands trade-offs between thick and thin client architectures. Participates in architectural discussions for integration scenarios. | |
| AI Product Engineer | Designs AI product service architecture considering inference load, prediction caching, and horizontal scaling. Selects appropriate patterns for integrating ML models into the product architecture. | |
| Analytics Engineer | Architects analytics pipeline considering data volumes, update frequency, and freshness requirements. Selects patterns for data warehouse organization — star schema, medallion architecture, ELT vs ETL. | |
| Android Developer | Designs Android feature module architecture: proper decomposition into presentation/domain/data layers, boundary definition between modules, module API design (public interfaces). Applies Clean Architecture in the Android context: UseCase for business logic, Repository for data abstraction, mapping between layer models, correct dependency direction. | |
| Application Security Engineer | Analyzes application architecture from a security perspective: trust boundary identification, attack surface mapping, data flow analysis. Identifies architectural vulnerabilities at the design stage. | |
| AR/VR Developer | Architects AR/VR applications considering real-time requirements. Designs scene state synchronization systems between multiple VR clients. | |
| Backend Developer (C#/.NET) | Designs .NET application modules: Clean Architecture layers, domain-driven boundaries. Applies MediatR for CQRS, MassTransit for messaging. Evaluates trade-offs. | |
| Backend Developer (Elixir) | Designs Elixir applications with proper decomposition into OTP applications and umbrella projects. Implements bounded contexts through Phoenix contexts, defines module boundaries. Applies GenServer for stateful components and Task.Supervisor for async operations. | |
| Backend Developer (Go) | Designs Go services with clean architecture: layered structure with dependency injection, interfaces for dependency abstraction, configuration via Wire. Applies repository, service layer, and middleware chain patterns for building maintainable Go applications. | |
| Backend Developer (Java/Kotlin) | Designs Java application modules: layered architecture, domain-driven boundaries in monolith. Applies Spring Cloud for distributed systems: Config Server, Service Discovery, Circuit Breaker. Evaluates trade-offs of architectural decisions. | |
| Backend Developer (Node.js) | Designs Node.js modules: layered architecture (controller → service → repository), Clean Architecture principles. Applies NestJS modules for bounded contexts. Evaluates trade-offs. | |
| Backend Developer (PHP) | Designs PHP application modules: layer separation (Controller → Service → Repository), bounded contexts in monolith. Applies caching, queues, events for scaling. Evaluates trade-offs when choosing architectural decisions. | |
| Backend Developer (Python) | 必要 | Designs simple systems: URL shortener, REST API. Understands CAP theorem. Knows patterns: caching, load balancing, database replication. Evaluates non-functional requirements. |
| Backend Developer (Rust) | Develops Rust microservice architecture: hexagonal architecture with ports/adapters through trait abstractions, error handling strategy (thiserror for libraries, anyhow for applications). Designs modular workspace structures with shared crates for domain types. | |
| Backend Developer (Scala) | Designs Scala system components: microservice decomposition, choosing between synchronous (gRPC) and asynchronous (Kafka) communication. Understands CAP theorem in Akka Cluster context, applies retry/circuit breaker patterns and designs API contracts for inter-service communication. | |
| BI Analyst | Designs architecture of analytical subsystems: data warehouse schema, ETL pipeline, caching layer. Evaluates trade-offs when choosing technologies: batch vs streaming, star vs snowflake schema. Develops system design for medium-scale analytics platforms. | |
| Blockchain Developer | Designs blockchain service architecture: indexer, API gateway, cache layer. Understands consistency vs availability trade-offs for blockchain data. Selects technologies based on requirements. | |
| Cloud Engineer | Designs cloud-native systems: 12-factor apps, microservices on managed services (Lambda, ECS, Cloud Run), event-driven architecture with SQS/EventBridge. Chooses between managed and self-hosted solutions considering cost, operational overhead and vendor lock-in. | |
| Compiler Engineer | Applies system design principles to compiler architecture: phase modularity, clear interfaces between IR levels, error handling strategies across components. | |
| Computer Vision Engineer | Designs architecture of medium CV systems considering batch and real-time inference, model and data storage. Selects appropriate technologies for specific CV tasks. | |
| Data Analyst | Designs medium-scale analytical system architecture considering scalability and fault tolerance. Selects appropriate data storage and processing technologies for specific tasks. | |
| Data Engineer | Designs data systems: partitioning strategies, replication models, consistency trade-offs. Defines capacity requirements for pipelines. | |
| Data Scientist | Designs ML systems considering scalability and reliability. Understands microservices architecture, message queues, caching for ML serving. Works with Docker for ML model containerization, configures basic monitoring and alerting. | |
| Database Engineer / DBA | Applies system design principles when planning DB infrastructure: choosing DBMS type, defining availability requirements, designing replication and backup schemes. | |
| Desktop Developer (.NET WPF/WinUI/MAUI) | Designs .NET desktop application architecture with clear layer separation through Dependency Injection and MVVM pattern. Selects data caching strategies, background synchronization and state management for rich-client applications. | |
| Desktop Developer (Electron/Tauri) | Designs Electron application architecture considering IPC communication, state management and offline mode. Chooses appropriate patterns for data synchronization between client and server. | |
| Desktop Developer (Qt/C++) | Designs Qt application architecture with clear separation of business logic, presentation and network interaction. Selects patterns for data organization, caching and synchronization between desktop client and server components. | |
| DevOps Engineer | Applies system design patterns to infrastructure: designs scalable deployments with load balancing, configures caching at different levels (CDN, Redis, application). Evaluates capacity and plans resources for growing workloads. | |
| DevSecOps Engineer | Designs CI/CD pipeline security components considering fault tolerance and scalability principles. Considers trade-off between scanning speed and analysis depth when designing systems. | |
| Embedded Developer | Designs embedded subsystems: hardware/software partitioning, peripheral allocation, power management strategy. Makes informed trade-offs between performance, power consumption and cost. | |
| Engineering Manager | Applies system design thinking in team leadership: evaluates architectural trade-offs for feature delivery, facilitates design discussions with technical context, and ensures non-functional requirements (scalability, reliability, security) are addressed in design phase. Participates meaningfully in architecture reviews. | |
| Flutter Developer | Applies system design principles to Flutter applications: clean architecture layers (presentation/domain/data), repository pattern for data access, and platform-specific service abstraction. Understands trade-offs between state management approaches (BLoC, Riverpod, Provider). Designs API contracts for backend integration. | |
| Frontend Developer (Angular) | Designs Angular application architecture considering scalability and caching. Develops data handling strategies — lazy loading, prefetching, and offline-first. | |
| Frontend Developer (React) | Designs React application architecture considering scalability: state management, routing, data fetching strategies. Chooses appropriate patterns for SSR/SSG/CSR based on requirements. | |
| Frontend Developer (Svelte) | Designs medium-sized SvelteKit application architecture considering SSR/SSG, routing, and state management. Selects appropriate patterns for specific tasks. | |
| Frontend Developer (Vue) | Designs medium-complexity Vue application architecture — modular structure, routing, state management, data caching. Chooses between SPA, SSR and SSG approaches. | |
| Fullstack Developer | Designs fullstack feature architecture: choosing between SSR and SPA, multi-level caching, task queues. Draws sequence diagrams for end-to-end scenarios (UI → API → Worker → DB), considers scalability and failure points. | |
| Game Designer | Designs game subsystem architecture: lobby, party system, chat, leaderboard with scaling considerations. Evaluates trade-offs in architectural decisions: latency vs consistency, cost vs performance. Develops system design for medium-scale multiplayer games. | |
| Game QA Engineer | Applies system design knowledge for testing: understands ECS, event systems, state machines in game logic context. Tests subsystem interactions and edge cases. | |
| Game Server Developer | Designs server architecture for specific game modes with scalability in mind. Separates stateful and stateless components, selects appropriate state synchronization patterns. | |
| Infrastructure Engineer | Designs infrastructure for common architectures: three-tier applications, microservices, event-driven systems. Considers availability, performance and cost requirements when selecting components. | |
| iOS Developer | Designs medium-complexity iOS application architecture: MVVM with Coordinator for navigation, service layer for data and networking. Separates project into modules via SPM packages, defines layer responsibility boundaries. Applies dependency injection through constructors or SwiftUI Environment, designs data flow between screens. | |
| IoT Engineer | Applies system design principles to IoT: edge-cloud architecture, protocol selection (MQTT/CoAP/HTTP), balancing processing between device and server, offline operation strategies. | |
| Language Tooling Engineer | Designs modular language servers with clear separation of concerns. Applies design patterns for extensible code analysis systems with plugin support. | |
| LLM Engineer | Independently designs medium-complexity LLM systems: RAG service with caching, async processing, and message queues. Considers scalability, reliability, and cost when choosing architectural decisions. | |
| ML Engineer | Designs ML systems with separation into training and serving components considering scalability. Applies batch prediction, online inference and feature serving patterns for common ML tasks. | |
| MLOps Engineer | Applies system design principles to ML infrastructure: training pipeline architecture, storage selection for datasets, model serving design considering latency and throughput. | |
| Network Engineer | Designs reliable network services considering fault tolerance and scalability. Applies active-standby, ECMP, anycast patterns to ensure high availability of network functions. | |
| NLP Engineer | Designs scalable NLP services with separation into processing and inference pipelines. Applies design patterns for systems with GPU resources and asynchronous processing. | |
| Penetration Testing Engineer | Analyzes target system architecture for pentest planning — identifies trust boundaries, data flows, and attack vectors. Designs pentest lab architecture. | |
| Performance Testing Engineer | Applies system design knowledge when planning performance tests: identifying load points, modeling user workload, designing test environments that mimic production. | |
| Platform Engineer | Designs individual platform components: API design, caching strategy, message-driven architectures. Analyzes trade-offs when choosing technologies. Creates ADRs (Architecture Decision Records) for platform decisions. Conducts design reviews for new services. | |
| Product Manager | 必要 | Understands trade-offs of architectural decisions and their impact on the product. Participates in technical discussions. Considers technical constraints in product decisions. |
| QA Automation Engineer | Designs test strategy considering system architecture — which components to test in isolation, where integration tests are needed, how to mock external services. | |
| QA Engineer (Manual) | Analyzes system design for designing comprehensive end-to-end test scenarios. Evaluates failure points and integration points in architecture for prioritizing testing efforts. Creates test plans considering scalability, fault tolerance, and performance characteristics. | |
| QA Security Engineer | Analyzes architecture of systems under test to determine security testing strategy. Identifies trust boundaries, critical data flows, and entry points for targeted testing. | |
| React Native Developer | Designs React Native module architecture — Feature-Sliced or modular structure. Separates the application into layers: UI, business logic, data layer, navigation. Applies dependency injection for testability. Designs offline-first scenarios with data caching and synchronization. | |
| Release Engineer | Designs release system components considering scalability requirements. Develops architecture for deployment orchestration services with high availability support. | |
| Security Analyst | Designs security components with scalability and fault tolerance in mind. Develops architecture for security monitoring systems with high availability. | |
| Site Reliability Engineer (SRE) | Designs reliable systems: redundancy patterns (active-passive, active-active), circuit breakers, retry with backoff. Conducts failure mode analysis. Chooses sync vs async communication. | |
| Smart Contract Developer | Designs smart contract system architecture: separation of concerns, proxy patterns for upgradeability, registry patterns for service discovery. Documents architectural decisions. | |
| Systems Programmer (C/C++) | 必要 | Designs system components with proper abstractions: HAL, platform abstraction, API contracts. Applies layered architecture for kernel subsystems and drivers. |
| Technical Lead | Applies system design principles when designing product components: defines service boundaries, evaluates data storage choices, and designs communication patterns between services. Understands trade-offs in consistency, availability, and partition tolerance. Participates actively in architectural decision-making. | |
| Technical Product Manager | 必要 | Understands system design patterns and their impact on product capabilities. Evaluates trade-offs: consistency vs availability, latency vs throughput. Participates in architecture reviews with informed product perspective. |
| Technical Writer | Documents system design decisions: capacity planning, scalability patterns, failure modes. Creates architecture overviews for different audiences (engineers, management, new hires). Visualizes complex systems through clear diagrams. | |
| Telecom Developer | Designs telecom services meeting 99.999% availability and fixed latency requirements. Applies active-active and geographic redundancy patterns to ensure communication continuity. | |
| Unity Developer | Designs medium-complexity game systems in Unity: save system, economy system, achievement system. Uses ScriptableObject architecture for decoupled design. Documents systems via UML. | |
| Unreal Engine Developer | Designs medium-complexity game systems in Unreal: save system with versioning, economy system with server validation, progression system via GAS attributes. | |
| XR Unity Developer | Designs server architecture for XR applications considering low-latency requirements and scalability. Selects appropriate communication patterns: REST, WebSocket, UDP for different types of XR interactions. |
| 角色 | 必要性 | 描述 |
|---|---|---|
| 1C Developer | 必要 | Designs system architecture for complex 1C:Enterprise solutions: high-availability cluster configurations, integration architecture with external systems (REST/SOAP/messaging), and data partitioning strategies for large-scale infobases. Makes architectural decisions (ADRs) for enterprise 1C deployments. Evaluates non-functional requirements for 1C platform solutions. |
| AI Product Engineer | Develops architecture for complex AI product systems with real-time inference, model A/B testing, and graceful degradation. Designs fault-tolerant data processing pipelines with delivery guarantees and idempotency. | |
| Analytics Engineer | Architects the analytics platform with real-time and batch layers, data mesh approach, and federation queries. Designs scalable systems considering the CAP theorem and eventual consistency for analytical data. | |
| Android Developer | 必要 | Designs multi-module Android application architecture: decomposition into feature/core/shared modules, defining inter-module contracts through API modules, navigation strategy between feature modules. Designs scalable solutions for 20+ modules, defines bounded context boundaries, applies DDD principles for complex domains in mobile context. |
| Application Security Engineer | Conducts security architecture reviews for complex distributed systems. Designs security layers for different architectural patterns: service mesh, API gateway, event-driven with threat model consideration. | |
| AR/VR Developer | Architects scalable AR/VR platforms with server-side rendering. Designs spatial computing systems with distributed processing and edge computing. | |
| Backend Developer (C#/.NET) | 必要 | Designs .NET system architecture: decomposition into microservices, event-driven via MassTransit, CQRS. Defines API contracts (OpenAPI, gRPC). Capacity planning via BenchmarkDotNet. |
| Backend Developer (Elixir) | 必要 | Designs distributed Elixir systems with microservice architecture on BEAM. Defines service boundaries through DDD, implements inter-service communication through distributed Erlang or gRPC with Protobuf. Designs resilient systems with circuit breaker through Fuse and bulkhead patterns. |
| Backend Developer (Go) | 必要 | Designs Go microservice architecture: event-driven via Kafka, CQRS for read/write separation, saga pattern for distributed transactions. Designs API contracts, defines service boundaries and data strategies, documents via Architecture Decision Records. |
| Backend Developer (Java/Kotlin) | 必要 | Designs Java system architecture: decomposition into microservices, event-driven via Kafka, CQRS for high-read services. Defines API contracts (OpenAPI, gRPC). Conducts capacity planning with JMH benchmarks. |
| Backend Developer (Node.js) | 必要 | Designs distributed Node.js systems: microservices decomposition, event-driven communication, CQRS for high-read services. Defines API contracts and inter-service communication. |
| Backend Developer (PHP) | 必要 | Designs PHP system architecture: monolith decomposition into modules/services, event-driven interaction, CQRS for high-load operations. Defines API contracts between services. Conducts capacity planning and designs for load. |
| Backend Developer (Python) | 必要 | Designs distributed systems. Applies patterns: Circuit Breaker, Bulkhead, Retry. Designs for fault tolerance and graceful degradation. Evaluates capacity planning. |
| Backend Developer (Rust) | 必要 | Designs distributed systems in Rust: event-driven architecture with Kafka/NATS, CQRS with separate read/write models, saga patterns for distributed transactions. Applies tower middleware stacks for cross-cutting concerns and designs resilience patterns (circuit breaker, bulkhead). |
| Backend Developer (Scala) | 必要 | Designs Scala systems end-to-end: distributed systems on Akka Cluster, Event Sourcing with Akka Persistence, CQRS for scaling. Makes trade-off decisions on consistency vs availability, designs fault-tolerant architectures with graceful degradation and self-healing. |
| BI Analyst | Designs enterprise data platform architecture: lakehouse, data mesh, real-time analytics stack. Solves complex challenges: data consistency, event-time processing, schema evolution, data versioning. Creates technical design documents and conducts architectural reviews of analytical systems. | |
| Blockchain Developer | Designs distributed systems for blockchain infrastructure: multi-region deployment, reliable transaction processing, event-driven architectures. Ensures high availability and fault tolerance. | |
| Cloud Engineer | 必要 | Designs complex distributed systems in cloud: saga pattern for distributed transactions, CQRS with DynamoDB Streams/Change Data Capture, multi-tenant architecture. Documents architectural decisions through ADR and conducts system design review. |
| Compiler Engineer | Designs compiler subsystems with scalability in mind: incremental compilation, lazy module loading, architecture for supporting multiple code generation backends. | |
| Computer Vision Engineer | Designs distributed CV systems for processing millions of images considering GPU clusters, model serving, and data pipelines. Optimizes latency and throughput. | |
| Data Analyst | Designs complex distributed analytical systems considering CAP theorem, partitioning, and replication. Develops real-time and batch analytics architecture. | |
| Data Engineer | Defines data system architecture: distributed data processing, storage tiering, compute separation. Designs scalable data platform. | |
| Data Scientist | Designs end-to-end ML systems: data ingestion, feature computation, training, serving, monitoring. Applies event-driven architecture for real-time ML. Optimizes system design for cost efficiency and reliability. | |
| Database Engineer / DBA | Designs data architecture for complex systems: distributed transactions, CQRS, event sourcing. Defines sharding, partitioning, and consistency strategies for high-load. | |
| Desktop Developer (.NET WPF/WinUI/MAUI) | Develops architecture for complex .NET desktop applications with plugin system through MEF, offline mode and conflict resolution. Designs scalable server component interaction through SignalR and gRPC. | |
| Desktop Developer (Electron/Tauri) | Develops scalable architecture for complex Electron applications: plugin systems, multi-window, background processes. Designs systems considering desktop platform constraints and network conditions. | |
| Desktop Developer (Qt/C++) | Develops architecture for complex Qt applications with plugin system, offline mode and conflict-resistant data synchronization. Designs scalable server components for supporting distributed desktop solutions. | |
| DevOps Engineer | 必要 | Designs infrastructure for high-load systems: multi-tier architecture with auto-scaling, event-driven microservices, CQRS for separating read/write workloads. Conducts capacity planning, defines SLO/SLI and designs for target reliability. |
| DevSecOps Engineer | Designs security platform architecture with distributed scanners, centralized storage and API layer. Designs systems considering high availability requirements for critical security functions. | |
| Embedded Developer | Designs complex embedded system architecture with distributed processing across multiple processors. Designs fault-tolerant systems with watchdog, graceful degradation and recovery mechanisms. | |
| Engineering Manager | 必要 | Designs system architecture for team products: defines service decomposition strategy, makes technology selection decisions, and ensures architecture supports business scalability goals. Creates ADRs and architecture documentation. Evaluates build-vs-buy decisions. Conducts architecture reviews with focus on non-functional requirements. |
| Flutter Developer | 必要 | Designs system architecture for Flutter products: offline-first data sync architecture, micro-frontend patterns for large Flutter apps, and cross-platform abstraction layers for platform-specific features. Makes architectural decisions balancing development velocity with app performance. Creates architecture documentation with C4/ADR patterns. Evaluates new Flutter frameworks and tools for team adoption. |
| Frontend Developer (Angular) | Creates architecture for complex Angular applications with micro-frontends and module federation. Designs horizontally scalable systems with optimal resource loading. | |
| Frontend Developer (React) | Develops architecture for complex React applications: micro-frontend, module federation, island architecture. Designs systems considering performance budgets, code splitting and progressive enhancement. | |
| Frontend Developer (Svelte) | Designs complex Svelte application architecture with micro-frontend approach, edge rendering, and offline-first strategies. Defines responsibility boundaries between client and server. | |
| Frontend Developer (Vue) | Develops architecture for large-scale Vue applications — micro-frontends, federated modules, shared libraries, bundle optimization through code splitting and lazy loading. | |
| Fullstack Developer | 必要 | Designs system architecture for fullstack applications: microservices vs monolith, event-driven communication, CQRS for read/write separation. Defines technical solutions for non-functional requirements: performance, availability, scalability. |
| Game Designer | Designs architecture for large game platforms: MMO backend, live-service infrastructure, cross-platform systems. Solves complex distributed system challenges: eventual consistency, conflict resolution for game data. Creates system design documentation and conducts architectural reviews. | |
| Game QA Engineer | Uses system design knowledge for designing test strategies. Analyzes architecture to identify risk areas, designs integration tests for interconnected subsystems. | |
| Game Server Developer | Develops architecture for high-load game systems — game world sharding, eventual consistency for inventory, CQRS for leaderboards. Accounts for global player distribution. | |
| Infrastructure Engineer | Develops infrastructure architecture for high-load systems considering CAP theorem and trade-offs. Designs multi-region deployment with failover, data replication and split-brain protection. | |
| iOS Developer | 必要 | Architects scalable iOS application architecture: multi-module structure with clear dependencies, feature-based organization with independent development. Defines navigation strategy for complex applications, designs state management system. Analyzes trade-offs between approaches (MVVM+C vs TCA vs VIPER) for specific business requirements. |
| IoT Engineer | Designs scalable IoT systems: architecture for millions of devices, event-driven telemetry processing, edge buffering strategies during cloud connectivity loss. | |
| Language Tooling Engineer | Develops architecture for distributed language tools considering scalability and fault tolerance. Designs incremental compilation and analysis result caching systems. | |
| LLM Engineer | Designs complex LLM systems: multi-model inference platforms, real-time RAG with streaming, distributed vector search. Ensures high availability, fault tolerance, and horizontal scalability. | |
| ML Engineer | Designs ML platform architecture with distributed training, model A/B testing and canary deployment. Designs real-time inference systems with low-latency requirements and graceful degradation. | |
| MLOps Engineer | Architects scalable ML platforms: distributed training architecture, feature store with low-latency access, multi-model serving with A/B testing and canary deployments. | |
| Network Engineer | Develops architecture for complex distributed network systems — SDN controllers, overlay networks, multi-region connectivity. Considers CAP theorem and consistency models in design. | |
| NLP Engineer | Develops distributed NLP platform architecture with scalability in mind. Designs model serving systems with A/B testing, canary deployments, and automatic rollback. | |
| Penetration Testing Engineer | Conducts threat modeling of complex distributed systems, identifies attack paths through microservices and API gateways. Designs red team infrastructure architecture. | |
| Performance Testing Engineer | Designs performance tests for complex architectures: microservices, event-driven systems, distributed caching. Defines testing strategy for each architectural component. | |
| Platform Engineer | 必要 | Develops IDP subsystem architecture: API gateway design, developer portal, self-service workflows. Creates reference architectures for typical platform patterns. Implements Architecture Fitness Functions for continuous validation of architectural decisions. |
| Product Manager | 必要 | Deeply understands the product's system architecture. Makes product decisions considering technical trade-offs. Can challenge technical decisions. |
| QA Automation Engineer | Develops test infrastructure architecture for distributed systems — parallel test execution, service virtualization, test data management in a microservices environment. | |
| QA Engineer (Manual) | Designs testing strategy based on deep analysis of project system architecture. Defines risk-based approach to testing considering architectural trade-offs and critical paths. Develops methodology for testing non-functional requirements: scalability, reliability, availability. | |
| QA Security Engineer | Designs security testing strategies for complex distributed systems considering architectural specifics. Develops threat models as the basis for test campaign planning. | |
| React Native Developer | 必要 | Architects large-scale React Native application — monorepo with shared packages, modular architecture with lazy loading. Defines boundaries between JS and Native layers. Designs migration to New Architecture. Develops ADRs (Architecture Decision Records) for key decisions. |
| Release Engineer | Creates architecture for distributed release platforms with horizontal scaling. Designs self-healing systems ensuring continuity of delivery processes. | |
| Security Analyst | Creates architecture for distributed security platforms for event correlation. Designs threat detection systems with horizontal scaling and minimal latency. | |
| Site Reliability Engineer (SRE) | 必要 | Designs distributed systems: CAP theorem trade-offs, consensus protocols, eventual consistency patterns. Defines data replication strategy. Designs cross-service communication (mesh, events). |
| Smart Contract Developer | Designs complex contract systems: multi-protocol integration, cross-chain deployment architecture, emergency pause and recovery mechanisms. Ensures modularity and extensibility. | |
| Solutions Architect | 必要 | Designs system architecture for complex enterprise solutions: distributed systems with consistency guarantees, event-driven architectures for real-time processing, and multi-tenant platform design. Makes architectural decisions considering scalability, reliability, security, and cost trade-offs. Creates reference architectures for common solution patterns. |
| Systems Programmer (C/C++) | 必要 | Designs complex system architectures: microkernel vs monolith tradeoffs, multi-layer HAL, cross-platform abstraction. Ensures backward compatibility and extensibility. |
| Technical Lead | 必要 | Designs system architecture for product: service decomposition, data architecture, and integration patterns. Makes architectural decisions (ADRs) balancing scalability, reliability, and development velocity. Evaluates non-functional requirements and designs for operational excellence. Creates architecture documentation and mentors team on design thinking. |
| Technical Product Manager | 必要 | Actively participates in system design for complex product scenarios. Understands distributed systems challenges: CAP theorem, eventual consistency. Defines non-functional requirements considering scale and reliability targets. |
| Technical Writer | Creates comprehensive system design documentation: NFR (non-functional requirements), capacity models, failure analysis, DR plans. Ensures coherence between system design docs, ADRs, and operational runbooks. | |
| Telecom Developer | Develops telecom platform architecture with distributed signaling and media stream processing. Designs systems meeting carrier-grade requirements: hitless upgrade, graceful degradation, overload control. | |
| Unity Developer | 必要 | Designs architecture for large Unity projects: game framework, plugin system, mod support. Ensures extensibility and maintainability for projects with 2+ years of development. |
| Unreal Engine Developer | 必要 | Designs AAA Unreal project architecture: Game Features for modularity, plugin-based systems, mod support via pak files. Ensures long-term maintainability. |
| XR Unity Developer | Develops distributed systems for XR platforms considering CAP theorem and eventual consistency. Designs architecture for multiplayer XR applications with regional routing and state prediction. |
| 角色 | 必要性 | 描述 |
|---|---|---|
| 1C Developer | 必要 | Defines architectural strategy for 1C:Enterprise products: platform migration planning, hybrid architecture with modern tech stacks, and enterprise integration strategy. Establishes architecture review processes and design guidelines. Conducts architecture reviews for major 1C system changes. |
| AI Product Engineer | Defines architectural principles and patterns for the AI product ecosystem, including event-driven processing and CQRS for ML data. Leads design of platform solutions to accelerate new AI product development. | |
| Analytics Engineer | Defines architectural principles for the analytics platform, including data lakehouse, streaming, and semantic layer. Leads system design to enable business user self-service and analytics scalability. | |
| Android Developer | 必要 | Defines architectural standards for the Android team: reference architecture for new applications, module decomposition and dependency rules, architectural review and ADR processes. Conducts design reviews for complex features, trains the team on design principles, balances ideal architecture with pragmatic delivery considering business priorities. |
| Application Security Engineer | Defines security requirements for system architecture at the organizational level. Creates reference security architectures for typical patterns and ensures their implementation in the design process. | |
| AR/VR Developer | Defines architectural standards for the organization's AR/VR systems. Conducts design reviews of complex XR projects with a focus on latency and multiplayer scalability. | |
| Backend Developer (C#/.NET) | 必要 | Makes architectural decisions: monolith vs microservices, MassTransit vs raw Kafka, sync vs async. Documents ADRs. Mentors senior developers. |
| Backend Developer (Elixir) | 必要 | Defines architectural standards for the organizational Elixir platform. Designs reference architecture with Phoenix, Ecto, Broadway and distributed OTP. Implements ADR (Architecture Decision Records), conducts architectural reviews and defines system evolution strategy. |
| Backend Developer (Go) | 必要 | Defines architectural standards for the Go team platform: microservice reference architecture, new service templates, inter-service communication patterns. Conducts architecture reviews, coordinates technical strategy and prioritizes tech debt. |
| Backend Developer (Java/Kotlin) | 必要 | Makes architectural decisions: monolith vs microservices, Spring Cloud vs Kubernetes-native, sync vs async. Documents ADRs. Conducts architectural reviews and mentors senior developers. |
| Backend Developer (Node.js) | 必要 | Makes architectural decisions: monolith vs microservices, NestJS vs Fastify, sync vs async. Documents ADRs. Conducts architecture reviews. |
| Backend Developer (PHP) | 必要 | Makes architectural decisions for the product: choosing between monolith and microservices, defining service boundaries, data strategy. Documents ADRs. Conducts architectural reviews and mentors senior developers. |
| Backend Developer (Python) | 必要 | Designs architecture at domain level. Conducts architecture decision reviews. Defines NFRs for services. Trains the team on system design. |
| Backend Developer (Rust) | 必要 | Defines architectural standards for Rust platform: reference architecture for microservices, ADR process for architectural decisions, technology radar. Develops platform SDK crates with abstractions for observability, configuration and service communication. |
| Backend Developer (Scala) | 必要 | Defines architectural standards for Scala team: Architecture Decision Records, service design patterns, migration strategies. Reviews system design for non-functional requirements compliance, conducts design review sessions and creates technical architecture documentation. |
| BI Analyst | Defines the analytical platform's system architecture and coordinates technical vision. Conducts design reviews and makes architectural decisions for the entire project's data platform. Mentors senior analysts in system design skills for analytical systems. | |
| Blockchain Developer | Defines system design principles for the blockchain organization. Conducts architecture reviews and establishes design document templates. Coordinates cross-team architectural decisions. | |
| Cloud Engineer | 必要 | Defines organizational architectural standards: technology radar, reference architectures for common scenarios (REST API, event processing, data pipeline). Establishes architecture review process and trains teams on cloud-native design patterns. |
| Compiler Engineer | Defines architectural decisions for the compiler platform: extensibility through plugins, caching strategies, balance between compilation time and optimization quality. | |
| Computer Vision Engineer | Leads CV system design in the team, conducts design reviews and defines architectural standards. Balances GPU infrastructure costs and performance requirements. | |
| Data Analyst | Leads analytical system design process for the team, conducts design reviews and defines architectural standards. Balances technical debt against new business requirements. | |
| Data Engineer | Defines system design standards: architecture review criteria, scalability requirements, reliability guidelines for data systems. | |
| Data Scientist | Defines architectural standards for the team's ML systems. Establishes reference architectures for typical ML use cases. Coordinates ML engineering and platform teams for building reliable ML infrastructure. | |
| Database Engineer / DBA | Defines data architecture for products: polyglot storage (SQL + NoSQL + Cache), scaling strategies, multi-region architecture for global applications with low latency. | |
| Desktop Developer (.NET WPF/WinUI/MAUI) | Defines architectural principles for .NET desktop application ecosystem, including cloud service integration patterns. Leads platform solution design and reference architecture for desktop products. | |
| Desktop Developer (Electron/Tauri) | Defines architectural standards for all organization's Electron products. Makes key trade-off decisions between performance, update convenience and offline capabilities. | |
| Desktop Developer (Qt/C++) | Defines architectural principles for the Qt application ecosystem, including cloud service and IoT device integration patterns. Leads platform solution design for accelerating new desktop product development. | |
| DevOps Engineer | 必要 | Defines organizational infrastructure architectural standards: reference architectures for typical patterns (web app, API, data pipeline). Conducts architecture reviews, defines scaling and fault tolerance guidelines for all teams. |
| DevSecOps Engineer | Defines system architecture of the organization's DevSecOps platform, including integration with existing infrastructure. Makes strategic build vs buy decisions for security tools based on requirements. | |
| Embedded Developer | Defines embedded product system architecture, including the split between hardware and software functionality. Makes strategic decisions on trade-offs between performance, power consumption and cost. | |
| Engineering Manager | 必要 | Defines product architectural strategy with System Design Fundamentals. Shapes architecture guidelines. Conducts architecture reviews. |
| Flutter Developer | 必要 | Defines architectural strategy for Flutter/mobile products: cross-platform architecture standards, shared code strategies between mobile and web, and integration architecture with backend services. Establishes architecture review processes and mobile-specific design guidelines. Conducts architecture reviews for major feature implementations. |
| Frontend Developer (Angular) | Defines architectural standards for Angular projects with a performance focus. Conducts design reviews of complex frontend systems and trains the team on design principles. | |
| Frontend Developer (React) | Defines architectural standards for the organization's React projects, including decision records. Makes key decisions on rendering strategies and frontend system design. | |
| Frontend Developer (Svelte) | Leads the frontend system design process in the team, conducts design reviews and defines architectural standards. Balances technical debt with new requirements. | |
| Frontend Developer (Vue) | Conducts architectural reviews of team's Vue projects. Makes strategic decisions about technology stack, state management patterns and inter-service communication approaches. | |
| Fullstack Developer | 必要 | Defines architectural standards for the fullstack platform: reference architectures for typical projects, ADR process, technical roadmap. Conducts architectural reviews, coordinates cross-team decisions and ensures technical vision alignment. |
| Game Designer | Defines system architecture for the entire game project and coordinates technical vision across teams. Conducts design reviews and makes key architectural decisions considering business requirements. Mentors senior engineers in game platform system design skills. | |
| Game QA Engineer | Defines approaches to architecture-aware testing for QA team. Establishes guidelines for testing various architectural patterns: ECS, microservices, event-driven. | |
| Game Server Developer | Conducts architectural reviews of server systems and makes strategic technology stack decisions. Balances architectural complexity with development speed for new content. | |
| Infrastructure Engineer | Defines infrastructure architecture standards for different service criticality levels. Creates reference architectures and landing zones for fast onboarding of new product teams. | |
| iOS Developer | 必要 | Defines architectural strategy for the iOS product: modular architecture with dependency graph, inter-module and feature-layer communication standards. Designs platform subsystems: analytics, logging, feature flags, and A/B testing. Conducts architecture decision records and trains the team on mobile system design principles. |
| IoT Engineer | Defines IoT platform system architecture: multi-tenant design, federation across regions, scaling strategies from prototype to production for a million devices. | |
| Language Tooling Engineer | Defines architectural principles for the entire language tooling platform. Designs systems with horizontal scaling support and ensures component consistency. | |
| LLM Engineer | Defines architectural standards for the LLM team. Establishes system design guidelines for ML systems, conducts architecture reviews, defines technical debt management strategy. | |
| ML Engineer | Defines system architecture of organizational ML platform, including feature platform, experiment tracking and model governance. Makes strategic decisions on trade-offs between latency, cost and model quality. | |
| MLOps Engineer | Defines the organization's ML platform architecture: standards for end-to-end pipelines, integration with data platform, architecture for real-time and batch inference, multi-tenant isolation. | |
| Network Engineer | Conducts architectural reviews of the team's network systems and makes key technology decisions. Ensures design alignment with business requirements and SLAs. | |
| NLP Engineer | Defines architectural principles for the organizational NLP platform. Designs systems supporting multi-model inference, feature store, and unified data processing pipeline. | |
| Penetration Testing Engineer | Leads process threat modeling for the team, defines methodologies for architecture security analysis. Creates reference architecture for secure system design. | |
| Performance Testing Engineer | Defines performance testing approaches for various architectural patterns: serverless, CQRS, event sourcing. Advises architects on performance implications of their decisions. | |
| Platform Engineer | 必要 | Defines architectural standards and principles for the platform: API-first design, modular architecture, domain boundaries. Leads Architecture Guild and review process. Creates Technology Radar for the organization. Designs evolutionary architecture for long-term IDP development. |
| Product Manager | 必要 | Participates in strategic architectural decisions. Ensures alignment between technical and product strategy. |
| QA Automation Engineer | Defines testing strategy for complex architectural decisions — event-driven systems, saga patterns, CQRS. Ensures adequate coverage of all architectural components. | |
| QA Engineer (Manual) | Defines test architecture and system design standards for the QA team. Conducts design reviews and makes architectural decisions for test infrastructure. Mentors senior QA engineers. | |
| QA Security Engineer | Defines security testing methodology for various architectural patterns in the organization. Creates test strategies for new systems at the architectural design stage. | |
| React Native Developer | 必要 | Defines the architectural strategy for the team's mobile apps. Establishes React Native reference architecture — layers, modules, dependencies. Conducts architecture reviews for new features and projects. Determines trade-offs between monolith and micro-frontends in the mobile context. |
| Release Engineer | Defines architectural standards for release platforms and continuous delivery systems. Conducts design reviews of critical infrastructure components with a focus on fault tolerance. | |
| Security Analyst | Defines architectural standards for organizational security systems. Conducts design reviews focused on security — threat modeling and attack surface analysis. | |
| Site Reliability Engineer (SRE) | 必要 | Defines reliability architecture standards: mandatory design reviews, failure budget, architecture templates. Conducts architecture reviews focused on failure modes and scalability. |
| Smart Contract Developer | Defines system design principles for smart contract organizations. Conducts architecture reviews and establishes design templates. Coordinates cross-team architectural decisions. | |
| Solutions Architect | 必要 | Defines product architectural strategy: establishes architecture principles, design patterns catalog, and technology radar for the organization. Conducts architecture reviews for critical system changes. Creates architecture governance framework with clear decision-making processes. Drives adoption of architectural best practices across teams. |
| Systems Programmer (C/C++) | 必要 | Defines system architecture for the product platform. Establishes architectural decision records, conducts system design reviews, coordinates cross-component interfaces. |
| Technical Lead | 必要 | Defines the product's architectural strategy with System Design Fundamentals. Establishes architecture guidelines. Conducts architecture reviews. |
| Technical Product Manager | 必要 | Defines architectural standards for the product division. Reviews system design proposals with product lens. Shapes technology radar and architecture principles. Trains TPMs on system design fundamentals. |
| Technical Writer | Defines system design documentation standards for the organization. Coordinates documentation of cross-cutting concerns: security, performance, reliability. Trains teams on documenting architectural decisions. | |
| Telecom Developer | Defines system architecture for the organization's telecom products, including transition from monolithic to cloud-native solutions. Makes strategic trade-off decisions between performance, cost, and flexibility. | |
| Unity Developer | 必要 | Defines architectural standards for Unity studio. Establishes reference architectures for different game types. Conducts architectural reviews and mentoring on system design. |
| Unreal Engine Developer | 必要 | Defines architectural standards for the Unreal studio. Establishes reference architectures. Conducts architecture reviews and mentoring on system design. |
| XR Unity Developer | Defines system architecture for organizational XR products, including scaling and fault tolerance strategies. Makes key trade-off decisions between latency, consistency and availability. |
| 角色 | 必要性 | 描述 |
|---|---|---|
| 1C Developer | 必要 | Defines organizational architectural strategy for 1C:Enterprise ecosystem: enterprise architecture framework, 1C modernization roadmap, and hybrid integration architecture with modern platforms. Designs reference architectures for large-scale 1C deployments. Establishes architecture governance across the organization. |
| AI Product Engineer | Shapes technology strategy and reference architecture for enterprise-scale AI product platform. Defines design principles ensuring system evolution with multiplicative growth of models and products. | |
| Analytics Engineer | Shapes the corporate analytics platform technology strategy considering data mesh and data fabric approaches. Defines the reference architecture for enterprise-scale analytics systems supporting hybrid scenarios. | |
| Android Developer | 必要 | Shapes the Android platform's architectural strategy: standards for all organizational applications, shared platform module architecture (auth, analytics, networking, feature flags). Designs solutions for enterprise scale — 100+ modules, 50+ developers, defines architecture evolution strategy, mentors leads on making complex architectural decisions with long-term consequences. |
| Application Security Engineer | Shapes the architectural vision for system security across the entire organization. Defines secure-by-design and zero-trust architecture principles applicable to the full spectrum of products and platforms. | |
| AR/VR Developer | Shapes the architectural strategy for the organization's AR/VR platform. Architects the immersive product ecosystem with unified rendering and networking architecture. | |
| Backend Developer (C#/.NET) | 必要 | Defines architectural strategy: reference architecture on ASP.NET Core, inter-service communication standards. Plans platform evolution. |
| Backend Developer (Elixir) | 必要 | Develops architectural strategy at the entire Elixir ecosystem level. Defines patterns for different load profiles: real-time through Phoenix Channels, batch through Broadway, API through Phoenix. Designs platform with shared-nothing architecture and automatic scaling. |
| Backend Developer (Go) | 必要 | Shapes system architecture for the entire Go platform: domain-driven decomposition, platform engineering, standards for all teams. Defines technology strategy, coordinates cross-team initiatives, and ensures architectural consistency. |
| Backend Developer (Java/Kotlin) | 必要 | Defines organizational architecture strategy: reference architecture on Spring Boot/Cloud, inter-service communication standards (gRPC, Kafka), data mesh. Plans platform evolution. |
| Backend Developer (Node.js) | 必要 | Defines architectural strategy: reference architecture on Node.js, inter-service communication standards, platform abstractions. Plans evolution roadmap. |
| Backend Developer (PHP) | 必要 | Defines organizational architecture strategy: reference architecture for PHP platform, inter-service communication standards, data mesh. Evaluates technology landscape and plans system evolution for 2-3 years. |
| Backend Developer (Python) | 必要 | Defines company system architecture. Designs multi-region deployment. Establishes architecture principles. Mentors architects. |
| Backend Developer (Rust) | 必要 | Shapes organizational technology strategy and architectural vision: domain-driven design at organizational level, evolutionary architecture principles. Defines platform architecture considering Rust specifics (zero-cost abstractions, memory safety), scaling standards and resilience. |
| Backend Developer (Scala) | 必要 | Shapes architectural strategy for Scala platform: evolutionary architecture, fitness functions, organizational-level design standards. Defines technology radar, makes build vs buy decisions, designs target architecture considering business strategy and three-year horizon. |
| BI Analyst | Shapes corporate data architecture strategy and reference architectures for the company. Defines long-term technical vision for the analytical platform at the company level. Influences industry standards for enterprise analytics architecture design. | |
| Blockchain Developer | Defines enterprise system architecture for the blockchain platform. Shapes scalability roadmap and technology radar. Publishes blockchain system design patterns and case studies. | |
| Cloud Engineer | 必要 | Shapes cloud platform architectural strategy: domain-driven cloud architecture, platform engineering vision, build vs buy framework. Designs cross-cutting concerns — observability, security, networking — as platform capabilities and defines technology governance. |
| Compiler Engineer | Shapes architectural vision for the compiler ecosystem: unified IR for multi-language support, distributed compilation, architecture for language standard evolution. | |
| Computer Vision Engineer | Defines architectural strategy for the organization's CV platform, designs visual data processing systems at scale. Shapes vision and roadmap for ML infrastructure development. | |
| Data Analyst | Defines architectural strategy for the organization's analytical platform, designs systems processing petabytes of data. Shapes technical vision and infrastructure development roadmap. | |
| Data Engineer | Shapes data platform architecture: organizational data infrastructure, technology selection, architectural governance. | |
| Data Scientist | Shapes system design strategy for the organization's ML platform. Defines enterprise architecture for ML workloads. Evaluates cloud providers and managed services for ML infrastructure. | |
| Database Engineer / DBA | Shapes organizational Data Architecture strategy: DBMS selection standards, data mesh/fabric architecture, integration of analytical and operational data storage systems. | |
| Desktop Developer (.NET WPF/WinUI/MAUI) | Shapes technology strategy for corporate .NET desktop development platform considering MAUI migration. Defines reference architecture for enterprise desktop applications with server integration at organizational scale. | |
| Desktop Developer (Electron/Tauri) | Shapes architectural vision for the company's Electron product ecosystem platform. Defines principles for designing scalable desktop applications with server infrastructure. | |
| Desktop Developer (Qt/C++) | Shapes technology strategy for the corporate Qt desktop development platform considering cross-platform compatibility and scalability. Defines reference architecture for desktop applications with enterprise-scale server integration. | |
| DevOps Engineer | 必要 | Develops architectural strategy for the entire infrastructure platform: patterns for scaling to millions of users, reliability engineering standards. Defines technology radar, architectural principles and governance for all engineering teams. |
| DevSecOps Engineer | Shapes organizational security platform development strategy with platform approach and self-service model. Defines architecture evolution considering cloud-native, zero-trust and supply chain security trends. | |
| Embedded Developer | Shapes architectural strategy for the embedded product line with a platform approach to component reuse. Defines system architecture evolution considering trends in RISC-V, edge AI and 5G. | |
| Engineering Manager | 必要 | Defines organizational architecture strategy: technology selection frameworks, architecture governance policies, and engineering excellence standards. Designs reference architectures for common organizational patterns. Drives architectural decision-making culture and establishes enterprise-wide architecture review processes. |
| Flutter Developer | 必要 | Defines organizational mobile/cross-platform architecture strategy. Designs reference architectures for Flutter applications at enterprise scale. Establishes architecture governance for mobile platforms. Evaluates emerging mobile technologies and frameworks for organizational adoption. Shapes industry practices through thought leadership. |
| Frontend Developer (Angular) | Shapes frontend platform architectural strategy for the organization. Designs an Angular application ecosystem with a unified design system and delivery infrastructure. | |
| Frontend Developer (React) | Shapes architectural vision for the frontend platform of the company's React product ecosystem. Defines principles for designing scalable frontend systems for millions of users. | |
| Frontend Developer (Svelte) | Defines the architectural strategy for the organization's frontend platform. Designs scalable content delivery systems and coordinates architecture between teams. | |
| Frontend Developer (Vue) | Defines architectural vision for the organization's frontend platform. Designs a system of reusable modules and components for dozens of Vue applications with unified infrastructure. | |
| Fullstack Developer | 必要 | Shapes organizational architectural strategy for fullstack development: platform approach, service boundaries, evolution from monolith to microservices. Defines technology radar, creates architecture council and mentors leads on system design. |
| Game Designer | Shapes technology strategy and reference architectures for the studio's game product lineup. Defines long-term technical vision and technology roadmap at the company level. Publishes architectural research and influences industry game system design standards. | |
| Game QA Engineer | Shapes enterprise testing methodology based on system architecture. Defines testing standards for different architectures, integrates architecture review into QA planning. | |
| Game Server Developer | Defines the technical vision for the studio's server platform for 3-5 years. Designs a reusable server platform for multiple game projects with a unified operational model. | |
| Infrastructure Engineer | Shapes organizational infrastructure design strategy with platform approach and self-service model. Defines architecture evolution considering multi-cloud, edge computing and sustainability. | |
| iOS Developer | 必要 | Develops architectural strategy for the organization's iOS platform: standards for all applications, shared SDKs, and reusable modules. Defines scaling principles: from monolithic app to multi-module architecture with independent teams. Implements architectural fitness functions for automatic design principle compliance validation. |
| IoT Engineer | Shapes architectural vision for organizational IoT ecosystem: integration standards for industrial protocols, digital twin architecture, edge computing evolution strategy. | |
| Language Tooling Engineer | Shapes architectural vision for the language tools ecosystem at the organizational level. Defines fundamental design principles influencing the entire development tools industry. | |
| LLM Engineer | Shapes enterprise architecture strategy for LLM platforms. Defines approaches to platform design, cross-team architecture governance, and long-term technical vision for ML/LLM infrastructure. | |
| ML Engineer | Shapes next-generation ML platform architectural strategy: foundation models, multi-modal pipelines, federated learning. Defines evolution considering emerging paradigms: compound AI systems and AI agents. | |
| MLOps Engineer | Shapes the ML platform strategy at the organizational level: unified ML infrastructure for all teams, architecture for heterogeneous hardware (GPU/TPU), cloud-agnostic design. | |
| Network Engineer | Defines the architectural strategy for the organization's network infrastructure for 3-5 years. Designs systems at the scale of tens of thousands of devices considering technology evolution. | |
| NLP Engineer | Shapes ML platform architectural vision at organizational level. Defines fundamental design principles ensuring NLP infrastructure scalability. | |
| Penetration Testing Engineer | Defines architectural security testing strategy for the organization. Shapes threat modeling frameworks and coordinates architectural security reviews across teams. | |
| Performance Testing Engineer | Shapes performance architecture review strategy: standards for evaluating architectural decisions' performance, performance modeling for design decisions, capacity planning frameworks. | |
| Platform Engineer | 必要 | Shapes platform architectural strategy for 3-5 years: platform-as-product, API economy, composable infrastructure. Defines industry-leading approaches to system design. Mentors senior architects and shapes organizational architecture culture. Influences industry through publications. |
| Product Manager | 必要 | Defines technology strategy jointly with the CTO. Makes platform decisions based on product strategy. |
| QA Automation Engineer | Shapes testing strategy for the organization's architectural platform. Designs scalable test infrastructure supporting hundreds of microservices and thousands of tests. | |
| QA Engineer (Manual) | Shapes corporate QA methodology based on systematic architecture analysis. Defines testability requirement standards for various architecture types. Publishes research on architecture-driven QA strategy effectiveness. | |
| QA Security Engineer | Shapes security testing strategy at the system design level for the entire organization. Defines shift-left security testing principles and QA integration into the architectural design process. | |
| React Native Developer | 必要 | Shapes enterprise mobile application architecture. Defines strategy — React Native vs Native vs Hybrid for different products. Designs platform architecture — shared SDK, design system, common services. Coordinates architectural standards across the organization's mobile teams. |
| Release Engineer | Shapes architectural strategy for building global release platforms. Designs multi-regional delivery systems with consistency guarantees and minimal deployment time. | |
| Security Analyst | Shapes the strategy for designing security platforms across the entire organization. Creates reference architectures for SOC, SIEM, and automated incident response systems. | |
| Site Reliability Engineer (SRE) | 必要 | Defines organizational architecture strategy: reference architecture for reliable systems, platform abstractions, cross-team design patterns. Shapes reliability engineering culture. |
| Smart Contract Developer | Defines enterprise contract system architecture strategy. Shapes scalability and extensibility patterns for smart contract platforms. Publishes system design case studies. | |
| Solutions Architect | 必要 | Defines organizational architecture strategy: reference architectures for common business domains, architecture principles aligned with business strategy, and technology investment roadmap. Designs architecture governance at enterprise level. Drives industry influence through publications, conference talks, and standards contributions. |
| Systems Programmer (C/C++) | 必要 | Shapes enterprise system architecture for the organization. Defines reference architecture for different classes of system software, mentors lead system architects. |
| Technical Lead | 必要 | Defines organizational architecture strategy: establishes reference architectures, architecture governance framework, and technology selection criteria. Designs architecture for enterprise-scale systems with focus on long-term evolution and sustainability. Drives architectural excellence across the organization through mentoring leads and establishing best practices. |
| Technical Product Manager | 必要 | Shapes enterprise architecture vision with product-technology alignment. Defines architectural principles for the organization. Coordinates cross-team architecture evolution. Builds technical advisory function for the product organization. |
| Technical Writer | Shapes technical architecture documentation strategy at the corporate level. Defines how system design documentation supports technology strategy and investment decisions. | |
| Telecom Developer | Shapes architectural strategy for the next-generation telecom platform: 5G core, network slicing, MEC. Defines system architecture evolution considering disaggregation and O-RAN open standards. | |
| Unity Developer | 必要 | Defines system architecture at studio level. Shapes technology platform for Unity development. Evaluates architectural patterns for new project types. |
| Unreal Engine Developer | 必要 | Defines system architecture at studio level. Shapes technology platform. Defines reusable systems and shared infrastructure for Unreal projects. |
| XR Unity Developer | Shapes architectural vision for the platform across the company's entire XR product ecosystem. Defines system design principles capable of serving millions of concurrent XR users. |