领域
Programming Fundamentals
技能档案
GoF patterns: Factory, Strategy, Observer, Decorator, Repository, etc.
角色数
70
包含此技能的角色
级别数
5
结构化成长路径
必要要求
145
其余 201 个可选
Programming Fundamentals
OOP & Design Patterns
2026/3/17
选择当前级别并对比期望。下方卡片显示晋升所需掌握的内容。
表格展示从初级到首席的技能深度变化。点击行查看详情。
| 角色 | 必要性 | 描述 |
|---|---|---|
| 1C Developer | Understands the fundamentals of Design Patterns at a basic level. Applies simple concepts in work tasks using 1С:Предприятие. Follows recommendations from senior developers when solving problems. | |
| AI Product Engineer | Understands the fundamentals of Design Patterns at a basic level. Applies simple concepts in work tasks using Python/TypeScript. Follows recommendations from senior developers when solving problems. | |
| Analytics Engineer | Getting familiar with main design patterns applicable to analytics engineering — Factory, Strategy, Observer. Understands how patterns help organize data pipeline and transformation code. | |
| Android Developer | Understands the fundamentals of Design Patterns at a basic level. Applies simple concepts in work tasks using Kotlin. Follows recommendations from senior developers when solving problems. | |
| Application Security Engineer | Knows main design patterns and their application in developing secure software. Understands Strategy and Observer patterns in the context of application security components. | |
| AR/VR Developer | 必要 | Knows basic patterns (Singleton, Observer, Factory) and applies them in XR development. Uses Observer for event-driven VR interactions. Understands the Component pattern in Unity. |
| Backend Developer (C#/.NET) | 必要 | Understands basic design patterns in C#/.NET: Singleton, Factory, Repository pattern in ASP.NET Core, dependency injection fundamentals with built-in DI container. Follows team conventions for pattern usage in .NET solution architecture. |
| Backend Developer (Elixir) | 必要 | Understands the fundamentals of Design Patterns at a basic level. Applies simple concepts in work tasks using Elixir. Follows recommendations from senior developers when solving problems. |
| Backend Developer (Go) | 必要 | Understands the fundamentals of Design Patterns at a basic level. Applies simple concepts in work tasks using Go. Follows recommendations from senior developers when solving problems. |
| Backend Developer (Java/Kotlin) | 必要 | Understands basic design patterns in Java: Singleton, Factory Method, Builder pattern, Observer in event handling, dependency injection with Spring IoC container. Follows team conventions for pattern usage in Spring Boot applications. |
| Backend Developer (Node.js) | 必要 | Understands the fundamentals of Design Patterns at a basic level. Applies simple concepts in work tasks using Node.js 20+/TypeScript. Follows recommendations from senior developers when solving problems. |
| Backend Developer (PHP) | 必要 | Knows and applies basic patterns: Singleton, Factory, Strategy. Understands why dependency injection is needed. Uses Repository for database operations. Follows patterns adopted in the project. |
| Backend Developer (Python) | 必要 | Knows basic patterns: Singleton, Factory, Observer. Understands the purpose of Repository and Service Layer. Can recognize patterns in existing code. Applies simple patterns on senior's recommendation. |
| Backend Developer (Rust) | 必要 | Understands the fundamentals of Design Patterns at a basic level. Applies simple concepts in work tasks using Rust. Follows recommendations from senior developers when solving problems. |
| Backend Developer (Scala) | 必要 | Understands the fundamentals of Design Patterns at a basic level. Applies simple concepts in work tasks using Scala 3. Follows recommendations from senior developers when solving problems. |
| BI Analyst | Knows basic design patterns for structuring analytical code: Factory, Strategy. Understands the purpose of patterns for creating modular ETL components and analytical tools. Applies simple patterns for organizing data loading and transformation code. | |
| Blockchain Developer | Knows basic design patterns: Factory, Observer, Strategy. Applies Factory for node component creation. Uses Observer for event-driven interaction between modules. | |
| Cloud Engineer | Applies basic patterns in cloud context: Singleton for SDK clients, Factory for resource creation. Understands retry and circuit breaker patterns for cloud calls. | |
| Compiler Engineer | Knows basic design pattern concepts for compiler engineering and can apply them in common tasks. Uses standard tools and follows established team practices. Understands when and why this approach is used. | |
| Computer Vision Engineer | Knows basic design patterns and can recognize Factory, Strategy in CV pipeline code. Understands pattern application for organizing image processing code. | |
| Data Analyst | Knows basic design patterns — Singleton, Factory, Observer — and understands their application in creating analytical tools. Can recognize patterns in existing code. | |
| Data Engineer | Applies patterns in data engineering: ETL vs ELT pattern, batch vs streaming. Understands data pipeline patterns and their application. | |
| Data Scientist | Applies patterns in DS: Pipeline pattern for data processing, Strategy for model selection. Organizes ML code. | |
| Database Engineer / DBA | Knows fundamental design patterns: Singleton, Observer, Factory. Understands how patterns apply when creating DBA tools and database automation scripts. | |
| Desktop Developer (.NET WPF/WinUI/MAUI) | Knows patterns in .NET: Observer (INotifyPropertyChanged), Singleton (DI singleton), Factory (IServiceProvider). Applies Command through ICommand/RelayCommand in WPF/WinUI. Uses Repository pattern. | |
| Desktop Developer (Electron/Tauri) | Knows patterns in TypeScript/Electron: Observer (EventEmitter), Singleton (main process services), Factory (window creation). Applies Module pattern for IPC handlers. | |
| Desktop Developer (Qt/C++) | Knows Observer (signals/slots), Singleton (Q_GLOBAL_STATIC), Factory patterns in the Qt context. Applies Strategy through C++17 functors and lambdas. Uses Builder for widget configuration. | |
| DevOps Engineer | Applies patterns in DevOps: Singleton for configuration, Factory for resource creation. Understands infrastructure patterns: blue-green, canary. | |
| DevSecOps Engineer | Knows basic design patterns: Singleton, Observer, Factory. Understands their application in DevSecOps context for creating reusable security components and utilities. | |
| Embedded Developer | Knows basic patterns for embedded: State Machine, Observer, Singleton for hardware resources. Applies under mentor guidance. | |
| Flutter Developer | Understands the fundamentals of Design Patterns at a basic level. Applies simple concepts in work tasks using Dart. Follows recommendations from senior developers when solving problems. | |
| Frontend Developer (Angular) | 必要 | Applies basic Angular patterns: component-based approach, dependency injection via constructor, smart/dumb component separation. Uses services as singletons via providedIn: root. |
| Frontend Developer (React) | 必要 | Applies basic React patterns: component composition, props drilling, conditional rendering. Understands the separation of presentational and container components, uses children and render props for logic reuse. |
| Frontend Developer (Svelte) | 必要 | Applies basic patterns in Svelte: component composition, prop and slot forwarding, using $props() for input data destructuring. Understands the container/presentation pattern for separating logic and display in components. |
| Frontend Developer (Vue) | 必要 | Applies basic Vue 3 patterns — props/emit for component communication, provide/inject for dependency injection. Uses Composition API for extracting repeating logic into composable functions. |
| Fullstack Developer | 必要 | Understands the fundamentals of Design Patterns at a basic level. Applies simple concepts in work tasks using TypeScript/Python. Follows recommendations from senior developers when solving problems. |
| Game Designer | Knows basic design patterns: Singleton, Observer, Factory in the context of game systems. Understands pattern applications for organizing game code: scene managers, object pools. Can recognize typical patterns in game engine codebase. | |
| Game QA Engineer | Applies patterns in game QA: Page Object, Test Data Builder, Fixture patterns. Organizes test code using patterns. | |
| Game Server Developer | Understands the fundamentals of Design Patterns at a basic level. Applies simple concepts in work tasks using C++/Go/C#. Follows recommendations from senior developers when solving problems. | |
| Infrastructure Engineer | Knows main design patterns and understands their application in infrastructure context. Uses Template Method and Factory patterns when writing infrastructure automation scripts. | |
| iOS Developer | Understands basic design patterns in iOS/Swift: MVC/MVVM architecture patterns, Delegate and Protocol patterns, Observer with NotificationCenter/Combine, Singleton for shared services. Follows team conventions for pattern usage in UIKit/SwiftUI applications. | |
| IoT Engineer | Knows fundamental design patterns: Singleton, Observer, Factory. Understands how these patterns apply in IoT: Observer for sensor events, Factory for driver creation. | |
| Language Tooling Engineer | Understands the fundamentals of Design Patterns at a basic level. Applies simple concepts in work tasks using TypeScript/Rust. Follows recommendations from senior developers when solving problems. | |
| LLM Engineer | Knows basic design patterns: Strategy, Factory, Observer. Applies them when writing simple LLM pipeline components: data loaders, prompt formatters. | |
| ML Engineer | Knows basic patterns: Factory, Strategy, Observer. Understands how sklearn uses patterns (Pipeline, Transformer). Uses existing patterns in ML code. | |
| MLOps Engineer | Understands the fundamentals of Design Patterns at a basic level. Applies simple concepts in work tasks using Python. Follows recommendations from senior developers when solving problems. | |
| Network Engineer | Knows basic design patterns — Singleton, Factory, Observer. Understands their application in the context of network applications for creating connections and handling events. | |
| NLP Engineer | Knows fundamental design patterns and applies them when developing NLP components. Uses Strategy for model selection, Factory for text handler creation, and Pipeline for chains. | |
| Penetration Testing Engineer | Knows basic design patterns and can recognize their application in security tool architecture. Understands Factory and Strategy for modular scanners. | |
| Performance Testing Engineer | Knows fundamental design patterns: Factory, Strategy, Observer. Understands how patterns apply when creating test scripts and load generators in performance projects. | |
| Platform Engineer | Understands the fundamentals of Design Patterns at a basic level. Applies simple concepts in work tasks using Go/Python/HCL. Follows recommendations from senior developers when solving problems. | |
| Product Manager | Knows basic design patterns for understanding technical discussions with the development team. Understands the impact of architectural decisions on development speed and product flexibility. Uses knowledge for more precise communication of technical requirements. | |
| QA Automation Engineer | Understands the fundamentals of Design Patterns at a basic level. Applies simple concepts in work tasks using Python/Java/TypeScript. Follows recommendations from senior developers when solving problems. | |
| QA Engineer (Manual) | Knows basic design patterns for understanding tested application architecture. Understands pattern purposes for writing more targeted test cases and identifying design-related defects. | |
| QA Security Engineer | Knows basic design patterns and their application in creating security test frameworks. Understands Page Object and Strategy for organizing application security tests. | |
| React Native Developer | Applies basic React patterns — functional components, useState/useEffect hooks, props drilling. Understands the Container/Presentational pattern for separating logic and UI in React Native screens. Uses component composition for reusing UI elements in the mobile app. | |
| Release Engineer | Studies fundamental design patterns — Strategy, Observer, Factory. Recognizes their application in existing release management tools and deployment scripts. | |
| Security Analyst | Studies basic design patterns and their application in security tools. Recognizes Observer for monitoring and Strategy for different vulnerability analysis methods. | |
| Site Reliability Engineer (SRE) | Applies patterns in SRE context: Circuit Breaker for resilience, Retry for fault tolerance. Understands architectural patterns for reliable systems. | |
| Smart Contract Developer | Applies basic Solidity patterns: Ownable, Pausable, ReentrancyGuard. Uses Factory and Clones (EIP-1167) for contract creation. Follows the checks-effects-interactions pattern. | |
| Systems Programmer (C/C++) | 必要 | Knows patterns for system software: RAII, Pimpl, Singleton for global state, Observer for event systems. Applies under guidance. |
| Technical Product Manager | Knows main design patterns at a level sufficient to understand team technical discussions. Understands why patterns are important for product extensibility and maintainability. | |
| Technical Writer | Knows basic design patterns and can correctly use their names in technical documentation. Understands the purpose of main patterns for accurately describing architectural decisions in API references. Creates simple pattern diagrams for architecture visualization in guides. | |
| Telecom Developer | Understands the fundamentals of Design Patterns at a basic level. Applies simple concepts in work tasks using C++/Java/Python. Follows recommendations from senior developers when solving problems. | |
| Unity Developer | Applies basic design patterns in Unity: Singleton for managers (GameManager, AudioManager), Observer via UnityEvents, Object Pool for bullets and effects. | |
| Unreal Engine Developer | Applies Unreal-specific patterns: GameplayAbility for ability systems, Components for composition, Subsystems for services. Uses delegates and interfaces for decoupling. | |
| XR Unity Developer | 必要 | Knows basic patterns and applies them in Unity XR: Singleton (AudioManager), Observer (events), Factory. Uses Unity-specific patterns (MonoBehaviour, ScriptableObject). |
| 角色 | 必要性 | 描述 |
|---|---|---|
| 1C Developer | Independently applies design patterns for 1C development: adapter patterns for external system integration, strategy pattern for interchangeable business rule implementations, template method for standardized document processing. Explains pattern choices in code review for 1C configurations. | |
| AI Product Engineer | Independently applies design patterns for AI products: strategy pattern for interchangeable model backends, pipeline pattern for ML data processing stages, factory pattern for model instantiation. Explains pattern trade-offs for ML system extensibility in code review. | |
| Analytics Engineer | Applies design patterns in analytics systems — Strategy for transformation selection, Factory for connector creation, Pipeline for processing chains. Structures dbt project code using template patterns. | |
| Android Developer | Independently applies design patterns for Android: MVVM with LiveData/StateFlow, Repository pattern for data layer abstraction, Builder for complex view configuration, Observer for reactive UI updates. Explains pattern choices for Android architecture in code review. | |
| Application Security Engineer | Applies design patterns for creating extensible security systems: Chain of Responsibility for request filtering, Decorator for adding security layers to existing logic. | |
| AR/VR Developer | 必要 | Applies design patterns for XR: State Machine for VR states, Command for undo/redo, Object Pool for VR objects. Selects appropriate patterns for specific XR tasks. |
| Backend Developer (C#/.NET) | 必要 | Independently applies design patterns in C#/.NET: mediator with MediatR for CQRS, decorator for cross-cutting concerns, repository and unit of work for data access, specification pattern for query building. Understands trade-offs between patterns and YAGNI in .NET applications. |
| Backend Developer (Elixir) | 必要 | Independently applies design patterns for Elixir: GenServer for stateful processes, Supervisor trees for fault tolerance, pipeline pattern with |> operator for data transformations, behaviour callbacks for polymorphism. Explains pattern trade-offs for OTP-based architectures. |
| Backend Developer (Go) | 必要 | Independently applies design patterns for Go: interface-based strategy and adapter patterns, functional options for configuration, middleware pattern for HTTP handling, channel-based observer/pub-sub. Explains Go-idiomatic pattern alternatives in code review. |
| Backend Developer (Java/Kotlin) | 必要 | Independently applies design patterns in Java: strategy with Spring profiles, template method for service workflows, decorator for stream processing, observer with Spring Events. Understands trade-offs between design patterns and framework conventions in Spring Boot. |
| Backend Developer (Node.js) | 必要 | Independently applies design patterns for Node.js: middleware chain pattern in Express/Fastify, observer with EventEmitter, factory for service instantiation, strategy for pluggable implementations. Explains pattern trade-offs for async-first Node.js architectures. |
| Backend Developer (PHP) | 必要 | Applies patterns deliberately: Observer for events, Decorator for extending functionality, Chain of Responsibility for middleware. Refactors code using appropriate patterns. Understands anti-patterns. |
| Backend Developer (Python) | 必要 | Applies Strategy, Template Method, Decorator, Command in Python code. Uses Repository pattern for database access. Applies Unit of Work with SQLAlchemy sessions. Knows antipatterns and can refactor them. |
| Backend Developer (Rust) | 必要 | Independently applies design patterns for Rust: trait-based strategy and visitor patterns, builder for complex struct construction, newtype pattern for type safety, state machine pattern with enums. Explains Rust-specific pattern choices considering ownership and lifetimes. |
| Backend Developer (Scala) | 必要 | Independently applies design patterns for Scala: type class pattern for ad-hoc polymorphism, cake pattern for dependency injection, monad transformers for composable effects, sealed trait hierarchies for algebraic data types. Explains FP-oriented pattern alternatives. |
| BI Analyst | Applies design patterns for creating flexible ETL pipelines: Pipeline, Builder, Adapter. Uses Strategy for switching between data sources and aggregation methods. Implements Observer for data quality monitoring and automatic anomaly alerting. | |
| Blockchain Developer | Applies patterns for distributed systems: Circuit Breaker, Retry, Bulkhead for P2P communication. Implements Pipeline pattern for transaction and block processing in node software. | |
| Cloud Engineer | Uses cloud-specific patterns: Sidecar for service mesh, Ambassador for API routing, Circuit Breaker for resilience. Implements Strangler Fig for cloud migration. | |
| Compiler Engineer | Confidently applies design patterns for compiler engineering in non-standard tasks. Independently selects optimal approach and tools. Analyzes trade-offs and suggests improvements to existing solutions. | |
| Computer Vision Engineer | Applies Pipeline, Strategy, and Builder patterns for building flexible CV image processing pipelines. Uses Registry pattern for managing models and augmentations. | |
| Data Analyst | Applies Strategy, Template Method, and Pipeline patterns for building flexible ETL processes. Uses Repository pattern for abstracting access to various data sources. | |
| Data Engineer | Uses data patterns: slowly changing dimensions, change data capture, star/snowflake schema. Implements idempotent pipelines. | |
| Data Scientist | Uses ML design patterns: feature store pattern, model registry, experiment tracking. Implements reproducible pipelines. | |
| Database Engineer / DBA | Applies design patterns in DBA tools: Repository for DBMS metadata access, Strategy for different backup strategies, Observer for database event monitoring. | |
| Desktop Developer (.NET WPF/WinUI/MAUI) | Implements MVVM with Command, Mediator (MediatR), Observer. Applies Strategy through DI for swappable algorithms. Uses Decorator for cross-cutting concerns (logging, caching). Understands Unit of Work with EF Core. | |
| Desktop Developer (Electron/Tauri) | Implements patterns for Electron: Mediator for IPC, Repository for data access, Strategy for platform-specific code. Applies Builder for complex configuration. Uses Proxy for IPC abstraction. | |
| Desktop Developer (Qt/C++) | Implements MVC/MVVM through Qt Model/View Framework. Applies Command for undo/redo (QUndoStack). Uses Decorator for extending QWidget functionality. Understands Composite in Qt widget tree. | |
| DevOps Engineer | Uses DevOps patterns: GitOps, Infrastructure as Code, immutable infrastructure. Implements pipeline patterns: fan-out/fan-in, matrix builds. | |
| DevSecOps Engineer | Applies Chain of Responsibility for security middleware, Strategy for scanner selection and Observer for alert systems. Uses Decorator for adding security layers to existing components. | |
| Embedded Developer | Applies design patterns in embedded: State Machine, Observer for event handling, Command for control interfaces, Strategy for algorithm selection. Benchmarks pattern overhead on target hardware. | |
| Engineering Manager | Independently evaluates design pattern usage in team projects: reviews architectural decisions for appropriate pattern application, identifies over-engineering vs under-abstraction in codebases, facilitates discussions on pattern trade-offs. Explains design pattern implications for team maintenance and onboarding. | |
| Flutter Developer | Independently applies design patterns for Flutter: BLoC/Cubit pattern for state management, Repository pattern for data layer, factory pattern for widget creation, observer with Streams for reactive updates. Explains pattern trade-offs for Flutter app architecture. | |
| Frontend Developer (Angular) | 必要 | Uses GoF patterns in Angular context: Observer via RxJS/signals, Strategy via DI tokens, Facade for simplifying service APIs. Applies Container/Presentational component separation. |
| Frontend Developer (React) | 必要 | Proficient in advanced React patterns: compound components, render props, HOC, custom hooks for logic reuse. Applies provider pattern through React Context and Zustand for state management, uses TypeScript generics for type-safe components. |
| Frontend Developer (Svelte) | 必要 | Implements Svelte 5 patterns: compound components through snippets, render delegation, context API for dependency injection. Applies the action pattern (use:action) for reusable DOM logic, designs adaptive layouts in SvelteKit. |
| Frontend Developer (Vue) | 必要 | Implements Renderless Components, Compound Components and Headless UI patterns in Vue 3. Designs reusable composables with inversion of control, applies Strategy and Observer through Vue reactivity system. |
| Fullstack Developer | 必要 | Independently applies design patterns across full stack: repository pattern for backend data access, strategy for interchangeable service implementations, observer for frontend reactivity, adapter for API integration layers. Explains pattern trade-offs for full-stack architecture coherence. |
| Game Designer | Applies game design patterns: State Machine, Command, Strategy for AI and gameplay. Uses Component/ECS for flexible game entity architecture and modularity. Combines patterns for specific tasks: quest system, dialogue trees, combat system. | |
| Game QA Engineer | Uses QA patterns: Strategy for multi-platform testing, Observer for event monitoring, Factory for test data generation. | |
| Game Server Developer | Independently applies design patterns for game servers: state pattern for game entity behavior, observer for event-driven game systems, command pattern for player action processing, object pool for performance-critical entity management. Explains pattern trade-offs for real-time game server architectures. | |
| Infrastructure Engineer | Applies Builder pattern for constructing complex infrastructure configurations and Adapter for cloud integrations. Uses Strategy for deployment strategy selection: blue-green, canary, rolling update. | |
| iOS Developer | Independently applies design patterns in iOS/Swift: coordinator pattern for navigation, MVVM with Combine/RxSwift for reactive data flow, protocol-oriented programming for composition, dependency injection with property wrappers. Understands trade-offs between UIKit and SwiftUI pattern approaches. | |
| IoT Engineer | Applies design patterns in IoT systems: State Machine for device control, Publisher-Subscriber for telemetry, Command for remote actuator management. | |
| Language Tooling Engineer | Independently applies design patterns for language tooling: visitor pattern for AST traversal, interpreter pattern for expression evaluation, composite for tree structures, strategy for pluggable compiler passes. Explains pattern trade-offs for extensible compiler architectures. | |
| LLM Engineer | Independently applies design patterns for LLM applications: chain of responsibility for prompt processing pipelines, strategy for interchangeable model providers, adapter for different embedding backends, observer for streaming response handling. Understands trade-offs between pattern complexity and LLM application maintainability. | |
| ML Engineer | Applies patterns in ML context: Strategy for model selection, Factory for feature pipeline creation, Observer for monitoring. Writes configurable ML components using Template Method. | |
| MLOps Engineer | Independently applies design patterns for MLOps: pipeline pattern for ML workflow orchestration, strategy for interchangeable model training backends, factory for pipeline step instantiation, observer for experiment tracking events. Explains pattern trade-offs for ML infrastructure extensibility. | |
| Network Engineer | Applies Strategy, Adapter, Template Method patterns for working with heterogeneous network equipment. Uses Chain of Responsibility for processing network events and alerts. | |
| NLP Engineer | Applies architectural patterns for building modular NLP systems. Implements Chain of Responsibility for text processing stages, Observer for model monitoring, and Adapter for integrations. | |
| Penetration Testing Engineer | Applies Plugin, Strategy, and Chain of Responsibility patterns when creating modular pentest frameworks. Uses Observer for scan result monitoring. | |
| Performance Testing Engineer | Applies patterns in load testing tools: Strategy for different load models (ramp-up, spike, soak), Builder for constructing scenarios, Observer for metric collection. | |
| Platform Engineer | Independently applies design patterns for platform engineering: strategy pattern for pluggable infrastructure providers, template method for standardized deployment pipelines, adapter for multi-cloud service abstraction, observer for platform event propagation. Explains pattern trade-offs for platform API design. | |
| Product Manager | Uses pattern understanding to evaluate technical proposals and their impact on product flexibility. Evaluates architectural decisions through the lens of product metrics: time-to-market, extensibility, maintainability. Includes architectural considerations in the product decision-making process. | |
| QA Automation Engineer | Independently applies design patterns for test automation: page object pattern for UI test abstraction, strategy for cross-browser/cross-platform test execution, builder for test data construction, factory for test environment setup. Explains pattern trade-offs for maintainable test architecture. | |
| QA Engineer (Manual) | Analyzes applied patterns in tested systems for designing effective test cases. Uses State Machine knowledge for testing workflows, Strategy for verifying behavior variations. Creates testing checklists based on analysis of component architectural patterns. | |
| QA Security Engineer | Applies design patterns for building extensible test frameworks: Builder for constructing test data, Factory for creating different types of security scanners. | |
| React Native Developer | Implements Custom Hooks patterns for encapsulating business logic. Applies Observer via Zustand subscriptions, Provider via React Context. Uses Adapter for native module integration. Implements Repository pattern for abstracting data sources — API, AsyncStorage, MMKV. | |
| Release Engineer | Applies design patterns to create flexible release pipelines. Uses Strategy pattern for different deployment strategies and Observer for release status notifications. | |
| Security Analyst | Applies patterns for building flexible security systems — Chain of Responsibility for threat filtering, Builder for constructing complex detection rules. | |
| Site Reliability Engineer (SRE) | Uses reliability patterns: Bulkhead for isolation, Saga for distributed recovery, Sidecar for observability. Implements self-healing patterns. | |
| Smart Contract Developer | Applies advanced smart contract patterns: Proxy (UUPS/Transparent), Diamond (EIP-2535), Pull Payment, Commit-Reveal. Designs modular contracts with interface segregation. | |
| Systems Programmer (C/C++) | 必要 | Applies system patterns: Flyweight for memory optimization, Reactor for I/O multiplexing, Chain of Responsibility for packet processing. |
| Technical Lead | Independently evaluates and guides design pattern usage: reviews architectural decisions for appropriate abstraction levels, identifies pattern misuse and over-engineering, facilitates team discussions on pattern trade-offs for maintainability. Explains design pattern implications for system evolution and developer productivity. | |
| Technical Product Manager | Uses pattern knowledge for evaluating technical decisions — strategy for A/B tests, observer for notifications, factory for creating different content types in the product. | |
| Technical Writer | Documents design pattern usage in product architecture with examples and rationale. Creates architectural guides describing pattern choices and their trade-offs for developers. Develops a project pattern catalog with code examples and usage recommendations. | |
| Telecom Developer | Independently applies design patterns for telecom systems: state machine pattern for call state management, observer for signaling event processing, chain of responsibility for protocol message handling, strategy for codec selection. Explains pattern trade-offs for telecom protocol implementations. | |
| Unity Developer | Applies advanced patterns in Unity: State Machine for AI and UI transitions, Command for undo/redo, Strategy for swappable NPC behaviors. Uses ScriptableObjects as Dependency Injection containers. | |
| Unreal Engine Developer | Applies advanced Unreal patterns: Gameplay Ability System (GAS), Data-Driven Design via DataTables, Async patterns with Latent Actions. Uses Gameplay Tags for flexible categorization. | |
| XR Unity Developer | 必要 | Applies patterns for Unity XR: State Machine for VR states, Object Pool for XR objects, Command for undo. Selects appropriate patterns. |
| 角色 | 必要性 | 描述 |
|---|---|---|
| 1C Developer | 必要 | Has deep expertise in design patterns for 1C systems: designs extensible architectures using adapter and facade patterns for complex integrations, implements domain-driven patterns for business logic in 1C configurations, optimizes pattern usage for 1C platform constraints. Mentors team on architectural patterns for enterprise 1C applications. |
| AI Product Engineer | 必要 | Has deep expertise in design patterns for AI systems: designs extensible ML architectures with strategy and pipeline patterns, implements plugin systems for model backends and data processors, optimizes pattern usage for ML system performance. Mentors team on architectural patterns for production AI applications. |
| Analytics Engineer | Architects analytics platforms using architectural patterns — Mediator for orchestration, Repository for storage abstraction. Creates extensible frameworks for typical analytics tasks with plug-in architecture. | |
| Android Developer | 必要 | Has deep expertise in design patterns for Android: designs clean architecture with dependency injection and use case patterns, implements reactive data flow architectures, optimizes pattern usage for Android lifecycle and performance. Mentors team on architectural patterns for scalable Android applications. |
| Application Security Engineer | Designs security frameworks using advanced patterns: Proxy for access control, Specification for flexible authorization rules. Creates reusable security components. | |
| AR/VR Developer | 必要 | Designs custom architectural patterns for XR. Combines patterns for complex XR systems. Adapts patterns to real-time XR constraints. |
| Backend Developer (C#/.NET) | 必要 | Has deep expertise in design patterns for .NET: designs domain-driven architectures with aggregate roots and bounded contexts, implements CQRS/ES patterns for complex business domains, optimizes pattern usage for .NET runtime performance. Mentors team on enterprise patterns for high-load .NET systems. |
| Backend Developer (Elixir) | 必要 | Has deep expertise in design patterns for Elixir/OTP: designs fault-tolerant architectures with supervision strategies, implements domain-driven patterns adapted for functional programming, optimizes GenServer and process patterns for scalability. Mentors team on OTP design patterns for distributed Elixir systems. |
| Backend Developer (Go) | 必要 | Has deep expertise in design patterns for Go: designs clean architectures with interface-driven abstractions, implements Go-idiomatic patterns replacing classical OOP approaches, optimizes concurrent patterns with goroutines and channels. Mentors team on Go-specific architectural patterns for production systems. |
| Backend Developer (Java/Kotlin) | 必要 | Has deep expertise in design patterns for Java: designs domain-driven architectures with DDD tactical patterns, implements hexagonal architecture for testable business logic, optimizes pattern usage for JVM performance. Mentors team on enterprise Java patterns for microservice architectures. |
| Backend Developer (Node.js) | 必要 | Has deep expertise in design patterns for Node.js: designs event-driven architectures with pub/sub and CQRS, implements middleware composition for complex request pipelines, optimizes async patterns for Node.js concurrency model. Mentors team on architectural patterns for scalable Node.js microservices. |
| Backend Developer (PHP) | 必要 | Combines patterns for complex problems: CQRS for read/write separation, Event Sourcing for audit, Specification for complex filters. Adapts patterns to project context rather than applying dogmatically. |
| Backend Developer (Python) | 必要 | Combines patterns for complex architectural tasks. Applies CQRS, Event Sourcing, Specification pattern. Designs middleware pipelines. Adapts classic patterns to Python idioms (decorators, context managers, generators). |
| Backend Developer (Rust) | 必要 | Has deep expertise in design patterns for Rust: designs zero-cost abstractions with trait objects and generics, implements type-safe state machines and builder patterns, optimizes pattern usage considering ownership and borrow checker. Mentors team on Rust-idiomatic patterns for systems programming. |
| Backend Developer (Scala) | 必要 | Has deep expertise in design patterns for Scala: designs effect-based architectures with ZIO/Cats Effect, implements type-level programming patterns for compile-time safety, optimizes functional patterns for JVM performance. Mentors team on FP design patterns for production Scala systems. |
| BI Analyst | Designs analytical frameworks using advanced patterns: Abstract Factory for connectors, Mediator for orchestration. Creates architectural solutions for scalable data platforms applying CQRS and Event Sourcing. Defines custom patterns for BI domain-specific tasks. | |
| Blockchain Developer | Designs architectural patterns for blockchain infrastructure: plugin architecture for consensus modules, event sourcing for state management, CQRS for node API. | |
| Cloud Engineer | Designs cloud architecture using patterns: CQRS for event-driven systems, Saga for distributed transactions, Bulkhead for isolation. Combines patterns for reliability. | |
| Compiler Engineer | Expertly applies design patterns for compiler engineering in designing complex systems. Optimizes existing solutions and prevents architectural mistakes. Conducts code reviews and trains colleagues on best practices. | |
| Computer Vision Engineer | Designs CV system architecture using complex patterns — Plugin, Chain of Responsibility, Mediator. Creates extensible frameworks for model experimentation. | |
| Data Analyst | Designs analytical system architecture using complex patterns — Mediator, Chain of Responsibility, Visitor. Adapts patterns for data processing and aggregation specifics. | |
| Data Engineer | Designs data architecture using patterns: data mesh, data lakehouse, event-driven data. Combines patterns for scalable data platform. | |
| Data Scientist | Designs ML architecture using patterns: ML platform patterns, model serving architecture, feature engineering patterns. | |
| Database Engineer / DBA | Designs DBA tools using advanced patterns: Chain of Responsibility for alert escalation, State Machine for database lifecycle management, Decorator for query auditing. | |
| Desktop Developer (.NET WPF/WinUI/MAUI) | 必要 | Designs architecture with State (Stateless library), Event Sourcing, CQRS. Implements Pipeline through MediatR behaviours. Applies Specification pattern for complex queries. Creates domain-driven design. |
| Desktop Developer (Electron/Tauri) | 必要 | Designs architecture with Plugin pattern, Event Sourcing for undo/redo, CQRS for data flow. Implements Pipeline for data processing. Applies Microkernel for extensible desktop. |
| Desktop Developer (Qt/C++) | 必要 | Designs architecture with State Machine (QStateMachine) for complex workflows. Applies Event Sourcing for offline-sync. Uses Mediator for component decoupling. Implements Plugin pattern. |
| DevOps Engineer | Designs DevOps architecture: pipeline-as-code, self-service platforms, deployment patterns. Combines patterns for reliable delivery. | |
| DevSecOps Engineer | Designs security tools using Pipeline, Plugin and Visitor patterns for extensible code analysis. Introduces Circuit Breaker for fault-tolerant integration with external security services. | |
| Embedded Developer | Designs firmware using embedded patterns: Active Object, Hierarchical State Machine (QP framework), Reactor for event-driven systems. | |
| Engineering Manager | 必要 | Has deep expertise in evaluating design pattern usage across teams: reviews architectural decisions for pattern appropriateness at scale, identifies systemic over-engineering or under-abstraction patterns, designs training programs for pattern competency. Mentors leads on balancing pattern rigor with pragmatic delivery. |
| Flutter Developer | 必要 | Has deep expertise in design patterns for Flutter: designs clean architecture with BLoC/Riverpod state management, implements repository and use case patterns for testable mobile apps, optimizes pattern usage for Flutter widget tree performance. Mentors team on architectural patterns for large-scale Flutter applications. |
| Frontend Developer (Angular) | 必要 | Designs architectural patterns for Angular: Feature Shell via standalone components, Mediator via NgRx Effects, Adapter for integrating third-party libraries with Angular DI and reactive stack. |
| Frontend Developer (React) | 必要 | Designs React application architectural patterns: modular structure with feature-sliced approach, dependency inversion through DI containers. Creates libraries of reusable hooks and headless components based on Radix UI. |
| Frontend Developer (Svelte) | 必要 | Designs architectural patterns for scalable Svelte applications: headless components, machine patterns for complex state, plugin architecture. Creates abstractions over SvelteKit hooks and middleware for cross-cutting concerns. |
| Frontend Developer (Vue) | 必要 | Designs architectural patterns for large-scale Vue applications — Plugin Architecture, Micro-frontend integration through Module Federation. Creates abstractions over Pinia for complex domain models with CQRS approach. |
| Fullstack Developer | 必要 | Has deep expertise in design patterns across full stack: designs cohesive architectures bridging frontend and backend patterns, implements API contract patterns for service integration, optimizes pattern usage for end-to-end system performance. Mentors team on full-stack architectural patterns for production applications. |
| Game Designer | Designs game system architecture with deep understanding of pattern trade-offs. Adapts classic patterns for game development constraints: performance, memory layout, GC pressure. Creates custom architectural solutions combining patterns for unique game mechanics. | |
| Game QA Engineer | Designs test architecture using patterns: extensible frameworks, plugin architectures, cross-game reusable patterns. | |
| Game Server Developer | 必要 | Has deep expertise in design patterns for game servers: designs ECS (Entity Component System) architectures, implements command pattern for deterministic game state, optimizes object pool and flyweight for game server memory/performance. Mentors team on game-specific architectural patterns for multiplayer systems. |
| Infrastructure Engineer | Designs infrastructure tools using patterns: Pipeline for deployment, Observer for event monitoring. Implements Circuit Breaker for fault-tolerant integration with cloud API providers. | |
| iOS Developer | 必要 | Has deep expertise in design patterns for iOS: designs clean architectures with VIPER/VIP or composable architecture patterns, implements reactive patterns with Combine/async-await, optimizes pattern usage for iOS memory management and performance. Mentors team on architectural patterns for complex iOS applications. |
| IoT Engineer | Designs IoT systems using advanced patterns: Gateway for communication protocols, Chain of Responsibility for sensor data processing, Mediator for device coordination. | |
| Language Tooling Engineer | 必要 | Has deep expertise in design patterns for compilers: designs extensible compiler architectures with visitor and interpreter patterns, implements plugin systems for compiler passes and code generators, optimizes pattern usage for compilation performance. Mentors team on compiler design patterns for language ecosystem tools. |
| LLM Engineer | Designs LLM system architecture using patterns: Plugin for model backends, Pipeline for inference chains, Registry for model/tokenizer management. Ensures extensibility. | |
| ML Engineer | Designs ML systems using architectural patterns: Plugin architecture for models, Chain of Responsibility for data validation, Decorator for model wrappers. | |
| MLOps Engineer | 必要 | Has deep expertise in design patterns for ML infrastructure: designs extensible pipeline architectures with plugin and strategy patterns, implements orchestration patterns for distributed training workflows, optimizes pattern usage for ML system scalability. Mentors team on architectural patterns for production MLOps platforms. |
| Network Engineer | Designs network systems using advanced patterns — Plugin Architecture for supporting new vendors, CQRS for separating configuration reads from application. | |
| NLP Engineer | Designs custom architectural patterns for NLP platforms. Creates extensible frameworks for model experiments using Plugin and Template Method to support new architectures. | |
| Penetration Testing Engineer | Designs security tool architecture using complex patterns — Command for exploit chains, Proxy for traffic interception, Mediator for attack coordination. | |
| Performance Testing Engineer | Designs performance frameworks using patterns: Pipeline for result processing, Composite for compound scenarios, Decorator for adding monitoring to test steps. | |
| Platform Engineer | 必要 | Has deep expertise in design patterns for platform systems: designs extensible platform architectures with adapter and strategy patterns, implements self-service patterns for infrastructure provisioning, optimizes pattern usage for multi-tenant platform scalability. Mentors team on architectural patterns for internal developer platforms. |
| Product Manager | Defines product requirements for architecture: plugin system, marketplace, white-label, multi-tenancy. Designs platform strategy considering architectural patterns for ecosystem development. Evaluates build vs buy decisions considering architectural implications and long-term product vision. | |
| QA Automation Engineer | 必要 | Has deep expertise in design patterns for test frameworks: designs extensible test architectures with page object and screenplay patterns, implements plugin systems for cross-platform test execution, optimizes pattern usage for test suite maintainability. Mentors team on architectural patterns for enterprise test automation frameworks. |
| QA Engineer (Manual) | Designs testing strategy considering architectural patterns: microservices, CQRS, event sourcing. Identifies critical testing points at pattern boundaries and potential defect sources. Develops a test design framework based on analysis of project architectural decisions. | |
| QA Security Engineer | Designs security testing platform architecture using advanced patterns: Plugin for extensible scanners, Observer for result monitoring, Template Method for test scenarios. | |
| React Native Developer | 必要 | Architects React Native application patterns — Feature-Sliced Design, modular architecture. Applies Mediator for navigation coordination, Strategy for platform-specific iOS/Android logic. Implements patterns for New Architecture (Fabric, TurboModules). |
| Release Engineer | Combines complex patterns to build extensible release infrastructure. Designs plugin architectures using Abstract Factory and Chain of Responsibility patterns. | |
| Security Analyst | Combines patterns to build an extensible security analytics platform. Designs pluggable detector architectures using Abstract Factory and Decorator patterns. | |
| Site Reliability Engineer (SRE) | Designs reliability architecture: cell-based architecture, shuffle sharding, backpressure patterns. Combines patterns for multi-layer resilience. | |
| Smart Contract Developer | Designs architectural patterns for smart contract systems: hook-based extensions (Uniswap V4 style), plugin architectures, abstract accounts. Analyzes pattern trade-offs for specific use cases. | |
| Solutions Architect | 必要 | Has deep expertise in design patterns across technology stacks: designs cross-service architectural patterns for distributed systems, implements integration patterns (saga, circuit breaker, bulkhead) for resilient architectures, optimizes pattern selection for organizational tech landscape. Mentors teams on strategic pattern application for system evolution. |
| Systems Programmer (C/C++) | 必要 | Designs with advanced patterns: Actor model, zero-copy pipeline, lock-free observer, compile-time strategy via template specialization. |
| Technical Lead | 必要 | Has deep expertise in evaluating and applying design patterns: designs team-level architectural patterns aligned with system requirements, identifies anti-patterns and refactoring opportunities, optimizes pattern decisions for long-term code maintainability. Mentors team on strategic pattern application and architectural decision-making. |
| Technical Product Manager | Applies pattern knowledge when designing product solutions — plugin architecture for extensions, CQRS for reporting, saga for complex business processes with compensations. | |
| Technical Writer | Designs architectural documentation standards with pattern descriptions at the organizational level. Creates in-depth whitepapers and ADRs on pattern application in the context of large-scale products. Develops interactive architectural pattern visualizations for developer education. | |
| Telecom Developer | 必要 | Has deep expertise in design patterns for telecom systems: designs protocol-aware architectures with state machine and chain of responsibility patterns, implements resilient communication patterns for telecom reliability, optimizes pattern usage for real-time signaling performance. Mentors team on telecom-specific architectural patterns for multi-protocol systems. |
| Unity Developer | 必要 | Designs Unity project architecture based on patterns: MVC/MVP for UI, ECS for gameplay, Event Bus for decoupled communication. Combines patterns to solve complex architectural challenges. |
| Unreal Engine Developer | 必要 | Designs AAA Unreal project architecture: Modular Gameplay via Game Features, plugin-based architecture, custom framework layers. Ensures extensibility for DLC and live-service. |
| XR Unity Developer | 必要 | Designs custom patterns for Unity XR. Combines patterns for complex XR systems. Adapts patterns for real-time constraints. |
| 角色 | 必要性 | 描述 |
|---|---|---|
| 1C Developer | 必要 | Defines design pattern standards for 1C development teams: establishes architectural review practices for pattern usage in configurations, creates guidelines for pattern application in 1C platform context, conducts training on patterns adapted for 1C:Enterprise development. |
| AI Product Engineer | 必要 | Defines design pattern standards for AI product teams: establishes architectural review practices for ML system patterns, creates guidelines for pattern application in AI/ML codebases, conducts training on patterns for extensible ML architectures. |
| Analytics Engineer | Defines a design pattern catalog for the analytics platform, trains the team on applying them in data engineering. Establishes best practices for using patterns to build maintainable and testable analytics systems. | |
| Android Developer | 必要 | Implements and adapts design patterns for the Android team: Repository for data management, Observer via LiveData/StateFlow, Factory for Fragment and ViewModel creation. Develops internal guides on pattern usage in the Android context — Dependency Injection via Hilt, Builder for component configuration, Strategy for A/B testing. |
| Application Security Engineer | Defines the security architecture patterns catalog for the organization. Trains teams on applying patterns for building secure systems and conducts architectural decision reviews. | |
| AR/VR Developer | 必要 | Builds a pattern catalog for XR development within the team. Reviews pattern application. Trains the team on architectural approaches. |
| Backend Developer (C#/.NET) | 必要 | Establishes .NET team architectural standards: MediatR for CQRS, FluentValidation, Options pattern. Defines Dependency Injection conventions. Conducts architectural reviews. |
| Backend Developer (Elixir) | 必要 | Adapts design patterns for idiomatic Elixir using OTP behaviours. Implements GenServer, Supervisor, GenStage and Broadway for building resilient data processing pipelines. Trains the team on applying functional patterns and protocols. |
| Backend Developer (Go) | 必要 | Adapts classic patterns to idiomatic Go: functional options, middleware chains in Gin/Chi, graceful shutdown via context.Context. Reviews team architectural decisions, ensuring adherence to Go conventions and interface composition principles. |
| Backend Developer (Java/Kotlin) | 必要 | Establishes architectural standards for the Java team based on patterns. Defines Spring configurations and conventions for the project. Conducts architectural reviews focused on GoF and enterprise patterns. |
| Backend Developer (Node.js) | 必要 | Establishes Node.js team architectural standards: Middleware pattern (Express/Fastify), Repository pattern for data access, Dependency Injection (tsyringe/inversify). Conducts architectural reviews. |
| Backend Developer (PHP) | 必要 | Shapes team architectural standards based on patterns. Decides which patterns to apply at project level. Conducts architectural reviews focused on correct pattern application. |
| Backend Developer (Python) | 必要 | Selects architectural patterns at system level. Builds catalog of approved patterns for the team. Designs framework-level solutions using patterns. Evaluates trade-offs of different approaches. |
| Backend Developer (Rust) | 必要 | Adapts classic patterns to Rust ownership model: Builder through consuming self, Strategy through trait objects (Box<dyn Trait>), Observer through Tokio channels. Forms team's library of idiomatic patterns including typestate pattern and newtype idiom. |
| Backend Developer (Scala) | 必要 | Implements functional design patterns in Scala team codebase: Tagless Final, Free Monad, Reader/Writer for dependency injection. Conducts architectural reviews emphasizing typeclass patterns from Cats and ZIO for ensuring code composability and testability. |
| BI Analyst | Defines architectural pattern standards for the entire team's analytical systems. Reviews analysts' architectural decisions and recommends optimal patterns for each task. Creates an internal pattern library for typical BI tasks: ETL, reporting, data quality. | |
| Blockchain Developer | Defines architectural standards and pattern library for the blockchain organization. Establishes architectural decision records (ADR) and conducts architecture review for 10+ projects. | |
| Cloud Engineer | Defines architectural patterns for cloud platform: reference architectures, pattern catalog for the team. Conducts design reviews focusing on cloud-native patterns. | |
| Compiler Engineer | Establishes design pattern standards for the compiler engineering team and makes architectural decisions. Defines technical roadmap considering this skill. Mentors senior engineers and influences practices of adjacent teams. | |
| Computer Vision Engineer | Defines architectural pattern catalog for the CV team, trains engineers in proper pattern selection. Conducts architectural reviews focused on ML system extensibility. | |
| Data Analyst | Defines a pattern catalog for the analytics team, trains engineers on proper pattern selection and application. Conducts architectural reviews focusing on reusability and extensibility. | |
| Data Engineer | Defines data architectural patterns: reference data architectures, pattern catalog, design review criteria. | |
| Data Scientist | Defines ML architectural patterns: reference ML architectures, pattern catalog for the DS team. | |
| Database Engineer / DBA | Defines a pattern catalog for the DBA platform: standard solutions for monitoring, failover, backup/restore. Mentors the team on applying patterns in database administration context. | |
| Desktop Developer (.NET WPF/WinUI/MAUI) | 必要 | Defines architectural patterns for .NET desktop team. Conducts design reviews, selects optimal patterns. Establishes pattern catalog for the team. |
| Desktop Developer (Electron/Tauri) | 必要 | Defines architectural patterns for the Electron team. Conducts design review. Establishes pattern catalog for desktop development. |
| Desktop Developer (Qt/C++) | 必要 | Defines pattern usage standards in Qt projects. Conducts design review, selects optimal patterns for tasks. Mentors on architectural patterns in desktop development. |
| DevOps Engineer | Defines architectural patterns for DevOps: reference pipeline architectures, deployment pattern catalog. Conducts design reviews. | |
| DevSecOps Engineer | Defines design pattern catalog for the organization's DevSecOps tooling. Reviews architectural decisions for correct pattern application and over-engineering prevention. | |
| Embedded Developer | Defines pattern catalog for the embedded team. Establishes reference implementations with overhead benchmarks, conducts architecture reviews. | |
| Engineering Manager | 必要 | Defines design pattern standards at the organizational level: establishes architectural review processes for pattern governance, creates guidelines balancing pattern consistency with team autonomy, conducts assessments of pattern competency across engineering teams. |
| Flutter Developer | 必要 | Defines design pattern standards for Flutter teams: establishes architectural review practices for mobile app patterns, creates guidelines for state management and architecture pattern selection, conducts training on Flutter-specific design patterns for scalable apps. |
| Frontend Developer (Angular) | 必要 | Builds a recommended pattern catalog for the Angular team: SCAM (Single Component Angular Module), feature-based architecture, error handling patterns via HttpInterceptors and ErrorHandler. |
| Frontend Developer (React) | 必要 | Defines architectural patterns for the team's React projects: convention over configuration, monorepo structure with Turborepo. Standardizes approaches to component composition, side-effects management and Next.js App Router integration. |
| Frontend Developer (Svelte) | 必要 | Defines an architectural pattern catalog for the team's Svelte ecosystem, standardizes composition and reuse approaches. Reviews architectural decisions, ensuring pattern consistency in load functions, form actions, and SvelteKit API routes. |
| Frontend Developer (Vue) | 必要 | Defines pattern and anti-pattern catalog for Vue development in the organization. Introduces architectural solutions — Feature-Sliced Design, Clean Architecture adapted for Vue 3 and Nuxt 3 ecosystem. |
| Fullstack Developer | 必要 | Applies design patterns across the entire stack: Repository and Unit of Work on backend, Compound Components and Render Props on frontend, BFF pattern for connection. Reviews team architectural decisions ensuring approach consistency. |
| Game Designer | Defines the architectural style and standard pattern set for the game project codebase. Reviews team architectural decisions and recommends optimal patterns for each subsystem. Conducts architecture sessions and trains the team on applying patterns in game development. | |
| Game QA Engineer | Defines QA design patterns: test framework patterns catalog, code review criteria, architectural guidelines. | |
| Game Server Developer | 必要 | Defines design pattern standards for game server teams: establishes architectural review practices for game system patterns (ECS, command, state), creates guidelines for pattern selection in real-time multiplayer contexts, conducts training on game-specific architectural patterns. |
| Infrastructure Engineer | Defines organizational infrastructure pattern catalog: immutable infrastructure, cattle vs pets, twelve-factor. Makes architectural decisions based on proven patterns for common tasks. | |
| iOS Developer | 必要 | Applies design patterns in the iOS development context: Coordinator for navigation, Repository for data access, Factory for UI component creation. Adapts classic GoF patterns for Swift specifics — protocol-oriented programming, value types, and property wrappers for dependency injection. |
| IoT Engineer | Defines pattern catalog for IoT platform: standard solutions for edge data processing, fault tolerance patterns for unstable connections, architectural templates for scaling. | |
| Language Tooling Engineer | 必要 | Defines design pattern standards for language tooling teams: establishes architectural review practices for compiler and tooling patterns, creates guidelines for extensible language tool architectures, conducts training on visitor, interpreter, and composite patterns for compiler development. |
| LLM Engineer | Defines architectural patterns for the LLM platform. Establishes guidelines for applying patterns in ML systems, conducts design reviews of new inference pipeline components. | |
| ML Engineer | Establishes ML system design patterns at team level. Defines reference architectures for common ML tasks. Trains the team on applying patterns in ML context. | |
| MLOps Engineer | 必要 | Implements MLOps system design patterns in the team: Strategy for training algorithm selection, Pipeline for processing stage composition, Observer for model drift monitoring. Standardizes approaches to building reusable ML pipeline components via Kubeflow Components and Airflow Operators. |
| Network Engineer | Defines the pattern catalog for the team's network solutions. Conducts architectural decision reviews, ensuring correct pattern application and preventing over-engineering. | |
| NLP Engineer | Defines architectural patterns for all organizational NLP projects. Standardizes ML pipeline construction approaches and ensures component reusability across teams. | |
| Penetration Testing Engineer | Defines architectural standards for team security tooling, trains engineers on designing extensible tools. Creates internal frameworks for pentest automation. | |
| Performance Testing Engineer | Defines architectural patterns for the performance platform: standard solutions for distributed load generation, scaling patterns for test infrastructure, reporting templates. | |
| Platform Engineer | 必要 | Implements architectural patterns for platform services: Operator pattern for K8s, Sidecar/Ambassador for service mesh, Circuit Breaker for resilience. Leads design pattern standardization through golden path templates. Conducts pattern-focused design reviews. |
| Product Manager | Defines architectural strategy for the product platform at the project level. Coordinates alignment between architectural and product decisions for all teams. Standardizes the framework for build vs buy evaluation considering architectural patterns. | |
| QA Automation Engineer | 必要 | Defines design pattern standards for QA automation teams: establishes architectural review practices for test framework patterns, creates guidelines for pattern selection in test infrastructure design, conducts training on patterns for maintainable and extensible test architectures. |
| QA Engineer (Manual) | Defines design pattern standards for test automation frameworks at the team/product level. Reviews test architecture decisions and recommends optimal patterns for each testing task. | |
| QA Security Engineer | Defines a pattern catalog for security testing in the organization. Trains teams on using patterns to build maintainable and scalable security test frameworks. | |
| React Native Developer | 必要 | Defines the architectural pattern catalog for the team's React Native projects. Establishes pattern application guidelines — when to use HOC vs Custom Hook vs Render Props. Reviews architectural decisions and ensures pattern consistency across multiple applications. |
| Release Engineer | Builds a pattern catalog for release engineering and trains the team on their proper application. Conducts architectural reviews focused on patterns for scalable CI/CD solutions. | |
| Security Analyst | Builds a pattern catalog for security engineering and trains the team on their application. Conducts architecture reviews of analytical systems focusing on detector extensibility. | |
| Site Reliability Engineer (SRE) | Defines reliability patterns for the organization: pattern catalog, reference architectures for resilience. Conducts design reviews focused on reliability. | |
| Smart Contract Developer | Defines pattern library for smart contract organizations. Establishes architectural decision framework for pattern selection. Conducts architecture reviews for new contract systems. | |
| Solutions Architect | 必要 | Defines design pattern standards across multi-team architectures: establishes cross-service pattern governance and architectural review practices, creates guidelines for integration and resilience pattern selection, conducts architecture forums on strategic pattern application for distributed systems. |
| Systems Programmer (C/C++) | 必要 | Defines pattern catalog for the systems team. Establishes reference implementations with benchmarks, conducts architecture reviews. |
| Technical Lead | 必要 | Defines design pattern standards for technical teams: establishes architectural review practices for pattern consistency across services, creates guidelines for pattern selection and refactoring strategies, conducts training on advanced patterns and anti-pattern recognition. |
| Technical Product Manager | Evaluates team architectural decisions from a product strategy perspective. Ensures chosen patterns support planned functionality and product scaling. | |
| Technical Writer | Defines standards for documenting architectural decisions and patterns for all company projects. Coordinates creation of a corporate pattern library with descriptions, examples, and decision criteria. Implements Architecture Decision Records as a standard documentation practice. | |
| Telecom Developer | 必要 | Defines design pattern standards for telecom teams: establishes architectural review practices for protocol and signaling patterns, creates guidelines for pattern selection in real-time telecom contexts, conducts training on telecom-specific patterns for multi-standard implementations. |
| Unity Developer | 必要 | Defines architectural patterns for Unity studio. Establishes decision matrix for choosing patterns by game type. Conducts architectural reviews and mentoring. |
| Unreal Engine Developer | 必要 | Defines architectural patterns for the Unreal studio. Establishes decision framework for choosing architecture by project type. Conducts architecture reviews and mentoring. |
| XR Unity Developer | 必要 | Establishes pattern catalog for XR team. Reviews pattern application. |
| 角色 | 必要性 | 描述 |
|---|---|---|
| 1C Developer | 必要 | Defines organizational strategy for design patterns in 1C development: evaluates pattern approaches for enterprise-scale 1C systems, makes technology decisions on architecture patterns for the 1C platform, mentors leads on strategic pattern application for complex 1C integrations. |
| AI Product Engineer | 必要 | Defines organizational strategy for design patterns in AI systems: evaluates pattern approaches for enterprise ML platforms, makes technology decisions on ML architecture patterns, mentors leads on strategic pattern application for scalable AI product architectures. |
| Analytics Engineer | Shapes corporate architectural patterns for enterprise analytics systems. Defines the data platform reference architecture with a proven pattern set for solving typical large-scale analytics challenges. | |
| Android Developer | 必要 | Defines architectural patterns at the Android platform level: MVVM/MVI standards, module decomposition rules, inter-module interaction protocols. Creates reference architectures for typical Android applications (e-commerce, social, media), mentors leads on selecting and combining patterns for complex business domains. |
| Application Security Engineer | Shapes the strategy for using design patterns to ensure security-by-design at the organizational level. Defines reference architectures for secure systems across different product types. | |
| AR/VR Developer | 必要 | Defines architectural patterns for the XR industry. Publishes research on XR design patterns. |
| Backend Developer (C#/.NET) | 必要 | Defines .NET platform architectural patterns: Clean Architecture, Vertical Slice, Event-Driven. Shapes reference architecture on ASP.NET Core. Evaluates trade-offs for business context. |
| Backend Developer (Elixir) | 必要 | Shapes architectural pattern standards at the entire Elixir platform level. Designs custom OTP behaviours and frameworks based on GenServer, Supervisor and DynamicSupervisor for typical business tasks. Defines protocol and macro usage strategy. |
| Backend Developer (Go) | 必要 | Shapes Go development architectural style across the organization: standard microservice patterns, unified dependency injection approach via Wire, error handling and graceful degradation templates. Publishes internal Go guidelines. |
| Backend Developer (Java/Kotlin) | 必要 | Defines Java platform architectural patterns: DDD, Hexagonal Architecture, Event-Driven. Shapes reference architecture on Spring Boot/Spring Cloud. Evaluates approach trade-offs for business context. |
| Backend Developer (Node.js) | 必要 | Defines Node.js platform architectural patterns: Event-Driven Architecture, CQRS, Circuit Breaker (opossum). Shapes reference architecture on NestJS/Fastify. Evaluates trade-offs. |
| Backend Developer (PHP) | 必要 | Defines architectural patterns at platform level: DDD, Hexagonal Architecture, Event-Driven. Evaluates trade-offs of different approaches for the business context. Shapes reference architecture for new services. |
| Backend Developer (Python) | 必要 | Defines architectural patterns at company level. Creates reference architecture for new projects. Publishes articles and presents on patterns. Adapts enterprise patterns to the Python ecosystem. |
| Backend Developer (Rust) | 必要 | Defines architectural patterns for the organizational Rust service ecosystem: tower middleware stacks, typed configurations through serde, plugin systems through dynamic dispatch. Develops proc macros for code generation of repetitive patterns. |
| Backend Developer (Scala) | 必要 | Defines architectural patterns for the entire Scala platform: choosing between Tagless Final and ZIO Environment, Effect system usage standards. Establishes guidelines for applying CQRS, Event Sourcing and Saga patterns in distributed Akka systems at organizational level. |
| BI Analyst | Shapes a corporate catalog of architectural patterns for analytical platforms. Defines best practices for applying patterns in the modern data stack at the industry level. Publishes research on architectural solutions for enterprise analytics. | |
| Blockchain Developer | Researches and publishes new patterns for blockchain systems. Shapes enterprise architecture guide for distributed blockchain platforms. Contributes to open-source patterns. | |
| Cloud Engineer | Shapes cloud platform pattern library: multi-cloud abstractions, platform patterns (cell-based architecture, shuffle sharding). Defines when to apply which patterns. | |
| Compiler Engineer | Shapes design pattern strategy for compiler engineering at the organizational level. Defines best practices and influences technology choices beyond their own team. Is a recognized expert in this area. | |
| Computer Vision Engineer | Shapes architectural standards for pattern application in the organization's CV platform. Creates internal frameworks encapsulating best practices for ML system design. | |
| Data Analyst | Shapes architectural standards for pattern application at the organizational analytical platform level. Creates internal frameworks and libraries encapsulating best design practices. | |
| Data Engineer | Shapes data architecture strategy: organizational data patterns, data mesh governance, architectural principles for data platform. | |
| Data Scientist | Shapes ML architecture strategy: organizational ML patterns, platform design principles. | |
| Database Engineer / DBA | Shapes architectural patterns for organizational data management: Database-as-a-Service patterns, self-healing cluster patterns, auto-scaling and zero-downtime upgrade patterns. | |
| Desktop Developer (.NET WPF/WinUI/MAUI) | 必要 | Shapes pattern catalog for .NET desktop organization. Adapts patterns for WPF/WinUI/MAUI. Publishes best practices on architectural patterns. |
| Desktop Developer (Electron/Tauri) | 必要 | Shapes pattern catalog for the organization's Electron desktop. Adapts patterns for TypeScript/Node.js. Publishes best practices. |
| Desktop Developer (Qt/C++) | 必要 | Shapes pattern catalog for the organization's desktop development. Adapts GoF/POSA patterns for the Qt/C++ context. Publishes research on pattern application in desktop. |
| DevOps Engineer | Shapes DevOps pattern library: platform patterns, deployment strategies, infrastructure design principles. Defines architectural governance. | |
| DevSecOps Engineer | Shapes organizational security platform architectural patterns, adapting classic approaches for DevSecOps specifics. Defines reference architecture for new security tools with reusable components. | |
| Embedded Developer | Defines enterprise catalog of embedded patterns. Establishes firmware architecture templates for product lines, mentors architects on pattern application. | |
| Engineering Manager | 必要 | Defines organizational strategy for design pattern governance: evaluates enterprise approaches to architectural pattern standardization, makes decisions on pattern competency programs and architecture review processes, mentors leads on balancing pattern rigor with pragmatic engineering culture. |
| Flutter Developer | 必要 | Defines organizational strategy for design patterns in mobile: evaluates enterprise approaches to mobile architecture patterns, makes technology decisions on state management and app architecture standards, mentors leads on strategic pattern application for mobile product lines. |
| Frontend Developer (Angular) | 必要 | Defines architectural pattern evolution during Angular version migration: from modules to standalone, from Zone.js to signal-based reactivity, from class-based guards to functional ones. |
| Frontend Developer (React) | 必要 | Shapes architectural pattern system for large-scale React ecosystems. Defines reuse strategy through shared libraries, micro-frontends on Module Federation, unified conventions for dozens of organization's React applications. |
| Frontend Developer (Svelte) | 必要 | Develops evolutionary pattern strategy for Svelte 5 migration, influences community best practice formation. Researches new patterns for rune usage ($state, $derived, $effect) and snippets, publishes architectural recommendations. |
| Frontend Developer (Vue) | 必要 | Shapes architectural pattern strategy for the entire company's Vue ecosystem. Researches and adapts advanced patterns — Islands Architecture, Resumability (Qwik-approach), server components for Nuxt. |
| Fullstack Developer | 必要 | Shapes organizational architectural pattern catalog for fullstack development. Defines when to apply CQRS, Event Sourcing, Micro-frontends. Creates reference implementations of end-to-end patterns from database to UI, mentors leads on their proper application. |
| Game Designer | Shapes corporate library of architectural patterns and best practices for the game studio. Researches and adapts modern patterns from adjacent fields for game applications. Publishes architectural guides and influences pattern development in the game development industry. | |
| Game QA Engineer | Shapes QA architecture strategy: organization-wide test patterns, reusable framework design, testing governance. | |
| Game Server Developer | 必要 | Defines organizational strategy for design patterns in game development: evaluates enterprise approaches to game architecture patterns (ECS, actor model), makes technology decisions on game engine and server architecture standards, mentors leads on strategic pattern application for multi-title game platforms. |
| Infrastructure Engineer | Shapes reference architecture for infrastructure platform with pattern catalog for each level. Defines pattern evolution considering serverless, edge computing and multi-cloud scenarios. | |
| iOS Developer | 必要 | Shapes the architectural pattern library for the iOS team, defining standards for Coordinator, Dependency Injection via SwiftUI Environment, and custom property wrappers. Develops custom patterns for complex scenarios: offline synchronization, multi-module navigation, and reactive data pipelines. |
| IoT Engineer | Builds architectural pattern catalog for organizational IoT ecosystem: patterns for edge computing, fog computing, device mesh. Publishes and promotes industry best practices. | |
| Language Tooling Engineer | 必要 | Defines organizational strategy for design patterns in language tooling: evaluates enterprise approaches to compiler and IDE architecture patterns, makes technology decisions on language tool extensibility models, mentors leads on strategic pattern application for language ecosystem platforms. |
| LLM Engineer | Shapes the catalog of architectural patterns for organizational LLM systems. Defines ML platform design standards, mentors architects on applying patterns in large-scale LLM projects. | |
| ML Engineer | Develops ML-specific patterns for the organization. Publishes best practices on ML system architecture. Defines ML platform architectural standards. | |
| MLOps Engineer | 必要 | Defines architectural patterns for the entire MLOps platform: Event-Driven Architecture for reactive retraining, CQRS for separating training and serving paths, Circuit Breaker for inference service fault tolerance. Establishes guidelines for applying Feature Store, Model Registry, and Experiment Tracking patterns at the organizational level. |
| Network Engineer | Develops and documents architectural patterns for the organization's network platforms. Creates reference implementations and builds a knowledge base of Network Automation patterns. | |
| NLP Engineer | Shapes design pattern catalog for ML/NLP systems at organizational level. Influences architectural practice development defining NLP infrastructure quality in the industry. | |
| Penetration Testing Engineer | Shapes the organization's security platform architectural strategy. Defines pentest tool design standards and their integration into the overall security ecosystem. | |
| Performance Testing Engineer | Shapes a pattern catalog for organizational performance engineering: architectural templates for continuous performance testing, CI/CD integration patterns, automation standards. | |
| Platform Engineer | 必要 | Defines architectural patterns at platform level: Platform API design patterns, self-service abstraction layers, composable infrastructure patterns. Shapes pattern language for the organization. Evaluates emerging patterns (cell-based architecture, hexagonal platforms) for IDP evolution. |
| Product Manager | Shapes corporate product architecture strategy at the company level. Defines industry standards for platform architecture for product-led growth. Publishes research on the impact of architectural patterns on product scalability. | |
| QA Automation Engineer | 必要 | Defines organizational strategy for design patterns in quality engineering: evaluates enterprise approaches to test architecture patterns, makes technology decisions on test framework and infrastructure standards, mentors leads on strategic pattern application for organizational test automation maturity. |
| QA Engineer (Manual) | Shapes corporate QA methodology for various architectural patterns and styles. Defines best practices for testing complex architectures: distributed, event-driven, serverless. Publishes research on testing effectiveness depending on applied patterns. | |
| QA Security Engineer | Shapes architectural pattern strategy for the organizational security testing ecosystem. Defines reference architectures for security testing platforms across different product types. | |
| React Native Developer | 必要 | Shapes the enterprise design patterns catalog for mobile development. Defines reference React Native application architecture with patterns for scaling, reuse, and maintainability. Leads architectural standards at the organizational level. |
| Release Engineer | Creates organizational standards for pattern application in release infrastructure. Develops new patterns specific to continuous delivery tasks in distributed systems. | |
| Security Analyst | Creates organizational standards for applying patterns in security platforms. Develops new patterns specific to threat detection and incident response tasks. | |
| Site Reliability Engineer (SRE) | Shapes reliability architecture: platform-wide resilience patterns, failure mode analysis framework, architectural principles for highly available systems. | |
| Smart Contract Developer | Publishes novel smart contract patterns for the community. Shapes enterprise architecture guide for smart contract systems. Contributes to open-source pattern libraries. | |
| Solutions Architect | 必要 | Defines organizational strategy for design patterns across architectures: evaluates enterprise approaches to architectural pattern standardization, makes technology decisions on integration and resilience pattern portfolios, mentors leads on strategic pattern application for system evolution and technology strategy. |
| Systems Programmer (C/C++) | 必要 | Defines enterprise catalog of system patterns. Establishes architectural patterns for performance-critical software. |
| Technical Lead | 必要 | Defines organizational strategy for design patterns in engineering: evaluates enterprise approaches to pattern governance and competency development, makes technology decisions on architectural pattern standards, mentors leads on strategic pattern application for organizational technical excellence. |
| Technical Product Manager | Shapes architectural requirements for the product platform. Defines which patterns should become standards to ensure component reusability across products. | |
| Technical Writer | Shapes industry standards for documenting architectural patterns and decisions. Publishes research on the effectiveness of different architecture documentation formats. Influences the development of automatic architecture documentation generation tools. | |
| Telecom Developer | 必要 | Defines organizational strategy for design patterns in telecom: evaluates enterprise approaches to telecom architecture patterns, makes technology decisions on protocol implementation and signaling architecture standards, mentors leads on strategic pattern application for multi-standard telecom platforms. |
| Unity Developer | 必要 | Defines architectural strategy for the studio. Shapes reference architectures for different Unity project types. Publishes architectural patterns for the game development community. |
| Unreal Engine Developer | 必要 | Defines architectural strategy for the studio. Shapes Unreal reference architectures. Publishes architectural guidelines for the game development community. |
| XR Unity Developer | 必要 | Defines architectural patterns for XR. Publishes research. |