领域
Programming Fundamentals
技能档案
Static vs dynamic typing, type narrowing, branded types, type guards, discriminated unions
角色数
49
包含此技能的角色
级别数
5
结构化成长路径
必要要求
84
其余 161 个可选
Programming Fundamentals
Type Systems
2026/3/17
选择当前级别并对比期望。下方卡片显示晋升所需掌握的内容。
表格展示从初级到首席的技能深度变化。点击行查看详情。
| 角色 | 必要性 | 描述 |
|---|---|---|
| 1C Developer | Understands basics of type safety in 1C:Enterprise platform — strict typing for document attributes, typed query results, and configuration object type hierarchies. Follows team conventions for type declarations in 1C module interfaces and data exchange formats. | |
| AI Product Engineer | Studies typing fundamentals and its importance for AI product code reliability. Understands the difference between static and dynamic typing, uses basic type annotations in Python and TypeScript for ML projects. | |
| Analytics Engineer | Studies typing basics and their importance for analytics code reliability. Understands the difference between typed and untyped approaches, uses type annotations in Python for data pipelines. | |
| Android Developer | Understands basics of type safety in Kotlin/Java Android development — null safety with Kotlin nullable types, sealed classes for state modeling, and typed Intent extras. Follows team conventions for type-safe navigation arguments and ViewBinding patterns. | |
| Backend Developer (C#/.NET) | 必要 | Understands basics of C# type system — value types vs reference types, nullable reference types, and generic constraints. Follows team conventions for type annotations, interface-based abstractions, and strongly-typed configuration patterns. |
| Backend Developer (Elixir) | Understands type safety in Elixir: typespecs (@spec, @type), Dialyzer for static analysis. Writes type specifications for functions and structs. | |
| Backend Developer (Go) | Understands type safety in Go: static typing, interface contracts, custom types. Uses linting for type checks. | |
| Backend Developer (Java/Kotlin) | 必要 | Understands basics of Java type system — generics, bounded type parameters, and Optional for null safety. Follows team conventions for type-safe collections, enum patterns, and interface-based dependency injection with proper type hierarchies. |
| Backend Developer (Node.js) | 必要 | Understands the fundamentals of Type Safety & Type Systems 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) | 必要 | Understands basics of PHP type system — strict_types declaration, type hints for function parameters and return types, and union types. Follows team conventions for PHPStan/Psalm static analysis levels and typed property declarations. |
| Backend Developer (Python) | 必要 | Uses basic type hints: str, int, list[str], Optional. Understands why typing is needed in Python. Knows main types from typing module. Runs mypy for type checking. |
| Backend Developer (Rust) | 必要 | Understands the fundamentals of Type Safety & Type Systems 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 Type Safety & Type Systems at a basic level. Applies simple concepts in work tasks using Scala 3. Follows recommendations from senior developers when solving problems. |
| Blockchain Developer | Applies type safety: typed Solidity (custom types), TypeScript for tooling. Uses strict typing. | |
| Compiler Engineer | Knows basic type safety 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 | Understands type safety concepts and can use type hints in Python for CV code. Knows the benefits of typing for preventing errors in ML pipelines. | |
| Data Engineer | Applies type safety in data code: typed Python (mypy), schema definitions, data class models. Uses typed configurations. | |
| Desktop Developer (.NET WPF/WinUI/MAUI) | Understands type safety in C#: nullable reference types, pattern matching. Uses record for immutable types. Avoids dynamic and object where possible. Applies strongly-typed IDs. | |
| Desktop Developer (Electron/Tauri) | Understands TypeScript typing for Electron: strict mode, interface vs type. Types IPC messages. Uses enum for constants. Avoids any. | |
| Desktop Developer (Qt/C++) | Understands typing in C++17/Qt: uses auto, strong typedef. Knows differences between QVariant and typed containers. Avoids implicit conversions through explicit constructors. | |
| DevOps Engineer | Applies type safety in DevOps code: typed Python/TypeScript for automation, JSON Schema for configs. Uses typed pipeline definitions. | |
| Embedded Developer | Understands type safety importance in embedded: proper casting, enum instead of magic numbers, typedef for hardware registers. | |
| Engineering Manager | Understands type safety concepts and can evaluate team decisions on using typing in projects. Knows the advantages of static typing for code quality. | |
| Flutter Developer | Understands the fundamentals of Type Safety & Type Systems at a basic level. Applies simple concepts in work tasks using Dart. Follows recommendations from senior developers when solving problems. | |
| Frontend Developer (Angular) | 必要 | Uses basic TypeScript types in Angular components: interfaces for data models, typed @Input/@Output, strict HTTP response typing via HttpClient.get<T>(). Avoids using any. |
| Frontend Developer (React) | 必要 | Uses basic TypeScript types in React components: interfaces for props, typing useState and events. Understands the difference between type and interface, applies React.FC, types event handlers onChange, onClick. |
| Frontend Developer (Svelte) | 必要 | Uses TypeScript in Svelte components with lang="ts", types $props() and basic $state variables. Understands basic types for SvelteKit load functions (PageData, PageServerLoad), applies built-in Svelte types for component events. |
| Frontend Developer (Vue) | 必要 | Uses TypeScript with Vue 3 — typing props through defineProps<T>(), emit through defineEmits, basic ref() and reactive() typing. Understands type inference in script setup and templates through Volar. |
| Fullstack Developer | 必要 | Understands the fundamentals of Type Safety & Type Systems at a basic level. Applies simple concepts in work tasks using TypeScript/Python. Follows recommendations from senior developers when solving problems. |
| Game Server Developer | Understands the benefits of typing in server code and uses basic types. Annotates game event handler functions, character data structures, and inventory items. | |
| Infrastructure Engineer | Understands type safety concept and its role in preventing errors in infrastructure code. Uses basic types in Terraform variables and TypeScript for CDK configurations. | |
| iOS Developer | Studies type safety basics in Swift and its importance for iOS application reliability. Understands Swift's type system — optionals, generics, protocols — and their role in preventing runtime errors. | |
| IoT Engineer | Understands type safety concepts and their importance for code reliability. Uses strict typing when developing IoT applications to prevent runtime errors. | |
| Language Tooling Engineer | Understands the fundamentals of Type Safety & Type Systems at a basic level. Applies simple concepts in work tasks using TypeScript/Rust. Follows recommendations from senior developers when solving problems. | |
| LLM Engineer | Applies type safety for LLM: typed prompt templates, response schemas. Uses Pydantic. | |
| ML Engineer | Understands type safety concept and its importance for ML code reliability. Uses type hints in Python for annotating preprocessing functions and feature types in ML pipelines. | |
| MLOps Engineer | Understands type safety concepts and their importance for ML code reliability. Uses Python type hints when writing scripts for MLOps pipelines. | |
| NLP Engineer | Understands basics of type safety in Python NLP development — type hints for tensor shapes, typed dataclasses for pipeline configurations, and Protocol classes for model interfaces. Follows team conventions for mypy strict mode and typed training configuration schemas. | |
| Performance Testing Engineer | Understands type safety concepts and their importance for code reliability. Uses typing when writing test scripts to prevent errors in load parameters. | |
| Platform Engineer | Applies type safety in platform code: typed CRD definitions, TypeScript for platform UI, Go structs for controllers. Uses typed configurations. | |
| QA Automation Engineer | Understands the benefits of static typing for test code quality. Uses basic TypeScript types when writing automated tests — typing page objects, test data, and fixtures. | |
| QA Engineer (Manual) | Studies type safety fundamentals and their importance for test code reliability. Understands the difference between static and dynamic typing, uses basic type annotations in test automation scripts. | |
| React Native Developer | Uses basic TypeScript types in React Native — interfaces for component props, types for state, enums for constants. Types API responses with interfaces. Understands generic types for useState and useRef. Fixes TypeScript compiler errors in the IDE. | |
| Site Reliability Engineer (SRE) | Applies type safety in SRE code: TypeScript for automation, typed Python for tooling. Uses typed configurations (Jsonnet, CUE). | |
| Smart Contract Developer | Understands the fundamentals of Type Safety & Type Systems at a basic level. Applies simple concepts in work tasks using Solidity/Vyper. Follows recommendations from senior developers when solving problems. | |
| Solutions Architect | Understands type safety in architecture: static vs dynamic typing trade-offs, schema validation. Evaluates type safety requirements. | |
| Systems Programmer (C/C++) | Understands the fundamentals of Type Safety & Type Systems at a basic level. Applies simple concepts in work tasks using C/C++/Rust. Follows recommendations from senior developers when solving problems. | |
| Technical Lead | Understands type safety: static vs dynamic typing, generic types, type inference. Uses TypeScript/typed languages to prevent runtime errors. | |
| Telecom Developer | Understands the concept of type safety and its importance for telecom code reliability. Uses strict types for describing SIP, Diameter, and GTP protocol message structures. |
| 角色 | 必要性 | 描述 |
|---|---|---|
| 1C Developer | Implements type safety practices in 1C development: strict parameter typing, runtime type checking, using TypeDescription for data validation during loading. | |
| AI Product Engineer | Applies strict typing in AI products to prevent errors in data processing and inference results. Uses generics, union types, and schema validation to ensure data correctness at service boundaries. | |
| Analytics Engineer | Applies strict typing in analytics pipelines through Pydantic, dataclasses, and typed DataFrames. Uses schema validation for data contracts between sources, transformations, and consumers. | |
| Android Developer | Implements strict typing in Android projects with Kotlin. Applies generics, type-safe builders for navigation, and sealed hierarchies for UI states, eliminating runtime type errors. | |
| Backend Developer (C#/.NET) | 必要 | Independently applies C# type system features — nullable reference type analysis, generic variance in interfaces, and source generators for type-safe boilerplate. Understands trade-offs between record types and classes for domain modeling. Applies type-safe patterns with System.Text.Json and strongly-typed options in code reviews. |
| Backend Developer (Elixir) | Ensures type safety in Elixir code: comprehensive typespecs, Dialyzer integration in CI, custom types for domain model. Uses guards for runtime type checking. | |
| Backend Developer (Go) | Ensures type safety: generics (Go 1.18+), typed errors, domain-specific types. Implements strict linting. | |
| Backend Developer (Java/Kotlin) | 必要 | Independently applies Java type system features — wildcard generics, sealed classes for ADTs, and type-safe builder patterns. Understands trade-offs between type erasure and reified generics, raw types vs parametric polymorphism. Applies type-safe patterns with records, pattern matching, and annotation processing in code reviews. |
| Backend Developer (Node.js) | 必要 | Independently applies TypeScript type system for Node.js services — discriminated unions for API response types, branded types for domain identifiers, and conditional types for handler signatures. Understands trade-offs between runtime validation (zod/io-ts) and compile-time safety. Applies type narrowing techniques in code reviews. |
| Backend Developer (PHP) | 必要 | Independently applies PHP type system features — intersection types, enums with backed values, and readonly properties for immutable DTOs. Understands trade-offs between phpstan level strictness and development velocity. Applies type-safe patterns with generics in doc-blocks, typed collections, and strict return type declarations in code reviews. |
| Backend Developer (Python) | 必要 | Uses TypedDict, Protocol, Literal, Union, Generic. Configures mypy with strict mode for modules. Creates custom type aliases. Understands variance (covariant/contravariant). Writes types for complex APIs (overload, ParamSpec). |
| Backend Developer (Rust) | 必要 | Independently applies Rust's type system for backend services — leveraging ownership and borrowing for memory safety, using enums with associated data for state machines, and applying trait bounds for generic service abstractions. Understands trade-offs between dynamic dispatch and monomorphization. Explains lifetime annotations and type-level programming to colleagues. |
| Backend Developer (Scala) | 必要 | Independently applies Scala's type system for backend services — using sealed traits for ADTs, type class patterns with implicits/givens, and higher-kinded types for effect abstractions. Understands trade-offs between type-level encoding complexity and runtime safety. Explains variance annotations and type inference to colleagues. |
| Blockchain Developer | Ensures type safety: TypeChain for typed contract interactions, Zod for validation. | |
| Compiler Engineer | Confidently applies type safety 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 strict typing in CV projects with mypy/pyright, creates typed dataclasses for model input/output. Ensures type safety in inference API. | |
| Data Engineer | Ensures type safety: Pydantic models for data validation, typed Spark DataFrames, strict schema enforcement. | |
| Desktop Developer (.NET WPF/WinUI/MAUI) | Uses discriminated unions through OneOf or custom types. Applies Result<T> pattern for error handling. Implements type-safe configuration through IOptions<T>. Understands covariance/contravariance. | |
| Desktop Developer (Electron/Tauri) | Creates type-safe IPC through generic typed channels. Uses discriminated unions for message types. Applies branded types for domain primitives. Configures strict tsconfig. | |
| Desktop Developer (Qt/C++) | Uses std::variant, std::optional, std::expected (C++23) for type-safe API. Applies enum class instead of int constants. Implements type-safe signals/slots through strictly typed Q_PROPERTY. | |
| DevOps Engineer | Provides type safety: typed Terraform (CDK/Pulumi), strict Python for scripts, schema validation for configurations. | |
| Embedded Developer | Applies type safety in embedded: strongly-typed register access, enum classes for hardware states, newtype pattern for physical units (volts, amps, degrees). | |
| Engineering Manager | Establishes typing standards for team projects, defines TypeScript or other type system strictness. Ensures typing consistency through linters. | |
| Flutter Developer | Independently applies Dart's type system for Flutter applications — null safety with sound null checking, generic widget patterns, and sealed classes for state management. Understands trade-offs between dynamic and strict typing approaches in widget trees. Applies type-safe serialization patterns in code reviews. | |
| Frontend Developer (Angular) | 必要 | Applies advanced typing: generic services, strictly typed forms (Typed Reactive Forms), discriminated unions for component states, typed NgRx actions and selectors. |
| Frontend Developer (React) | 必要 | Creates strictly typed React components with generics, discriminated unions for props, conditional types. Types hooks, Zustand/Jotai contexts, TanStack Query responses. Uses zod for runtime validation at the API boundary. |
| Frontend Developer (Svelte) | 必要 | Creates strict TypeScript interfaces for component props, types stores and $derived runes with generics. Configures svelte-check in strict mode, types form actions, server hooks, and SvelteKit API endpoints with full type safety. |
| Frontend Developer (Vue) | 必要 | Creates strictly typed composables and Pinia stores with generics. Configures TypeScript strict mode for Vue project, types provide/inject, route params in Nuxt 3 and API responses through Zod validation. |
| Fullstack Developer | 必要 | Independently applies type safety across frontend and backend — TypeScript strict mode for shared type definitions, API contract types with tRPC/GraphQL codegen, and end-to-end type-safe data flow. Understands trade-offs between runtime validation and compile-time guarantees across system boundaries. Applies type-safe patterns in code reviews. |
| Game Server Developer | Designs type-safe interfaces for server systems — strictly typed game events, protocol messages, API contracts. Uses generic types and discriminated unions. | |
| Infrastructure Engineer | Applies strict typing in infrastructure code: Terraform variable types, Pulumi with TypeScript, CDK constructs. Creates typed interfaces for infrastructure modules to prevent configuration errors. | |
| iOS Developer | Applies strict typing in iOS projects through Codable models, typed wrappers, and phantom types for error prevention. Uses Result type, associated values, and generic constraints for a type-safe application API layer. | |
| IoT Engineer | Applies strict typing in IoT projects: typed communication protocols, generic interfaces for different sensor types, enums for device states and hardware error codes. | |
| Language Tooling Engineer | Independently applies type system theory in language tool development — implementing type checkers, designing type inference algorithms, and building type-aware code analysis. Understands trade-offs between structural and nominal typing, soundness vs completeness. Explains type system design decisions to colleagues. | |
| LLM Engineer | Ensures type safety: structured output schemas, typed function calling, validation. | |
| ML Engineer | Applies strict typing in ML code: Pydantic models for API schemas, typed dataclasses for features. Creates type-safe interfaces for model inference with input/output schema validation. | |
| MLOps Engineer | Applies strict typing in MLOps: Pydantic models for pipeline configuration validation, typed schemas for feature stores, TypedDict for experiment and model metadata. | |
| NLP Engineer | Implements strict typing in NLP projects with Pydantic/dataclasses for data validation. Types model configurations, training parameters, and prediction formats for reliability. | |
| Performance Testing Engineer | Applies strict typing in performance scripts: TypeScript for k6 tests, typed load configurations, interfaces for test results and metrics, test parameter validation. | |
| Platform Engineer | Ensures type safety: strongly-typed operator code, CRD validation schemas, typed Helm values. Implements compile-time checks for platform components. | |
| QA Automation Engineer | Applies strict typing in the test framework — typed API clients, generic helpers for data handling, interfaces for page objects. Catches errors at compile time. | |
| QA Engineer (Manual) | Tests applications considering type safety: boundary values, type coercion, nullable fields. Validates API contracts for type compliance: request/response schemas, validation rules. Creates comprehensive checklists for testing type-related edge cases in formats and APIs. | |
| React Native Developer | Designs type-safe APIs — Generic hooks, discriminated unions for React Navigation parameters. Types Zustand/Jotai state management. Creates utility types for reuse. Configures strict mode TypeScript and path aliases in tsconfig for React Native. | |
| Site Reliability Engineer (SRE) | Ensures type safety in infrastructure code: typed Terraform (CDK/Pulumi), strict Python for automation, JSON Schema for configs. | |
| Smart Contract Developer | Independently applies Solidity/Vyper type systems for smart contract safety — using custom types for token amounts and addresses, interface inheritance for contract composition, and type-safe event definitions. Understands trade-offs between gas optimization and type safety in contract storage patterns. Applies type-safe patterns in contract audits. | |
| Solutions Architect | Designs type-safe systems: API schema contracts, code generation, cross-service type safety. Defines typing strategy. | |
| Systems Programmer (C/C++) | Independently applies type systems in systems programming — using C++ templates/concepts or Rust traits for zero-cost abstractions, phantom types for compile-time state tracking, and type-level encoding of invariants. Understands trade-offs between type erasure and monomorphization for performance. Explains advanced type system features to colleagues. | |
| Technical Lead | Ensures type safety: strict mode configurations, custom types for domain model, type guards. Uses type-safe ORM and API clients. | |
| Telecom Developer | Applies strict typing for telecom protocols: typed structures for SIP headers, ASN.1-encoded messages. Creates type-safe APIs for working with CDR, billing, and session management. |
| 角色 | 必要性 | 描述 |
|---|---|---|
| 1C Developer | Designs type-safe architectures for 1C solutions with contract interfaces. Develops type validation mechanisms for integrations and ensures data integrity during exchanges. | |
| AI Product Engineer | Designs type-safe AI product interfaces with runtime validation, typed model configurations, and strict API contracts. Implements code generation for types based on ML pipeline data schemas. | |
| Analytics Engineer | Architects type-safe analytics systems with runtime validation through Great Expectations and typed data contracts. Implements data contracts between teams with automated schema evolution and compatibility checking. | |
| Android Developer | Designs type-safe Android application architectures with Kotlin DSL. Creates type-safe APIs for modules, navigation, and DI with compile-time interaction correctness checks. | |
| Backend Developer (C#/.NET) | 必要 | Has deep expertise in C# type system — designs domain models leveraging discriminated unions (OneOf/custom), generic math interfaces, and Span<T>/Memory<T> for high-performance type-safe code. Architects type-safe middleware pipelines and API contracts. Mentors team on advanced generics, covariance/contravariance patterns, and compile-time type validation with analyzers. |
| Backend Developer (Elixir) | Designs type-safe Elixir systems: protocol-based type contracts, behaviour specs, comprehensive Dialyzer coverage. Implements type-driven development. | |
| Backend Developer (Go) | Designs type-safe Go: interface-driven design, type-safe options pattern, code generation for type safety. | |
| Backend Developer (Java/Kotlin) | 必要 | Has deep expertise in Java type system — designs domain models leveraging sealed interfaces, pattern matching exhaustiveness, and generic type witnesses for type-safe APIs. Architects type-safe annotation-driven frameworks and compile-time validation processors. Mentors team on advanced generics, type token patterns, and effective use of sealed hierarchies for domain modeling. |
| Backend Developer (Node.js) | 必要 | Has deep expertise in TypeScript type system — designs type-safe API layers with template literal types, mapped types for schema-driven development, and conditional types for plugin architectures. Architects end-to-end type-safe stacks with tRPC or effect-ts. Mentors team on advanced type inference, variance annotations, and balancing type complexity with developer ergonomics. |
| Backend Developer (PHP) | 必要 | Has deep expertise in PHP type system — designs domain models maximizing static analysis coverage with PHPStan/Psalm at maximum strictness levels. Architects type-safe frameworks using generics in templates, immutable value objects, and typed event systems. Mentors team on transitioning codebases to strict typing, effective phpstan baseline management, and type-safe ORM patterns. |
| Backend Developer (Python) | 必要 | Designs type-safe APIs for libraries. Uses advanced typing (TypeVar, ParamSpec, Concatenate). Configures mypy plugins. Creates typed DSLs. Understands Python type system limitations. |
| Backend Developer (Rust) | 必要 | Has deep expertise in Rust type system — designs zero-cost abstractions with associated types and GATs, encodes business invariants using newtype patterns and typestate programming, and leverages const generics for compile-time computation. Architects type-safe async service layers with tower middleware. Mentors team on advanced lifetime patterns, unsafe code auditing, and macro-based type generation. |
| Backend Developer (Scala) | 必要 | Has deep expertise in Scala type system — designs type-safe DSLs with dependent types, match types, and opaque type aliases. Architects effect-based systems using ZIO/Cats Effect with type-level error handling and resource safety. Mentors team on advanced type class derivation, implicit resolution, and balancing type-level sophistication with codebase accessibility. |
| Blockchain Developer | Designs type-safe blockchain: end-to-end typed interactions, schema validation. | |
| Compiler Engineer | Expertly applies type safety 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 type-safe CV system architecture with generic types for various models and transformations. Implements runtime validation with pydantic and compile-time checks. | |
| Data Engineer | Designs type-safe data pipelines: schema registry, typed transformations, compile-time data validation. | |
| Desktop Developer (.NET WPF/WinUI/MAUI) | 必要 | Designs type-safe API with Source Generators for compile-time validation. Creates strongly-typed wrappers for primitive obsession. Uses ref struct and Span<T> for type-safe memory access. Introduces exhaustive matching. |
| Desktop Developer (Electron/Tauri) | 必要 | Designs type-safe Electron architecture with end-to-end type safety (IPC→store→component). Uses conditional types and template literal types. Creates type-safe API for plugin developers. |
| Desktop Developer (Qt/C++) | 必要 | Designs type-safe architecture with concepts (C++20) and constexpr. Uses phantom types for compile-time validation. Creates type-safe wrappers for Qt API. Introduces strict typing in the QML-C++ bridge. |
| DevOps Engineer | Designs type-safe infrastructure: CUE/Jsonnet for typed configs, generated clients, schema validation pipeline. | |
| Embedded Developer | Designs type-safe API for embedded: phantom types for unit-of-measure, type-safe register access, newtype pattern for hardware interfaces. | |
| Engineering Manager | Shapes type safety strategy for multiple teams, defines generic type and type guard standards. Manages legacy code migration to strict typing. | |
| Flutter Developer | 必要 | Has deep expertise in Dart type system — designs type-safe state management architectures with sealed classes and exhaustive pattern matching, generic repository patterns, and extension types for domain-specific type safety. Architects type-safe navigation systems and serialization layers. Mentors team on null safety migration, generic widget patterns, and type-safe platform channel communication. |
| Frontend Developer (Angular) | 必要 | Designs type-safe APIs for Angular libraries: conditional types for DI tokens, template literal types for routing, branded types for business domain values, dynamic component typing. |
| Frontend Developer (React) | 必要 | Designs advanced type systems for React applications: type-safe form libraries, Next.js App Router routing, generic components for UI libraries. Creates utility types and type guards for complex business domains. |
| Frontend Developer (Svelte) | 必要 | Designs end-to-end type safety from server load functions to client components through SvelteKit type auto-generation. Creates type-safe API wrappers, implements branded types and discriminated unions for the Svelte application domain model. |
| Frontend Developer (Vue) | 必要 | Designs type system for large-scale Vue applications — generic components, conditional types for composables, type-safe routing. Creates utility types for Pinia stores and Nuxt modules with full autocompletion. |
| Fullstack Developer | 必要 | Has deep expertise in cross-stack type safety — designs shared type schemas between frontend and backend with code generation, implements end-to-end type-safe APIs with tRPC or GraphQL codegen, and architects monorepo type sharing strategies. Mentors team on maintaining type consistency across system boundaries, runtime validation at API edges, and balancing type strictness with development velocity. |
| Game Server Developer | Implements advanced typing for correctness guarantees — phantom types for entity IDs, branded types for validated data, end-to-end typing from protocol to storage. | |
| Infrastructure Engineer | Designs type-safe infrastructure abstractions with generic types for reusable modules. Implements custom validation rules and type guards for preventing invalid infrastructure configurations. | |
| iOS Developer | Architects type-safe iOS application architecture with compile-time correctness guarantees through protocol witnesses and type erasure. Implements code generation via SwiftGen and Sourcery for typed resources and strictly typed navigation routes. | |
| IoT Engineer | Designs type-safe architectures for IoT: phantom types for units of measurement, branded types for device identifiers, compile-time protocol configuration validation. | |
| Language Tooling Engineer | 必要 | Has deep expertise in type system theory and implementation — designs type inference engines, implements constraint-based type solvers, and builds type-aware refactoring tools. Architects gradual typing systems balancing soundness with adoption ergonomics. Mentors team on formal type theory foundations, decidability trade-offs in type checking, and practical type system design patterns. |
| LLM Engineer | Designs type-safe LLM systems: schema-driven output, typed tool interfaces, contract validation. | |
| ML Engineer | Designs type-safe ML pipelines with runtime validation via Pandera for DataFrames and Great Expectations for data. Introduces generic types for reusable components: transformers, encoders, validators. | |
| MLOps Engineer | Architects type-safe ML systems: protocols for model interfaces, generic types for pipeline operators, compile-time validation of training and deployment configurations. | |
| NLP Engineer | Designs type-safe NLP system architecture with runtime validation. Creates typed ML pipeline interfaces ensuring contract compatibility between components. | |
| Performance Testing Engineer | Designs type-safe performance frameworks: generic types for different testing protocols, compile-time test scenario validation, typed APIs for reporting. | |
| Platform Engineer | Designs type-safe platform: CUE/Jsonnet for typed configs, generated type-safe clients, schema validation pipeline. Defines type safety strategy. | |
| QA Automation Engineer | Designs type-safe test infrastructure — end-to-end typing from API schema to assertions, type auto-generation from OpenAPI, discriminated unions for test data. | |
| QA Engineer (Manual) | Designs type safety testing strategy for the project: schema validation, contract testing, type coverage. Develops methodology for detecting type-related defects through TypeScript/schema definition analysis. Defines tools and automatic type conformance checks in CI pipeline. | |
| React Native Developer | 必要 | Develops advanced types for React Native architecture — type-safe navigation, typed routes, branded types for entity IDs. Designs type-safe API layer with auto-generated types from OpenAPI/GraphQL schemas. Implements runtime validation via Zod for native module data. |
| Site Reliability Engineer (SRE) | Designs type-safe infrastructure: CUE for configuration validation, typed deployment pipelines, schema validation for infrastructure-as-data. | |
| Smart Contract Developer | 必要 | Has deep expertise in smart contract type safety — designs type-safe DeFi protocol interfaces with custom value types for financial primitives, implements formal verification compatible type patterns, and architects upgradeable contract systems with type-safe storage layouts. Mentors team on ABI encoding type safety, cross-contract type compatibility, and type-driven security patterns for preventing common vulnerabilities. |
| Solutions Architect | Defines type safety architecture: end-to-end type contracts, schema registry, automated validation. Designs type-safe platform. | |
| Systems Programmer (C/C++) | 必要 | Has deep expertise in systems-level type safety — designs type-safe kernel interfaces with zero-cost abstractions, implements compile-time state machine verification through typestate patterns, and leverages type-level programming for memory layout guarantees. Architects type-safe FFI boundaries and hardware abstraction layers. Mentors team on unsafe code auditing, type-driven correctness proofs, and balancing type system expressiveness with compilation performance. |
| Technical Lead | Designs type-safe systems: end-to-end type safety, branded types, type-driven design. Implements typing standards and automated checks. | |
| Telecom Developer | Designs type-safe frameworks for telecom protocols with compile-time message encoding and state machine verification. Implements branded types for separating different identifiers: IMSI, MSISDN, session-id. |
| 角色 | 必要性 | 描述 |
|---|---|---|
| 1C Developer | Defines type safety standards for all 1C projects in the organization. Establishes guidelines for attribute typing, API parameters, and exchange data to prevent errors. | |
| AI Product Engineer | Defines typing standards for AI product teams, including type-safe abstractions for ML operations and data pipelines. Ensures type consistency between frontend, backend, and ML services of the product platform. | |
| Analytics Engineer | Defines typing standards for the analytics platform, including data contracts and schema governance. Ensures type consistency between ETL pipelines, warehouse, and analytics APIs for data reliability. | |
| Android Developer | Defines type safety standards for all Android projects in the organization. Establishes architectural guidelines for using the Kotlin type system to prevent errors. | |
| Backend Developer (C#/.NET) | 必要 | Defines typing strategy: nullable reference types, required members, init-only properties. Implements strict null checks via <Nullable>enable</Nullable>. Controls warning-as-error in CI. |
| Backend Developer (Elixir) | Defines typing standards in Elixir: mandatory typespecs policy, Dialyzer configuration, type documentation requirements. Implements automated type checking. | |
| Backend Developer (Go) | Defines type safety standards: custom type conventions, interface design guidelines, generics usage policies. | |
| Backend Developer (Java/Kotlin) | 必要 | Defines Java project typing strategy: NullAway/Checker Framework, sealed interfaces for domain modeling, record classes for DTOs. Implements strict null checks in CI pipeline. |
| Backend Developer (Node.js) | 必要 | Defines typing strategy: TypeScript strict mode, Zod for runtime validation, tRPC for end-to-end type safety. Controls tsconfig strictness and no-any policy. |
| Backend Developer (PHP) | 必要 | Defines typing strategy for the codebase: strict_types, PHPStan level, generics via annotations. Implements Value Objects and enums for business logic. Controls type coverage via CI. |
| Backend Developer (Python) | 必要 | Implements typing strategy for the organization. Establishes type hint standards and guidelines. Configures type checking infrastructure in CI. Trains the team on advanced typing. |
| Backend Developer (Rust) | 必要 | Designs APIs with maximum type safety: newtype patterns for domain types, phantom types for compile-time invariants, exhaustive enums instead of string constants. Implements typestate pattern for guaranteeing protocol correctness at the type level. |
| Backend Developer (Scala) | 必要 | Establishes team standards for Scala type system usage: refined types for validation, phantom types for states, opaque types for domain primitives. Reviews type-level programming correctness, ensures balance between type safety and code readability. |
| Blockchain Developer | Defines type safety standards: typed contracts, validation requirements. | |
| Compiler Engineer | Establishes type safety 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 typing standards for the CV team, ensures consistency in ML code. Integrates type checking into CI/CD and organizes legacy code migration to typed Python. | |
| Data Engineer | Defines type safety standards: schema governance, validation requirements, typed pipeline policies. | |
| Desktop Developer (.NET WPF/WinUI/MAUI) | 必要 | Defines type safety strategy for .NET desktop. Establishes guidelines for nullable, records, pattern matching. Conducts reviews focused on type safety. |
| Desktop Developer (Electron/Tauri) | 必要 | Defines TypeScript strategy for the Electron team. Establishes type safety guidelines. Conducts reviews focused on typing. |
| Desktop Developer (Qt/C++) | 必要 | Defines typing strategy for Qt projects. Establishes guidelines for C++20/23 type safety features. Conducts review focusing on type safety. |
| DevOps Engineer | Defines type safety standards: typed IaC requirements, configuration validation policies. Implements automated type checking. | |
| Embedded Developer | Defines type safety standards for the embedded team. Establishes guidelines for type-safe hardware access, conducts reviews. | |
| Engineering Manager | Defines type safety policy for the department, coordinates language and framework selection considering typing. Evaluates the impact of strict typing on team productivity. | |
| Flutter Developer | 必要 | Defines type safety standards for Flutter development teams — establishes Dart analysis options, null safety migration policies, and type-safe serialization codegen requirements. Conducts architectural reviews ensuring consistent type patterns across widget libraries, state management, and API client layers. |
| Frontend Developer (Angular) | 必要 | Ensures maximum type safety in the Angular project: strict TypeScript and Angular compiler mode, typed interceptors and guards, auto-generated types from OpenAPI schemas for HttpClient. |
| Frontend Developer (React) | 必要 | Standardizes typing approaches in the team's React projects: strict TypeScript configuration, shared types between frontend and backend, auto-generated types from API schemas (OpenAPI, GraphQL codegen). Defines migration strategy away from any. |
| Frontend Developer (Svelte) | 必要 | Standardizes typing strategy for the team's Svelte projects: shared types between packages, auto-generation from OpenAPI schemas, strict tsconfig settings. Ensures zero-any policy, introduces incremental typing during Svelte 5 and TypeScript strict migration. |
| Frontend Developer (Vue) | 必要 | Defines typing strategy for organizational Vue projects — config strictness, JavaScript migration, runtime validation integration. Introduces end-to-end type safety from API to templates through tRPC or typed fetch. |
| Fullstack Developer | 必要 | Ensures end-to-end type safety in fullstack applications: from database schema through Prisma/Drizzle to tRPC or typed GraphQL resolvers and auto-generated frontend types. Implements Zod validation at layer boundaries, configures strict TypeScript for the entire monorepo. |
| Game Server Developer | Defines typing standards for the server codebase. Selects tools and approaches, ensures strict types at service boundaries, and auto-generates types from protocol schemas. | |
| Infrastructure Engineer | Defines type safety standards for organizational infrastructure code with automatic verification in CI/CD. Designs type-safe API for internal platform with compile-time configuration checks. | |
| iOS Developer | Defines type safety standards for the iOS team, including typed API contracts and shared models with the server team. Ensures type consistency between iOS client and backend through OpenAPI code generation and Codable contracts. | |
| IoT Engineer | Defines type safety standards for the IoT team: mandatory strict modes, typed device data serialization, code review criteria for preventing type-unsafe code. | |
| Language Tooling Engineer | 必要 | Defines type system design standards for language tooling products — establishes type inference algorithm requirements, error reporting quality standards, and type checker performance benchmarks. Conducts architectural reviews ensuring consistent type system implementation across compiler stages and IDE integration layers. |
| LLM Engineer | Defines type safety standards: output schema requirements, validation policies. | |
| ML Engineer | Defines type safety standards for organizational ML codebase with mypy strict mode and pre-commit hooks. Designs type-safe SDK for ML platform with compile-time experiment configuration verification. | |
| MLOps Engineer | Defines type safety standards for the MLOps team: mandatory type hints, mypy/pyright in CI, typed SDKs for ML platform interaction, code review criteria. | |
| NLP Engineer | Defines typing standards for all organizational ML/NLP projects. Establishes type safety requirements for pipelines and ensures contract-based interaction between ML services. | |
| Performance Testing Engineer | Defines type safety standards for the performance team: mandatory script typing, type-safe configurations, code review criteria for preventing runtime errors in tests. | |
| Platform Engineer | Defines type safety standards: typed CRD requirements, configuration validation, schema evolution policies. Implements automated type checking. | |
| QA Automation Engineer | Defines typing standards for the team's test framework. Selects tools and approaches, enforces strict mode, implements type auto-generation in the CI/CD pipeline. | |
| QA Engineer (Manual) | Defines type safety standards for test automation code at the team/product level. Conducts reviews. Establishes best practices for typed test frameworks. | |
| React Native Developer | 必要 | Defines the typing strategy for the team's React Native projects. Establishes TypeScript guidelines — strict settings, any ban, mandatory types for public API. Reviews type architecture — proper use of generics, conditional types, template literal types. |
| Site Reliability Engineer (SRE) | Defines SRE type safety standards: typed IaC requirements, configuration validation policies. Implements automated type checking for infrastructure code. | |
| Smart Contract Developer | 必要 | Defines type safety standards for smart contract development teams — establishes custom type requirements for financial primitives, ABI-safe interface patterns, and formal verification compatible type hierarchies. Conducts architectural reviews ensuring type-safe storage layouts, upgrade compatibility, and cross-protocol type consistency. |
| Solutions Architect | Defines type safety standards: typing requirements, schema governance, contract validation. Coordinates cross-team type safety. | |
| Systems Programmer (C/C++) | 必要 | Defines type safety standards for systems programming teams — establishes unsafe code review policies, type-safe FFI boundary requirements, and compile-time verification standards. Conducts architectural reviews ensuring consistent type patterns across kernel interfaces, hardware abstraction layers, and performance-critical paths. |
| Technical Lead | Defines type safety standards: strict mode requirements, type coverage metrics, no-any policies. Trains the team on type-driven development. | |
| Telecom Developer | Defines type safety standards for the telecom codebase with automatic type generation from ASN.1 and protobufs. Designs type-safe DSL for telecom business rules and billing. |
| 角色 | 必要性 | 描述 |
|---|---|---|
| 1C Developer | Shapes organizational culture of type-safe development in 1C. Defines data validation and typing standards that improve reliability and predictability of all 1C systems. | |
| AI Product Engineer | Shapes corporate type safety strategy for the AI product ecosystem with end-to-end typing from data to UI. Defines architectural patterns that minimize runtime errors in critical ML systems. | |
| Analytics Engineer | Shapes the corporate type safety strategy for the analytics ecosystem with end-to-end data contracts. Defines the schema registry and governance architecture ensuring quality at scale in enterprise analytics systems. | |
| Android Developer | Shapes the organizational culture of type-safe Android development. Defines typing standards and architectural patterns improving reliability of all mobile products. | |
| Backend Developer (C#/.NET) | 必要 | Shapes .NET platform typing standards. Evaluates C# evolution (discriminated unions, roles/extensions) and plans adoption. Designs type-safe inter-service contracts. |
| Backend Developer (Elixir) | Shapes type safety strategy for the Elixir platform: gradual typing adoption, cross-service type contracts, evaluation of new type systems (TypedElixir). | |
| Backend Developer (Go) | Shapes type safety strategy: Go type system best practices, generics adoption, type-driven design. | |
| Backend Developer (Java/Kotlin) | 必要 | Shapes Java platform typing standards. Evaluates type system evolution (pattern matching, sealed classes, value types/Valhalla) and plans adoption. Designs type-safe inter-service contracts. |
| Backend Developer (Node.js) | 必要 | Shapes Node.js platform typing standards: shared type packages, branded types for domain safety, type-safe ORM (Prisma/Drizzle). Evaluates new TypeScript features for adoption. |
| Backend Developer (PHP) | 必要 | Shapes typing standards at platform level. Evaluates PHP type system evolution and plans migration. Determines balance between type strictness and development productivity. |
| Backend Developer (Python) | 必要 | Defines typing standards at company level. Participates in PEP discussions on typing. Evaluates runtime type checkers (pydantic, beartype). Shapes gradual typing strategy for legacy code. |
| Backend Developer (Rust) | 必要 | Shapes type safety strategy for the entire codebase: session types for protocols, refinement types through const generics, branded types for preventing ID mixing. Defines 'making invalid states unrepresentable' standards and develops type-level state machines for critical business logic. |
| Backend Developer (Scala) | 必要 | Defines type safety strategy for Scala platform: leveraging Scala 3 match types, inline/given, compile-time type-level checks. Designs domain DSLs with correctness guarantees through the type system, makes decisions on applying dependent types and type-level computations. |
| Blockchain Developer | Shapes type safety strategy: blockchain type system, governance. | |
| Compiler Engineer | Shapes type safety 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 type safety strategy for the organization's ML platform. Defines typing standards at the Python/C++ boundary and cross-language integration in CV systems. | |
| Data Engineer | Shapes type safety strategy: platform-wide schema management, data contract validation, type-driven data engineering. | |
| Desktop Developer (.NET WPF/WinUI/MAUI) | 必要 | Shapes enterprise type safety standards for .NET. Evaluates new type safety features (C# 13+). Defines balance between type safety and pragmatism. |
| Desktop Developer (Electron/Tauri) | 必要 | Shapes enterprise TypeScript standards for Electron. Evaluates TypeScript evolution. Defines type safety architecture. |
| Desktop Developer (Qt/C++) | 必要 | Shapes enterprise typing standards for C++/Qt. Evaluates new type safety features (C++26). Defines the balance between type safety and ergonomics. |
| DevOps Engineer | Shapes type safety strategy: end-to-end typed infrastructure, configuration language selection, type-driven DevOps practices. | |
| Embedded Developer | Defines enterprise type safety strategy for embedded. Establishes type-safe HAL framework for all MCU platforms. | |
| Engineering Manager | Shapes type safety strategy at the organizational level, defines cross-language interaction standards. Coordinates type-safe approach usage in distributed systems. | |
| Flutter Developer | 必要 | Defines organizational strategy for type safety in Flutter/Dart ecosystems — makes strategic decisions on analysis strictness levels, codegen tooling adoption, and cross-platform type sharing approaches. Mentors lead developers on type-driven architecture and shapes technical vision for type-safe mobile development practices. |
| Frontend Developer (Angular) | 必要 | Defines typing strategy for the Angular platform: schema-first approach with type generation, type-safe routing via typedRoutes, custom TypeScript plugins for verifying Angular-specific patterns. |
| Frontend Developer (React) | 必要 | Defines type safety strategy for the React application ecosystem. Designs end-to-end type safety from DB to UI through tRPC/GraphQL codegen, shared type packages in monorepo, automatic type generation from contracts. |
| Frontend Developer (Svelte) | 必要 | Defines platform-level type safety architecture, researches extended typing capabilities for Svelte 5 runes. Influences TypeScript support in Svelte through contributions to svelte-language-server and svelte2tsx, shapes industry standards. |
| Frontend Developer (Vue) | 必要 | Shapes type safety architecture for the entire Vue ecosystem — shared types between services, code generation from OpenAPI, automated type compatibility checks between Vue micro-frontends. |
| Fullstack Developer | 必要 | Designs end-to-end type safety strategy for organizational fullstack platform. Creates type code generation tooling from a single source of truth (OpenAPI, Prisma schema). Defines contract testing standards between frontend and backend. |
| Game Server Developer | Shapes type-safety strategy for the studio's server platform. Explores formal verification approaches for critical systems and promotes type safety as an engineering value. | |
| Infrastructure Engineer | Shapes type safety strategy for infrastructure platform, defining balance between flexibility and strictness. Defines typing approaches for multi-cloud abstractions and cross-provider modules. | |
| iOS Developer | Shapes the corporate type safety strategy for the mobile ecosystem with end-to-end typing from server to UI. Defines architectural patterns minimizing runtime errors in enterprise-scale critical mobile applications. | |
| IoT Engineer | Shapes type safety strategy for IoT ecosystem: standard types for communication protocols, typed DSLs for device configuration, integration with formal verification. | |
| Language Tooling Engineer | 必要 | Defines organizational strategy for type system design in language tooling products — makes strategic decisions on type theory foundations, gradual typing adoption roadmaps, and type checker scalability approaches. Mentors lead developers on type system research and shapes technical vision for type-safe language tooling innovation. |
| LLM Engineer | Shapes type safety strategy: LLM output governance, schema management. | |
| ML Engineer | Shapes type safety strategy for ML platform, including schema registry for features and model signatures. Defines contract-based development approaches for ML pipelines with automated schema evolution. | |
| MLOps Engineer | Shapes the type safety strategy for the ML ecosystem: standard types for ML artifacts, typed DSL for pipeline descriptions, integration with schema validation at all levels. | |
| NLP Engineer | Shapes organizational culture of type-safe ML development. Defines typing standards for the AI industry that improve NLP system reliability and predictability. | |
| Performance Testing Engineer | Shapes type safety strategy for performance engineering: standard types for metrics and SLI, typed DSL for describing load scenarios, integration with CI validation. | |
| Platform Engineer | Shapes platform type safety strategy: end-to-end typed platform, configuration language selection, type-driven platform design. | |
| QA Automation Engineer | Shapes type-safety strategy for the organization's test platform. Promotes contract-first testing approach with automatic typed test client generation. | |
| QA Engineer (Manual) | Shapes corporate QA methodology for type safety in strongly-typed and schema-driven systems. Defines industry standards for testing type correctness in APIs and data flows. Explores automation of type-aware testing through AI and formal verification. | |
| React Native Developer | 必要 | Shapes enterprise typing standards in mobile development. Defines shared types strategy between React Native and backend. Designs monorepo architecture with type-safe code reuse across iOS, Android, and web through shared TypeScript packages. |
| Site Reliability Engineer (SRE) | Shapes type safety strategy for infrastructure: platform-wide configuration typing, automated validation, technology evaluation. Defines adoption roadmap. | |
| Smart Contract Developer | 必要 | Defines organizational strategy for type safety in smart contract development — makes strategic decisions on formal verification tooling, type-safe upgrade patterns, and cross-chain type compatibility standards. Mentors lead developers on type-driven contract security and shapes technical vision for type-safe DeFi protocol engineering. |
| Solutions Architect | Shapes type safety strategy: organizational typing strategy, schema evolution governance, type-driven design principles. | |
| Systems Programmer (C/C++) | 必要 | Defines organizational strategy for type safety in systems programming — makes strategic decisions on type-safe kernel interface design, compile-time verification tooling, and language-level safety guarantees for performance-critical systems. Mentors lead developers on type-driven systems architecture and shapes technical vision for provably safe systems software development. |
| Technical Lead | Shapes the organization's type safety strategy: cross-service type contracts, shared type packages, technology evaluation. Defines adoption strategy. | |
| Telecom Developer | Shapes type safety strategy for the telecom platform, including protocol-level type checking and formal verification. Defines typing approaches for 5G service models and network function interfaces. |