Domäne
API & Integration
Skill-Profil
Schema design, resolvers, subscriptions, federation, N+1 (DataLoader)
Rollen
60
wo dieser Skill vorkommt
Stufen
5
strukturierter Entwicklungspfad
Pflichtanforderungen
73
die anderen 224 optional
API & Integration
GraphQL
17.3.2026
Wählen Sie Ihr aktuelles Level und vergleichen Sie die Erwartungen.
Die Tabelle zeigt, wie die Tiefe von Junior bis Principal wächst.
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| 1C Developer | Understands basics of GraphQL schema design for 1C platform data exposure. Reads and interprets GraphQL queries when integrating 1C with modern frontends. Follows team conventions for defining types that map to 1C business entities. | |
| AI Product Engineer | Understands basics of GraphQL schema design for ML model serving and experiment tracking APIs. Writes simple queries and mutations for model metadata and prediction endpoints. Follows team conventions for exposing AI feature catalogs through GraphQL interfaces. | |
| Analytics Engineer | Studies GraphQL basics and its application for creating analytics APIs. Understands concepts of queries, mutations, and schema-first approach for providing analytical data to consumers. | |
| Android Developer | Performs basic GraphQL queries in Android via Apollo Kotlin: writing simple queries and mutations in .graphql files, receiving typed responses. Understands the difference between query and mutation, uses generated Apollo classes for data access, handles basic GraphQL response errors under mentor guidance. | |
| Application Security Engineer | Understands basics of GraphQL from a security perspective — query depth limits, introspection risks, and authorization patterns. Reviews simple GraphQL schemas for common vulnerabilities. Follows team guidelines for security testing of GraphQL endpoints. | |
| Backend Developer (C#/.NET) | Pflicht | Creates GraphQL schemas via Hot Chocolate: types, queries, mutations. Implements resolvers. Understands differences with REST. Tests via Banana Cake Pop. |
| Backend Developer (Elixir) | Pflicht | Creates basic GraphQL schemas in Elixir using Absinthe. Defines types, queries and mutations through Absinthe DSL. Connects resolvers to Phoenix Ecto contexts, returns data with basic error handling through {:ok, data} and {:error, message}. |
| Backend Developer (Go) | Creates GraphQL APIs in Go: gqlgen for type-safe schemas, queries/mutations. Understands gqlgen's code generation approach. | |
| Backend Developer (Java/Kotlin) | Pflicht | Creates simple GraphQL schemas via Spring for GraphQL: types, queries, mutations. Implements resolvers with @QueryMapping/@MutationMapping. Understands the difference between REST and GraphQL. Tests via GraphiQL. |
| Backend Developer (Node.js) | Pflicht | Creates GraphQL API via Apollo Server/Mercurius: type definitions, resolvers, queries and mutations. Understands schema-first vs code-first. Tests via GraphQL Playground. |
| Backend Developer (PHP) | Pflicht | Creates simple GraphQL schemas: types, queries, mutations. Understands the difference from REST. Implements resolvers for basic operations. Uses GraphQL playground for testing. |
| Backend Developer (Python) | Understands GraphQL concepts: queries, mutations, schema. Creates simple resolvers with Strawberry or Graphene. Knows the difference between REST and GraphQL. Uses GraphiQL for testing. | |
| Backend Developer (Rust) | Creates GraphQL API in Rust: async-graphql or Juniper for schema, queries/mutations. Understands type-safe GraphQL through Rust type system. | |
| Backend Developer (Scala) | Creates GraphQL API in Scala: Sangria or Caliban for schema definition, queries/mutations. Understands type-safe GraphQL through Scala type system. | |
| Blockchain Developer | Understands basics of GraphQL schema design for blockchain data indexing and querying. Writes simple queries against subgraph APIs for on-chain event data. Follows team conventions for exposing smart contract state through GraphQL interfaces like The Graph. | |
| Cloud Engineer | Understands GraphQL in cloud context: AWS AppSync for API, basic queries and mutations. Uses GraphQL Playground for testing cloud APIs. | |
| Computer Vision Engineer | Understands basics of GraphQL schema design for computer vision service APIs. Writes simple queries for image processing task submission and result retrieval. Follows team conventions for defining types that represent vision model outputs and annotation data. | |
| Data Analyst | Understands basics of GraphQL as a data querying interface for analytical dashboards. Writes simple queries to retrieve dataset metadata and aggregated metrics. Follows team conventions for accessing data catalog and reporting APIs via GraphQL. | |
| Data Engineer | Understands GraphQL for data access: query API for data catalog, metadata queries. Works with GraphQL-based data tools. | |
| Data Scientist | Understands GraphQL for DS: flexible data queries for ML features, metadata exploration. | |
| Desktop Developer (.NET WPF/WinUI/MAUI) | Studies GraphQL basics and its use for .NET desktop application interaction with server API. Understands query, mutation and subscription concepts through HotChocolate for data-rich desktop clients. | |
| Desktop Developer (Electron/Tauri) | Understands basics of GraphQL schema design for Electron application data layers. Writes simple queries and mutations for syncing desktop app state with backend services. Follows team conventions for structuring GraphQL client integrations in Electron renderers. | |
| Desktop Developer (Qt/C++) | Studies GraphQL basics and its application for Qt application interaction with server APIs. Understands query, mutation and subscription concepts as an alternative to REST for data-rich desktop applications. | |
| DevOps Engineer | Understands GraphQL for DevOps: monitoring GraphQL services, deployment configuration. Configures health checks and alerting. | |
| DevSecOps Engineer | Understands basics of GraphQL from a DevSecOps perspective — rate limiting, query cost analysis, and authentication patterns. Monitors GraphQL endpoint security configurations in CI/CD pipelines. Follows team guidelines for scanning GraphQL schemas for security misconfigurations. | |
| Embedded Developer | Understands basics of GraphQL as an interface for embedded device management APIs. Reads GraphQL queries for device configuration and telemetry retrieval endpoints. Follows team conventions for lightweight GraphQL client usage on resource-constrained devices. | |
| Engineering Manager | Understands basics of GraphQL Design to evaluate API strategy decisions for managed teams. Reviews GraphQL schema proposals from an architectural consistency perspective. Follows organizational guidelines for API design review processes. | |
| Flutter Developer | Understands basics of GraphQL schema design for Flutter mobile and web applications. Writes simple queries using graphql_flutter package for data fetching and caching. Follows team conventions for structuring GraphQL operations alongside Flutter state management. | |
| Frontend Developer (Angular) | Understands basics of GraphQL schema design for Angular applications. Writes simple queries and mutations using Apollo Angular client for component data binding. Follows team conventions for organizing GraphQL operations with Angular services and dependency injection. | |
| Frontend Developer (React) | Uses GraphQL in React components through Apollo Client or urql: writing queries and mutations, handling loading and error states. Understands GraphQL schema basics, uses GraphQL Playground for API exploration, basic typing through codegen. | |
| Frontend Developer (Svelte) | Connects a GraphQL client (urql, houdini) to a SvelteKit application, executes basic queries in load functions. Understands GraphQL schema, types, and variables, displays data in Svelte components through reactive stores of the client library. | |
| Frontend Developer (Vue) | Uses GraphQL API from Vue components through urql or Apollo Client. Writes basic queries and mutations, understands GraphQL syntax, handles loading and error states in Vue templates. | |
| Fullstack Developer | Uses GraphQL queries in fullstack applications: writes queries and mutations on the frontend with Apollo Client or urql. Understands GraphQL advantage for frontend — requesting only needed fields, avoiding over-fetching compared to REST. | |
| Game QA Engineer | Understands GraphQL for game QA: tests GraphQL endpoints for game services, query validation. Uses GraphQL playground. | |
| Game Server Developer | Understands basics of GraphQL schema design for game backend services. Writes simple queries for player profile, inventory, and matchmaking data endpoints. Follows team conventions for exposing game state through GraphQL subscriptions and queries. | |
| Infrastructure Engineer | Understands basics of GraphQL as an interface for infrastructure management APIs. Reads GraphQL queries for resource provisioning and monitoring dashboards. Follows team conventions for infrastructure-as-code tool GraphQL API integrations. | |
| iOS Developer | Performs basic GraphQL queries from iOS applications using Apollo iOS or URLSession. Understands query and mutation structure, parses responses via generated Swift types. Uses GraphQL Playground to explore API schema, forms queries with arguments, and retrieves only needed data fields. | |
| IoT Engineer | Understands basics of GraphQL schema design for IoT device management and data querying APIs. Writes simple queries for device registry, telemetry history, and fleet status endpoints. Follows team conventions for exposing IoT platform capabilities through GraphQL interfaces. | |
| Language Tooling Engineer | Understands basics of GraphQL schema design for language service APIs and developer tool integrations. Writes simple queries for code analysis results and symbol information endpoints. Follows team conventions for exposing compiler/analyzer data through GraphQL interfaces. | |
| LLM Engineer | Understands GraphQL for LLM: query API for prompt management, metadata access. | |
| ML Engineer | Understands basics of GraphQL schema design for ML experiment tracking and model registry APIs. Writes simple queries for model metadata, training metrics, and dataset information. Follows team conventions for exposing ML pipeline states through GraphQL interfaces. | |
| MLOps Engineer | Understands basics of GraphQL schema design for MLOps platform APIs — model deployment, pipeline orchestration, and monitoring. Writes simple queries for experiment comparison and resource utilization endpoints. Follows team conventions for GraphQL access to ML infrastructure dashboards. | |
| NLP Engineer | Understands basics of GraphQL schema design for NLP service APIs — text analysis, entity extraction, and language model endpoints. Writes simple queries for submitting text processing tasks and retrieving results. Follows team conventions for exposing NLP pipeline capabilities through GraphQL. | |
| Penetration Testing Engineer | Understands basics of GraphQL from a penetration testing perspective — introspection enumeration, query injection, and authorization bypass vectors. Performs basic reconnaissance of GraphQL endpoints. Follows team methodologies for initial GraphQL security assessment. | |
| Performance Testing Engineer | Understands basics of GraphQL query performance characteristics — N+1 problems, query depth impact, and resolver execution patterns. Writes simple load tests for GraphQL endpoints using tools like k6 or Artillery. Follows team guidelines for baseline performance benchmarking of GraphQL APIs. | |
| Platform Engineer | Understands GraphQL for platform: query API for resource discovery, introspection. Uses GraphQL playground for platform API exploration. | |
| QA Automation Engineer | Understands basics of GraphQL schema design for automated API testing. Writes simple query and mutation tests verifying schema conformance and data types. Follows team conventions for organizing GraphQL test suites and validating response structures. | |
| QA Engineer (Manual) | Understands basics of GraphQL query structure for manual API testing using tools like GraphiQL or Postman. Writes simple test scenarios validating query responses against expected data. Follows team conventions for documenting GraphQL test cases and exploratory testing of schema endpoints. | |
| QA Security Engineer | Understands basics of GraphQL security testing — introspection exposure, query complexity attacks, and field-level authorization validation. Writes simple security test cases for GraphQL endpoints. Follows team guidelines for GraphQL vulnerability scanning and authentication testing. | |
| React Native Developer | Performs basic GraphQL queries from React Native — queries and mutations with Apollo Client or urql. Understands schema, types, variables. Uses useQuery/useMutation hooks for fetching and sending data. Handles GraphQL errors and displays results in components. | |
| Release Engineer | Understands basics of GraphQL schema versioning and its impact on release processes. Monitors GraphQL schema changes for breaking compatibility in deployment pipelines. Follows team conventions for including GraphQL schema validation in release checklists. | |
| Site Reliability Engineer (SRE) | Understands GraphQL for SRE: monitors GraphQL services, understands query complexity. Configures health checks and alerting for GraphQL endpoints. | |
| Smart Contract Developer | Understands GraphQL for blockchain: The Graph for indexed queries, subgraph basics. | |
| Systems Programmer (C/C++) | Understands GraphQL for systems: query API for system monitoring, metadata access. | |
| Technical Writer | Understands basics of GraphQL schema design to write accurate API documentation. Reads and interprets GraphQL type definitions, queries, and mutations for documentation purposes. Follows team conventions for documenting GraphQL endpoints using tools like GraphQL Playground and schema annotations. | |
| Telecom Developer | Understands basics of GraphQL schema design for telecom network management APIs. Writes simple queries for network element configuration and service inventory endpoints. Follows team conventions for exposing telecom OSS/BSS data through GraphQL interfaces. | |
| Unity Developer | Understands GraphQL for Unity: query API for game data, flexible data fetching. Uses GraphQL client. | |
| Unreal Engine Developer | Understands GraphQL for Unreal backend: query API for game data, flexible fetching. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| 1C Developer | Designs GraphQL API for exposing 1C data to external consumers. Implements efficient resolvers for working with registers, documents, and catalogs through typed schemas. | |
| AI Product Engineer | Independently designs GraphQL schemas for AI product APIs with efficient model serving query patterns. Implements resolvers for feature store data, experiment metadata, and prediction result aggregations. Writes comprehensive schema tests and generates interactive API documentation. | |
| Analytics Engineer | Implements GraphQL APIs for analytics data access with flexible filtering and aggregation. Designs schemas for analytical entities with pagination, nested resolvers, and N+1 query optimization against the warehouse. | |
| Android Developer | Works with Apollo Kotlin Client in Android projects: normalized cache configuration for offline access, pagination implementation via Relay-style connections, fragment usage for field reuse. Handles GraphQL errors and partial responses, configures custom scalar adapters for dates and ID types, implements optimistic UI updates for mutations. | |
| Application Security Engineer | Conducts security audits of GraphQL APIs: checks depth limiting, query complexity, field-level and resolver authorization. Identifies vulnerabilities in GraphQL service schemas and implementations. | |
| Backend Developer (C#/.NET) | Pflicht | Designs GraphQL API: custom scalars, DataLoader for N+1, pagination via Relay. Configures filtering/sorting via Hot Chocolate conventions. Handles errors through error filter middleware. |
| Backend Developer (Elixir) | Pflicht | Develops GraphQL API on Absinthe with nested types, enums and interfaces. Solves N+1 problem through Dataloader and batch resolvers. Implements Relay-style pagination with cursors, configures Absinthe middleware for logging and authentication. |
| Backend Developer (Go) | Designs GraphQL in Go: gqlgen with DataLoader, subscriptions, custom scalars. Optimizes resolver performance. | |
| Backend Developer (Java/Kotlin) | Pflicht | Designs GraphQL API for Java services: custom scalars, input types, enum mapping. Implements DataLoader to solve N+1. Configures pagination via Relay Connection spec. Handles errors through GraphQL error extensions. |
| Backend Developer (Node.js) | Pflicht | Designs GraphQL schemas: input types for mutations, pagination (Relay connections), error handling. Optimizes: DataLoader for N+1, query complexity limits, persisted queries. |
| Backend Developer (PHP) | Pflicht | Designs efficient schemas: relay-style pagination, input types, unions/interfaces for polymorphism. Solves N+1 via DataLoader. Implements subscriptions for real-time. Configures query complexity limits. |
| Backend Developer (Python) | Designs GraphQL schema with types and interfaces. Implements DataLoader to solve N+1. Configures authentication and authorization. Uses subscriptions for real-time. Handles errors via custom error types. | |
| Backend Developer (Rust) | Designs GraphQL solutions in Rust: async-graphql with DataLoader, subscriptions, custom scalars. Optimizes N+1 through batch loading. | |
| Backend Developer (Scala) | Designs GraphQL solutions in Scala: Caliban for type-safe schemas, ZIO integration, DataLoader for N+1. Implements subscriptions and authorization. | |
| Blockchain Developer | Independently designs GraphQL schemas for blockchain data indexing using The Graph or custom subgraphs. Implements efficient resolvers for on-chain event queries, token transfer histories, and DeFi protocol analytics. Writes comprehensive subgraph tests and schema documentation. | |
| Cloud Engineer | Designs GraphQL API on cloud services: AppSync with DynamoDB resolvers, authorization through Cognito, subscriptions for real-time. Optimizes resolver performance. | |
| Computer Vision Engineer | Designs GraphQL schemas for CV API — prediction queries, batch inference, model management. Implements subscriptions for real-time processing result updates. | |
| Data Analyst | Designs GraphQL schemas for analytical APIs, implements resolvers for data aggregation from multiple sources. Optimizes queries using DataLoader and pagination. | |
| Data Engineer | Designs GraphQL API for data: metadata queries, lineage exploration, data preview endpoints. Implements authorization. | |
| Data Scientist | Designs GraphQL for ML: feature discovery API, model metadata queries, experiment exploration. | |
| Desktop Developer (.NET WPF/WinUI/MAUI) | Implements GraphQL interaction in .NET desktop applications through StrawberryShake for type-safe data retrieval. Designs queries with traffic minimization and optimal data loading for WPF interfaces. | |
| Desktop Developer (Electron/Tauri) | Integrates GraphQL client into Electron application with caching, optimistic updates and offline support. Designs GraphQL schemas for efficient data exchange with the desktop client. | |
| Desktop Developer (Qt/C++) | Implements GraphQL interaction in Qt applications for flexible server data retrieval. Designs queries with traffic minimization and optimal data loading for desktop interfaces with rich visualization. | |
| DevOps Engineer | Provides DevOps for GraphQL: deployment pipelines, performance monitoring, scaling configuration. Configures GraphQL-specific metrics. | |
| DevSecOps Engineer | Designs secure GraphQL APIs with query depth limiting, rate limiting and query complexity analysis. Implements field-level and type-level authorization for protecting sensitive data in GraphQL schema. | |
| Embedded Developer | Designs GraphQL schemas for IoT platform with types for devices, telemetry and control commands. Implements resolvers with N+1 query optimization and DataLoader configuration for batch data loading. | |
| Engineering Manager | Makes decisions on GraphQL usage in team projects, evaluates schema complexity and performance. Defines GraphQL API design standards. | |
| Flutter Developer | Independently designs GraphQL schemas optimized for Flutter mobile and web client consumption. Implements efficient query patterns with graphql_flutter for offline-first caching and optimistic updates. Writes comprehensive widget-level tests for GraphQL data binding and documents API usage patterns. | |
| Frontend Developer (Angular) | Configures Apollo Angular: Apollo Client setup with caching, optimistic updates, pagination via fetchMore, WebSocket subscriptions, type auto-generation from GraphQL schema via graphql-codegen. | |
| Frontend Developer (React) | Implements advanced GraphQL patterns in React: fragments for field reuse, optimistic updates, cache normalization in Apollo Client. Configures GraphQL codegen for auto-generating TypeScript types and hooks, implements cursor-based pagination. | |
| Frontend Developer (Svelte) | Integrates GraphQL into SvelteKit through Houdini or type generation: mutations with optimistic UI, subscriptions for real-time. Configures client-level caching, creates fragments for reusable fields, types responses through codegen. | |
| Frontend Developer (Vue) | Integrates GraphQL into Vue application — type generation through graphql-codegen, fragment colocation with components, caching through normalized cache. Uses useQuery/useMutation composables for reactive data work. | |
| Fullstack Developer | Implements GraphQL API for fullstack applications: schema with types, resolvers with DataLoader for N+1, mutations with validation. Configures codegen for auto-generating TypeScript types and React hooks, ensuring type safety from schema to UI. | |
| Game QA Engineer | Tests game GraphQL: query complexity testing, mutation validation, subscription testing. Automates GraphQL API tests. | |
| Game Server Developer | Designs GraphQL schemas for game server APIs — player profiles, leaderboards, store. Implements resolvers with dataloaders to optimize N+1 queries, configures subscriptions. | |
| Infrastructure Engineer | Designs GraphQL API for internal infrastructure management platform: resource queries, deployment status. Implements resolvers with integration to cloud APIs and monitoring systems. | |
| iOS Developer | Integrates GraphQL into iOS applications via Apollo iOS: code generation setup, working with fragments and query variables. Implements caching through Apollo Cache with data normalization, handles GraphQL errors separately from network errors. Uses subscriptions for real-time WebSocket updates and optimistic updates. | |
| IoT Engineer | Develops GraphQL API for IoT platform: schemas for device state queries, telemetry update subscriptions, mutations for configuration management and device commands. | |
| Language Tooling Engineer | Designs GraphQL schemas for language tools with efficient resolvers. Implements queries for code navigation, symbol search, and project dependency visualization. | |
| LLM Engineer | Designs GraphQL for LLM: prompt template API, evaluation results queries, model metadata. | |
| ML Engineer | Designs GraphQL schemas for ML platform: models, experiments, datasets, predictions with typing. Implements resolvers with integration to model registry, feature store and experiment tracker. | |
| MLOps Engineer | Develops GraphQL APIs for the ML platform: schemas for querying experiments, training metrics, model versions. Implements subscriptions for real-time training job status updates. | |
| NLP Engineer | Designs GraphQL schemas for NLP platform with typed analysis results. Implements efficient resolvers for batch model queries and subscriptions for async tasks. | |
| Penetration Testing Engineer | Independently conducts security assessments of GraphQL APIs — exploits batching attacks, field suggestion enumeration, and nested query DoS vectors. Develops custom GraphQL fuzzing tools and introspection analysis scripts. Documents findings with proof-of-concept exploits and remediation guidance. | |
| Performance Testing Engineer | Conducts GraphQL API performance testing: creating realistic queries of varying complexity, testing query depth limits, measuring latency for nested queries and batch operations. | |
| Platform Engineer | Designs GraphQL API for the platform: resource queries, mutations for provisioning, subscriptions for status updates. Implements authorization directives. | |
| QA Automation Engineer | Independently designs comprehensive GraphQL API test suites covering schema validation, resolver logic, and subscription flows. Implements automated testing for query complexity limits, pagination, and error handling patterns. Writes schema-driven test generation and documents GraphQL testing best practices. | |
| QA Engineer (Manual) | Independently designs manual test strategies for GraphQL APIs covering query variations, mutation side effects, and subscription behavior. Applies exploratory testing techniques to discover edge cases in schema resolution and data consistency. Documents comprehensive GraphQL test matrices and regression scenarios. | |
| QA Security Engineer | Conducts GraphQL API security testing: depth limiting verification, query complexity analysis, field-level authorization testing. Develops test cases for GraphQL-specific vulnerabilities. | |
| React Native Developer | Designs GraphQL integration in React Native — normalized Apollo cache, optimistic updates, subscriptions via WebSocket. Applies fragments for reuse, cursor-based pagination. Generates types from GraphQL schema with graphql-codegen for TypeScript. | |
| Release Engineer | Develops GraphQL API for the release platform — deployment status queries and configuration management. Designs schemas for integration with monitoring and notification systems. | |
| Site Reliability Engineer (SRE) | Ensures GraphQL reliability: performance monitoring, query depth limiting, rate limiting. Configures SLIs for GraphQL (latency, error rate). | |
| Smart Contract Developer | Designs subgraphs: The Graph schema design, entity relationships, event handlers. Optimizes queries. | |
| Systems Programmer (C/C++) | Designs GraphQL for systems: system metrics query, resource management API, real-time monitoring. | |
| Technical Lead | Independently designs GraphQL schemas for team-owned services with proper type hierarchies and federation boundaries. Implements resolver patterns, dataloader batching, and connection-based pagination. Reviews team API designs and writes comprehensive schema documentation and testing guidelines. | |
| Technical Writer | Creates comprehensive GraphQL API documentation: schema reference, query examples, mutation guides, error handling. Uses GraphQL introspection for auto-generating reference docs. Documents API usage best practices. | |
| Telecom Developer | Designs GraphQL schemas for telecom BSS: subscriber management, tariffs, services, and billing. Implements resolvers with legacy system integration through adapters for SOAP and CORBA interfaces. | |
| Unity Developer | Integrates GraphQL in Unity: efficient data queries, subscriptions for real-time updates, type-safe clients. | |
| Unreal Engine Developer | Integrates GraphQL: efficient data queries, subscriptions for real-time, type-safe clients. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| 1C Developer | Develops scalable GraphQL APIs for integrating 1C with microservice architecture. Optimizes 1C database queries, implements batching and caching for high performance. | |
| AI Product Engineer | Pflicht | Designs GraphQL API architecture for AI product platforms spanning model serving, experiment tracking, and feature management. Defines schema evolution strategy supporting multiple model versions and A/B experiment configurations. Optimizes resolver performance for large-scale prediction result aggregation and real-time model monitoring queries. |
| Analytics Engineer | Architects a GraphQL semantic layer for the analytics platform with caching, rate limiting, and field-level authorization. Implements subscriptions for real-time analytics and integrates GraphQL with BI tools for self-service. | |
| Android Developer | Pflicht | Designs Android application GraphQL integration: caching strategy (cache-first, network-first, cache-and-network), subscription configuration via WebSocket for real-time updates, query complexity optimization. Implements persisted queries to reduce traffic, configures Apollo codegen in CI, profiles and optimizes Apollo cache for large data graphs. |
| Application Security Engineer | Designs secure GraphQL architecture: per-field authorization, complexity-based rate limiting, batching attack protection. Develops security rules for automated testing of GraphQL endpoints. | |
| Backend Developer (C#/.NET) | Pflicht | Designs GraphQL architecture: Schema Stitching/Federation for microservices, subscriptions via WebSocket, persisted queries. Optimizes execution engine and complexity analysis. |
| Backend Developer (Elixir) | Pflicht | Designs scalable GraphQL APIs on Absinthe with subscriptions through Phoenix PubSub and WebSocket. Implements persisted queries, query complexity analysis and depth limiting for DoS protection. Implements schema federation and Phoenix LiveView integration through push updates. |
| Backend Developer (Go) | Designs GraphQL architecture: federation with gqlgen, schema composition, zero-allocation resolvers. | |
| Backend Developer (Java/Kotlin) | Pflicht | Designs GraphQL architecture: federation for microservices, subscriptions via WebSocket, caching strategies. Optimizes query complexity and depth limiting. Integrates with Spring Security for field-level authorization. |
| Backend Developer (Node.js) | Pflicht | Designs GraphQL architecture: Federation for microservices, schema stitching, subscriptions via WebSocket. Implements authorization directives, query depth limiting. Monitors field usage. |
| Backend Developer (PHP) | Pflicht | Designs GraphQL architecture: schema stitching/federation for microservices, persisted queries for production, custom directives. Optimizes performance: caching, batching, query depth limiting. |
| Backend Developer (Python) | Designs GraphQL federation for microservices. Optimizes performance (caching, persisted queries). Creates custom directives. Chooses between Strawberry, Ariadne, Graphene for Python. | |
| Backend Developer (Rust) | Designs GraphQL architecture: federation with async-graphql, schema composition, zero-cost abstractions for resolvers. Benchmarks vs REST. | |
| Backend Developer (Scala) | Designs GraphQL architecture: federation with Caliban, schema composition, performance optimization. Defines GraphQL vs REST by use cases. | |
| Blockchain Developer | Pflicht | Designs API architecture with GraphQL Design for production systems. Defines versioning, error handling, pagination standards. Optimizes performance. |
| Cloud Engineer | Designs GraphQL architecture in cloud: AppSync federation, caching strategies, offline support. Compares GraphQL vs REST for various cloud use cases. | |
| Computer Vision Engineer | Designs scalable GraphQL APIs for the CV platform with federation and custom scalars for images. Optimizes queries for batch inference and model management. | |
| Data Analyst | Designs scalable GraphQL APIs for analytical platforms using federation and subscriptions. Solves N+1 query problems and optimizes performance of complex analytical queries. | |
| Data Engineer | Designs GraphQL data API: federated data access, real-time data subscriptions, unified data query layer. | |
| Data Scientist | Designs ML data API: unified feature access, model registry GraphQL, real-time subscriptions. | |
| Desktop Developer (.NET WPF/WinUI/MAUI) | Designs GraphQL API for .NET server components through HotChocolate optimized for desktop clients — DataLoader, caching. Implements subscriptions through WebSocket for real-time updates in desktop applications. | |
| Desktop Developer (Electron/Tauri) | Designs GraphQL architecture for the Electron platform: schema stitching, subscriptions for real-time updates, batch operations. Optimizes queries considering client network connection limitations. | |
| Desktop Developer (Qt/C++) | Designs GraphQL API for Qt ecosystem server components optimized for desktop clients — batching, caching and pagination. Implements subscriptions for real-time updates and offline-first strategy for desktop applications. | |
| DevOps Engineer | Designs DevOps for GraphQL infrastructure: federation deployment, schema CI/CD, performance tuning. Defines operational requirements. | |
| DevSecOps Engineer | Develops GraphQL API security standards: persisted queries, operation allowlisting and cost analysis. Integrates GraphQL security testing into CI/CD pipeline with automated schema validation. | |
| Embedded Developer | Develops scalable GraphQL APIs with subscriptions for real-time embedded device state updates. Implements federation for unifying IoT platform microservices into a single data graph. | |
| Engineering Manager | Defines GraphQL usage strategy across multiple teams, including federation and schema governance. Coordinates cross-team design of a unified API graph. | |
| Flutter Developer | Pflicht | Designs GraphQL API architecture optimized for cross-platform Flutter applications with offline-first requirements. Defines schema federation strategy for microservice backends consumed by mobile and web clients. Optimizes query patterns for bandwidth-constrained mobile networks and implements efficient cache invalidation strategies. |
| Frontend Developer (Angular) | Pflicht | Designs GraphQL integration in Angular: normalized Apollo cache, cache-policy strategies (cache-first, network-only), fragments for reuse, request batching, query performance monitoring. |
| Frontend Developer (React) | Pflicht | Designs GraphQL architecture for React applications: caching and invalidation strategy, persisted queries for security and performance, React Server Components integration. Optimizes query complexity, implements real-time subscriptions through WebSocket. |
| Frontend Developer (Svelte) | Pflicht | Designs GraphQL architecture for SvelteKit applications: schema-first approach, resolver composition, DataLoader for N+1. Creates GraphQL BFF on SvelteKit server routes, implements persisted queries for security, optimizes queries through complexity analysis. |
| Frontend Developer (Vue) | Pflicht | Designs GraphQL architecture for Vue application — schema design, optimistic updates, subscriptions for real-time data. Configures persisted queries, cache policies and pagination patterns for large-scale applications. |
| Fullstack Developer | Pflicht | Designs GraphQL architecture for fullstack applications: federation for microservices, subscriptions for real-time, persisted queries for performance. Optimizes resolvers with batching and caching, configures protection against complex queries and depth limiting. |
| Game QA Engineer | Designs GraphQL testing: comprehensive schema testing, performance benchmarks, security validation. | |
| Game Server Developer | Develops scalable GraphQL architecture for the game platform — federation between services, query-level caching, complexity optimization. Ensures schema security. | |
| Infrastructure Engineer | Develops scalable GraphQL API for IDP with real-time infrastructure change subscriptions. Implements caching and batching for optimizing queries to multiple cloud API providers. | |
| iOS Developer | Pflicht | Architects GraphQL integration for iOS applications: caching strategy with cache policies, watched query lifecycle management. Optimizes performance: query batching, persisted queries for traffic reduction, and automatic query deduplication. Configures custom scalar types and interceptor chains for Apollo. |
| IoT Engineer | Designs advanced GraphQL solutions for IoT: federated schemas for different device types, N+1 query optimization for fleet data, DataLoader for batching. | |
| Language Tooling Engineer | Develops scalable GraphQL APIs for the language tooling platform. Designs federated schemas for integrating multiple analyzers and optimizes N+1 queries. | |
| LLM Engineer | Designs LLM API architecture: unified prompt management, real-time evaluation, caching. | |
| ML Engineer | Develops scalable GraphQL API for ML platform with subscriptions for training job and model deployment status. Introduces DataLoader for optimizing batch queries to model metadata and metrics stores. | |
| MLOps Engineer | Architects GraphQL infrastructure for the ML platform: federated schemas for experiment tracking, model registry, and feature store. Optimizes queries for dashboards with large metric volumes. | |
| NLP Engineer | Develops scalable GraphQL APIs for NLP platform with federation. Designs schemas for multi-model integration, optimizes dataloader for batch inference. | |
| Penetration Testing Engineer | Pflicht | Designs comprehensive GraphQL security assessment methodologies for production APIs. Architects advanced attack scenarios including authorization bypass through nested resolvers, information disclosure via error messages, and resource exhaustion through query complexity manipulation. Defines remediation standards and security review processes for GraphQL schema changes. |
| Performance Testing Engineer | Designs comprehensive GraphQL performance tests: resolver chain benchmarking, testing N+1 problems under load, measuring DataLoader overhead, stress-testing subscriptions. | |
| Platform Engineer | Designs GraphQL platform API: federated schema for multi-component platform, real-time subscriptions, caching strategy. Defines GraphQL vs REST trade-offs. | |
| QA Automation Engineer | Pflicht | Designs GraphQL API testing architecture for complex federated schema environments. Implements contract testing between GraphQL gateway and subgraph services. Defines schema change impact analysis automation and backward compatibility verification. Optimizes test execution for large schemas with thousands of types and resolvers. |
| QA Engineer (Manual) | Pflicht | Designs comprehensive GraphQL API testing strategy combining automated schema validation with targeted exploratory testing. Architects test approaches for complex mutation workflows, subscription reliability, and federation boundary behavior. Defines quality gates for schema evolution and mentors team on GraphQL-specific testing patterns. |
| QA Security Engineer | Designs comprehensive GraphQL security testing strategy: automated schema fuzzing, batching attack testing, complexity-based rate limiting verification. Creates specialized testing tools. | |
| React Native Developer | Pflicht | Architects the GraphQL layer for large-scale React Native applications. Designs cache strategy — merge policies, field policies, cache eviction. Optimizes queries for mobile networks — persisted queries, automatic batching. Implements offline-first GraphQL with cache persistence. |
| Release Engineer | Designs scalable GraphQL APIs for a comprehensive release platform. Implements federated schemas to unify data from various CI/CD and monitoring systems. | |
| Site Reliability Engineer (SRE) | Designs reliability for GraphQL infrastructure: caching strategy, CDN integration, federation monitoring. Defines performance budgets. | |
| Smart Contract Developer | Designs GraphQL architecture: multi-chain subgraphs, custom indexers, performance optimization. | |
| Solutions Architect | Pflicht | Designs enterprise-wide GraphQL API architecture with federation, gateway patterns, and cross-domain schema composition. Defines versioning strategy that supports backward compatibility across multiple consumer teams. Optimizes performance through persisted queries, caching layers, and intelligent query planning for complex business domains. |
| Systems Programmer (C/C++) | Designs system API: efficient query execution, streaming data, custom resolvers. | |
| Technical Lead | Pflicht | Designs GraphQL API architecture for production microservice ecosystems with schema federation and domain-driven boundaries. Defines error handling standards, pagination patterns, and query cost analysis policies. Optimizes resolver performance through dataloader strategies and query plan analysis. Mentors team on schema design best practices. |
| Technical Writer | Documents complex GraphQL patterns: federation, schema stitching, custom directives, real-time subscriptions. Creates interactive GraphQL explorer for the developer portal. Develops migration guides during schema evolution. | |
| Telecom Developer | Develops scalable GraphQL API for the telecom platform with federation for unifying BSS/OSS domains. Implements subscriptions for real-time service status notifications and network events. | |
| Unity Developer | Designs GraphQL architecture: game data API, caching strategy, offline support. | |
| Unreal Engine Developer | Designs GraphQL architecture: game data API, caching, offline support. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| 1C Developer | Defines GraphQL API standards for integrating 1C with all organizational systems. Designs a unified data model for exposing 1C business objects through modern APIs. | |
| AI Product Engineer | Pflicht | Defines GraphQL API strategy for AI product platforms spanning model serving and MLOps tooling. Establishes schema design standards for ML data types, experiment metadata, and inference result structures. Conducts API design reviews ensuring consistency across AI product teams and coordinates federated schema governance. |
| Analytics Engineer | Defines GraphQL API standards for the analytics platform, including naming conventions and metric/dimension patterns. Coordinates development of a unified data API for providing analytical data to all organizational consumers. | |
| Android Developer | Pflicht | Defines GraphQL strategy for the Android team: query and mutation writing standards, fragment and variable usage rules, Apollo module architecture in multi-module applications. Coordinates schema evolution with the backend team, implements schema validation in CI, trains the team on advanced patterns — deferred queries, @defer, custom fetch policies. |
| Application Security Engineer | Defines security standards for the organization's GraphQL APIs: mandatory protective mechanisms, audit logging, schema validation. Coordinates implementation of security best practices in GraphQL development. | |
| Backend Developer (C#/.NET) | Pflicht | Defines GraphQL strategy: schema conventions, federation architecture, performance budgets. Implements schema registry and breaking change detection. |
| Backend Developer (Elixir) | Pflicht | Defines GraphQL strategy for the Elixir platform. Designs federated architecture with Absinthe Federation, defines naming standards, error handling and authorization through middleware. Implements schema stitching between microservices and monitoring through :telemetry. |
| Backend Developer (Go) | Defines GraphQL standards: gqlgen conventions, schema governance, performance requirements. | |
| Backend Developer (Java/Kotlin) | Pflicht | Defines product GraphQL strategy: schema conventions, federation architecture, performance budgets. Implements schema registry and breaking change detection in CI. |
| Backend Developer (Node.js) | Pflicht | Defines GraphQL standards: schema design guidelines, federation strategy, deprecation policy. Implements schema review process and automated breaking change detection. |
| Backend Developer (PHP) | Pflicht | Defines GraphQL standards for the team: schema conventions, review process, monitoring. Makes decisions about GraphQL vs REST vs gRPC applicability for different scenarios. |
| Backend Developer (Python) | Designs GraphQL strategy for the organization. Defines graph ownership model. Implements schema registry. Trains the team. | |
| Backend Developer (Rust) | Defines GraphQL standards: library selection (async-graphql vs Juniper), schema governance, performance requirements. Implements schema validation. | |
| Backend Developer (Scala) | Defines GraphQL standards: Caliban vs Sangria selection, schema governance, deprecation policy. Implements automated breaking change detection. | |
| Blockchain Developer | Pflicht | Defines API strategy at product level. Establishes design standards. Conducts API design reviews. Coordinates cross-team API interaction. |
| Cloud Engineer | Defines GraphQL standards for cloud services: schema design guidelines, security policies, performance budgets. Introduces schema review and versioning. | |
| Computer Vision Engineer | Defines GraphQL API standards for the CV team, creates guidelines for designing ML service schemas. Coordinates API contracts between CV and frontend teams. | |
| Data Analyst | Defines GraphQL API design standards for the analytics team, creates guidelines on naming and schema structure. Organizes schema review and versioning processes. | |
| Data Engineer | Defines GraphQL standards for data: schema design, access patterns, performance requirements. | |
| Data Scientist | Defines GraphQL standards for ML: schema design, access patterns, performance. | |
| Desktop Developer (.NET WPF/WinUI/MAUI) | Defines GraphQL interaction standards for .NET desktop platform, including schema, error patterns and versioning. Coordinates development of unified GraphQL layer for standardizing data access from desktop applications. | |
| Desktop Developer (Electron/Tauri) | Defines GraphQL usage standards for the organization's Electron product line. Coordinates schema governance and establishes best practices for desktop GraphQL clients. | |
| Desktop Developer (Qt/C++) | Defines GraphQL interaction standards for the Qt platform, including naming schema, error patterns and version policy. Coordinates development of a unified GraphQL layer for standardizing data access from desktop applications. | |
| DevOps Engineer | Defines DevOps standards for GraphQL: deployment guidelines, monitoring requirements, performance budgets. Coordinates with development. | |
| DevSecOps Engineer | Defines GraphQL security architecture standards for the organization, including federation security model. Designs monitoring and audit logging for GraphQL API with anomalous query pattern detection. | |
| Embedded Developer | Defines GraphQL architectural standards for the IoT ecosystem, including authorization schemes and per-device rate limiting. Designs schema evolution strategy considering backward compatibility for client applications. | |
| Engineering Manager | Shapes GraphQL API policy for the department, manages schema registry and versioning. Coordinates REST to GraphQL migration and ensures backward compatibility. | |
| Flutter Developer | Pflicht | Defines GraphQL API strategy for Flutter application portfolios across mobile, web, and embedded platforms. Establishes schema design standards optimized for client-side state management and offline capabilities. Conducts API design reviews from a mobile consumer perspective and coordinates cross-team schema federation. |
| Frontend Developer (Angular) | Pflicht | Manages GraphQL strategy for the Angular project: query and mutation writing standards, code-generation pipeline, field usage monitoring, schema evolution process, team GraphQL pattern training. |
| Frontend Developer (React) | Pflicht | Defines GraphQL strategy for the team's React projects: query writing conventions, fragment structure, code generation approach. Coordinates with backend team: schema design, breaking changes management, GraphQL operation performance monitoring. |
| Frontend Developer (Svelte) | Pflicht | Defines GraphQL standards in the Svelte team: schema conventions, query patterns, caching strategy, monitoring. Coordinates schema evolution with backend teams, implements GraphQL playground and documentation, trains the team on efficient patterns with Houdini. |
| Frontend Developer (Vue) | Pflicht | Defines GraphQL strategy for Vue projects — schema governance, performance monitoring, security (query complexity, depth limiting). Introduces GraphQL standards — codegen pipeline, testing patterns, error handling. |
| Fullstack Developer | Pflicht | Defines GraphQL strategy for the fullstack platform: schema-first vs code-first, service federation, governance process. Designs graph gateway architecture, naming standards and trains the team on effective GraphQL usage patterns. |
| Game QA Engineer | Defines GraphQL testing standards: schema validation requirements, performance testing, security policies. | |
| Game Server Developer | Defines GraphQL usage strategy for the server stack. Standardizes schema design approaches, establishes naming conventions, depth limiting, and performance budgets for queries. | |
| Infrastructure Engineer | Defines GraphQL API architecture for organizational platform services with federation and schema governance. Designs unified API for managing multi-cloud infrastructure through a single GraphQL endpoint. | |
| iOS Developer | Pflicht | Defines GraphQL layer architecture for the iOS team: modular schema structure, fragment reuse strategy, and code generation pipeline. Implements query performance monitoring, manages complexity through query cost analysis. Designs patterns for offline support and optimistic updates in complex business scenarios. |
| IoT Engineer | Defines GraphQL strategy for IoT platform: schema standards, deprecation policies, query complexity monitoring. Designs gateway for aggregating data from multiple services. | |
| Language Tooling Engineer | Defines GraphQL API standards for all organizational language tools. Designs a unified codebase graph model with subscription support and incremental updates. | |
| LLM Engineer | Defines GraphQL standards: schema design, access patterns. | |
| ML Engineer | Defines GraphQL API architecture for organizational ML platform with federation for unifying data from different subsystems. Designs schema governance considering ML platform evolution and backward compatibility. | |
| MLOps Engineer | Defines the GraphQL strategy for ML infrastructure: schema standards for ML metadata, query complexity policies, integration with various ML backends through a unified API layer. | |
| NLP Engineer | Defines GraphQL API standards for all organizational ML services. Designs unified graph data model for the ML platform with model versioning and experiment support. | |
| Penetration Testing Engineer | Pflicht | Defines GraphQL security assessment strategy across the product portfolio. Establishes standards for GraphQL threat modeling, introspection policy enforcement, and query depth governance. Conducts cross-team API security reviews and coordinates GraphQL vulnerability disclosure processes. |
| Performance Testing Engineer | Defines GraphQL performance testing strategy: standard benchmarks, query complexity criteria, optimization recommendations. Develops methodology for the development team. | |
| Platform Engineer | Defines GraphQL platform standards: schema design, authorization patterns, performance requirements. Implements schema governance. | |
| QA Automation Engineer | Pflicht | Defines GraphQL API testing strategy across the product ecosystem. Establishes quality standards for schema evolution, federation testing, and cross-service contract verification. Conducts API design reviews from a testability perspective and coordinates cross-team GraphQL testing infrastructure. |
| QA Engineer (Manual) | Pflicht | Defines GraphQL testing strategy at the product level. Establishes standards for API testing of GraphQL endpoints. Conducts API test design reviews. |
| QA Security Engineer | Defines GraphQL security testing standards for the organization. Implements automated GraphQL security testing in CI/CD and trains the QA team on GraphQL API testing specifics. | |
| React Native Developer | Pflicht | Defines the GraphQL strategy for the team's mobile projects. Establishes guidelines — query complexity, fragment co-location, caching strategies. Coordinates schema design between mobile and backend teams. Reviews GraphQL architecture for N+1, overfetching, underfetching. |
| Release Engineer | Establishes GraphQL API design standards for infrastructure services. Trains teams on creating efficient schemas and optimizing query performance for release data. | |
| Site Reliability Engineer (SRE) | Defines reliability standards for GraphQL: SLO requirements, monitoring coverage, capacity planning. Coordinates with development teams. | |
| Smart Contract Developer | Defines GraphQL standards: subgraph design guidelines, schema governance. | |
| Solutions Architect | Pflicht | Defines enterprise GraphQL API strategy spanning business domains and organizational boundaries. Establishes federated schema governance, API gateway standards, and cross-team schema composition policies. Conducts architectural reviews of GraphQL implementations and coordinates API platform evolution across engineering teams. |
| Systems Programmer (C/C++) | Defines API standards: system API design, performance requirements. | |
| Technical Lead | Pflicht | Defines GraphQL API strategy across product domains. Establishes schema design standards, federation governance, and API lifecycle management processes. Conducts cross-team schema design reviews and coordinates unified API experience across consumer applications. |
| Technical Writer | Defines GraphQL API documentation standards for the organization. Creates templates and guidelines. Ensures documentation consistency when multiple teams work on federated GraphQL schemas. | |
| Telecom Developer | Defines GraphQL architecture as a unified API for the telecom ecosystem, combining legacy and cloud-native systems. Designs migration strategy from SOAP/REST to GraphQL with backward compatibility for partners. | |
| Unity Developer | Defines GraphQL standards: schema design, performance requirements, security. | |
| Unreal Engine Developer | Defines GraphQL standards: schema design, performance, security. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| 1C Developer | Shapes 1C API integration strategy at the organizational level. Defines GraphQL interface standards ensuring seamless integration of 1C systems into the company's IT landscape. | |
| AI Product Engineer | Pflicht | Defines organizational GraphQL API strategy for enterprise AI platforms spanning model serving, MLOps, and data science tooling. Designs platform-level schema architecture for unified access to ML capabilities across business units. Establishes enterprise API governance for AI services balancing standardization with domain-specific model serving requirements. |
| Analytics Engineer | Shapes the corporate analytics API strategy based on GraphQL with federation and semantic layer. Defines the unified access layer architecture for scaling self-service analytics at the enterprise level. | |
| Android Developer | Pflicht | Shapes GraphQL strategy at the Android platform level: schema federation architecture for mobile clients, type and operation generation standards, schema version migration protocols. Defines REST-to-GraphQL transition strategy, designs solutions for complex subscriptions and real-time scenarios, manages GraphQL performance at scale across multiple applications. |
| Application Security Engineer | Shapes GraphQL API security strategy at organizational scale. Defines architectural principles for GraphQL layer protection considering complex federation and gateway pattern scenarios. | |
| Backend Developer (C#/.NET) | Pflicht | Shapes organizational GraphQL platform: supergraph, schema governance, query analytics. Determines when GraphQL vs REST vs gRPC. |
| Backend Developer (Elixir) | Pflicht | Develops platform GraphQL architecture for the entire organization on Absinthe. Designs Graph Federation with automatic schema composition, defines API evolution policy and breaking changes. Implements distributed query cache through ETS and Redis. |
| Backend Developer (Go) | Shapes GraphQL strategy: Go performance advantages, federation architecture, schema evolution governance. | |
| Backend Developer (Java/Kotlin) | Pflicht | Shapes organizational GraphQL platform: supergraph from microservices, schema governance, query analytics. Determines when GraphQL is optimal vs REST vs gRPC. |
| Backend Developer (Node.js) | Pflicht | Designs GraphQL strategy: unified graph (Apollo Federation), schema governance, GraphQL vs REST trade-offs per use case. Determines when GraphQL is justified on the platform. |
| Backend Developer (PHP) | Pflicht | Designs platform API architecture with GraphQL: federated gateway, schema registry, breaking change detection. Defines API evolution strategy for external and internal clients. |
| Backend Developer (Python) | Defines API strategy: REST + GraphQL + gRPC. Designs unified graph for the organization. Evaluates GraphQL vs alternatives at scale. | |
| Backend Developer (Rust) | Shapes GraphQL strategy: Rust performance advantages for GraphQL, federation architecture, schema evolution governance. | |
| Backend Developer (Scala) | Shapes GraphQL strategy: unified graph architecture, cross-service federation, schema evolution governance. Defines API strategy. | |
| Blockchain Developer | Pflicht | Defines organizational GraphQL API strategy for blockchain data infrastructure spanning multiple chains and indexing protocols. Designs platform-level subgraph architecture for unified access to on-chain analytics and DeFi protocol data. Establishes enterprise governance for blockchain data APIs balancing decentralization principles with data consistency and query performance. |
| Cloud Engineer | Shapes cloud platform GraphQL strategy: unified API layer, multi-source federation, GraphQL gateway architecture. Defines when GraphQL vs REST. | |
| Computer Vision Engineer | Shapes GraphQL usage strategy for the organization's ML platform. Defines approaches to schema federation between CV, NLP, and other ML services. | |
| Data Analyst | Shapes GraphQL usage strategy for the organization's analytical platform. Defines approaches to schema federation, data management, and integration with existing REST services. | |
| Data Engineer | Shapes data access strategy: unified query layer, data API governance, self-service data access architecture. | |
| Data Scientist | Shapes ML API strategy: unified ML platform API, governance. | |
| Desktop Developer (.NET WPF/WinUI/MAUI) | Shapes corporate GraphQL architecture strategy for .NET desktop application ecosystem with federated graph. Defines API gateway architecture for scaling desktop client interaction with server infrastructure. | |
| Desktop Developer (Electron/Tauri) | Shapes GraphQL API strategy for the Electron desktop product ecosystem. Defines architectural principles for scaling GraphQL infrastructure for millions of desktop clients. | |
| Desktop Developer (Qt/C++) | Shapes corporate GraphQL architecture strategy for the desktop application ecosystem with a federated data graph. Defines API gateway architecture for scaling Qt client interaction with server infrastructure. | |
| DevOps Engineer | Shapes GraphQL operations strategy: platform-wide GraphQL infrastructure, deployment automation, operational governance. | |
| DevSecOps Engineer | Shapes organizational GraphQL API security strategy considering supply chain and third-party integrations. Defines roadmap for GraphQL protection against emerging threats and WAF solution integration. | |
| Embedded Developer | Shapes API strategy for the IoT ecosystem: GraphQL federation for device management, protocol selection guidelines (GraphQL vs REST vs MQTT), API evolution governance. | |
| Engineering Manager | Defines GraphQL usage strategy at the organizational level, shapes architectural principles for the unified API layer. Coordinates schema federation between departments. | |
| Flutter Developer | Pflicht | Defines organizational GraphQL API strategy for cross-platform Flutter ecosystems. Designs platform-level GraphQL gateway architecture serving mobile, web, and embedded clients. Establishes enterprise API governance standards balancing developer experience with performance and security requirements across product lines. |
| Frontend Developer (Angular) | Pflicht | Defines GraphQL strategy at the Angular platform level: federated GraphQL architecture for micro-frontends, edge caching via Persisted Queries, Angular Universal integration for server-side data fetching. |
| Frontend Developer (React) | Pflicht | Shapes GraphQL strategy for the React application ecosystem: GraphQL Federation for microservices, schema governance, REST migration strategy. Defines architectural decisions: Relay vs Apollo, server-driven UI, edge caching for GraphQL at the organization level. |
| Frontend Developer (Svelte) | Pflicht | Shapes GraphQL strategy at the organizational level, defines federated architecture with a SvelteKit BFF layer. Researches defer/stream directives and incremental delivery for SvelteKit SSR optimization, influences GraphQL integration development in the Svelte ecosystem. |
| Frontend Developer (Vue) | Pflicht | Shapes GraphQL strategy for company's Vue ecosystem — federated graph, schema registry, REST migration. Researches and introduces new approaches — GraphQL over HTTP, defer/stream directives, Relay-style pagination. |
| Fullstack Developer | Pflicht | Shapes organizational GraphQL strategy: federated supergraph for fullstack ecosystem, schema monitoring, breaking change detection. Defines GraphQL's role in API strategy vs REST vs tRPC and creates platform solutions for scaling. |
| Game QA Engineer | Shapes GraphQL QA strategy: platform-wide GraphQL testing, schema governance, quality assurance. | |
| Game Server Developer | Shapes API strategy for the studio platform considering GraphQL and REST. Designs a unified graph for the entire game services ecosystem and defines inter-service communication standards. | |
| Infrastructure Engineer | Shapes API-first strategy for organizational infrastructure platform with GraphQL as primary interface. Defines platform API development roadmap considering scaling and new cloud services. | |
| iOS Developer | Pflicht | Develops GraphQL usage strategy for the iOS platform: choosing between REST and GraphQL for different domains, transition architecture, and standards. Implements schema-driven development with automatic client code generation, contract testing between iOS and backend. Defines schema evolution strategy with backward compatibility for mobile clients. |
| IoT Engineer | Shapes API layer strategy for IoT ecosystem: combining GraphQL/REST/gRPC for different tiers (devices/edge/cloud), standards for integrator and partner ecosystem. | |
| Language Tooling Engineer | Shapes API strategy for the language tools ecosystem. Defines graph interface standards for the development tools industry and promotes innovative approaches. | |
| LLM Engineer | Shapes LLM API strategy: platform API architecture, governance. | |
| ML Engineer | Shapes unified API strategy for organizational ML ecosystem with GraphQL as primary interface for UI and SDK. Defines API roadmap considering GenAI, vector store and new ML paradigm integration. | |
| MLOps Engineer | Shapes the API layer strategy for the organization's AI platform: unified GraphQL gateway for all ML services, standards for integration with external ML data consumers. | |
| NLP Engineer | Shapes API strategy for the organizational ML platform. Defines graph interface standards for the AI services industry and promotes unified approaches to ML APIs. | |
| Penetration Testing Engineer | Pflicht | Defines organizational GraphQL security strategy spanning all API surfaces. Designs enterprise-grade GraphQL security frameworks including automated vulnerability detection, query cost enforcement, and zero-trust authorization patterns. Establishes GraphQL security governance standards and certification processes for production deployments. |
| Performance Testing Engineer | Shapes GraphQL performance testing strategy for the organization: query complexity standards, load testing methodology for federation, best practices for production GraphQL. | |
| Platform Engineer | Shapes platform GraphQL strategy: unified platform graph, federation architecture, developer experience. Defines API strategy. | |
| QA Automation Engineer | Pflicht | Defines organizational GraphQL API quality strategy spanning hundreds of services and schema domains. Designs platform-level testing infrastructure for automated schema compatibility verification and federated graph validation. Establishes enterprise GraphQL testing governance and self-service testing frameworks for engineering teams. |
| QA Engineer (Manual) | Pflicht | Defines organizational GraphQL API quality strategy bridging automated schema testing with expert manual validation. Designs platform-level quality frameworks for evaluating API usability, documentation completeness, and consumer developer experience. Establishes enterprise GraphQL testing governance and cross-team quality coordination processes. |
| QA Security Engineer | Shapes GraphQL API security testing strategy at organizational scale. Defines approaches to automated security verification for GraphQL federation and gateway architectures. | |
| React Native Developer | Pflicht | Shapes the enterprise GraphQL strategy for the organization's mobile applications. Defines architecture — schema stitching, federation for mobile clients. Designs API evolution strategy accounting for mobile app versions in production and App Store review cycles. |
| Release Engineer | Defines GraphQL layer architecture for the entire organizational release tool ecosystem. Creates a unified API gateway for deployment management and monitoring through federated GraphQL. | |
| Site Reliability Engineer (SRE) | Shapes GraphQL reliability strategy: platform-wide monitoring, performance governance, capacity management. Defines operational standards. | |
| Smart Contract Developer | Shapes data access strategy: blockchain data API platform, indexer governance. | |
| Solutions Architect | Pflicht | Defines organizational GraphQL API strategy as a core enterprise integration platform. Designs platform-level federated graph architecture supporting hundreds of services and multiple business domains. Establishes enterprise API governance balancing innovation speed with schema consistency, security, and operational excellence. |
| Systems Programmer (C/C++) | Shapes API strategy: system management API architecture, governance. | |
| Technical Lead | Pflicht | Defines organizational GraphQL API strategy spanning all product domains and engineering teams. Designs platform-level schema registry and federated gateway architecture. Establishes enterprise API governance standards, developer tooling for schema-first development, and organizational API design review processes. |
| Technical Writer | Shapes GraphQL ecosystem documentation strategy at the company level. Defines approaches to developer experience: interactive docs, type-safe SDK generation, real-time schema documentation. | |
| Telecom Developer | Shapes API transformation strategy for the telecom organization with GraphQL as the primary digital services interface. Defines integration roadmap with TM Forum Open API and 5G Service-Based Architecture via GraphQL. | |
| Unity Developer | Shapes organizational API strategy evaluating GraphQL versus REST for game service backends, defining governance for real-time game data subscriptions and player-facing service schemas. Establishes platform standards for game API architecture balancing latency requirements with schema flexibility across game titles. | |
| Unreal Engine Developer | Shapes organizational API strategy evaluating GraphQL versus REST for Unreal Engine multiplayer backends, defining governance for live-service game data APIs and matchmaking schemas. Establishes platform standards for game API architecture optimized for high-throughput game state synchronization across titles. |