Dominio
API & Integration
Perfil de habilidad
Proto3, unary/streaming calls, interceptors, reflection, code generation
Roles
21
donde aparece esta habilidad
Niveles
5
ruta de crecimiento estructurada
Requisitos obligatorios
39
los otros 63 opcionales
API & Integration
gRPC
17/3/2026
Selecciona tu nivel actual y compara las expectativas.
La tabla muestra cómo crece la profundidad desde Junior hasta Principal.
| Rol | Obligatorio | Descripción |
|---|---|---|
| Backend Developer (C#/.NET) | Understands gRPC for C#: Grpc.Net, proto files, code generation. Implements basic gRPC services. | |
| Backend Developer (Elixir) | Understands gRPC/Protobuf for Elixir: proto files for API description, basic client through grpc_elixir. Generates Elixir modules from .proto files. | |
| Backend Developer (Go) | Obligatorio | Uses generated protobuf clients and servers in Go projects. Understands basic .proto file structure, protobuf data types, code generation via protoc-gen-go and protoc-gen-go-grpc. Implements simple unary RPC methods. |
| Backend Developer (Java/Kotlin) | Understands gRPC for Java: proto files, grpc-java code generation. Implements basic gRPC services. | |
| Backend Developer (Node.js) | Understands gRPC for Node.js: proto files, @grpc/grpc-js for client/server. Generates TypeScript types from .proto files. | |
| Backend Developer (PHP) | Familiar with gRPC protocol and Protocol Buffers format as an alternative to REST/JSON for inter-service communication. Understands binary serialization benefits, reads .proto files, and uses generated PHP client to call existing gRPC services from Laravel/Symfony applications. | |
| Backend Developer (Python) | Understands gRPC for Python: proto files, grpcio code generation. Implements basic gRPC services. | |
| Backend Developer (Rust) | Obligatorio | Implements basic gRPC services in Rust through tonic, defining .proto files and using Rust code auto-generation through prost. Understands Protobuf message structure, unary RPC calls and proto type mapping to Rust structs. |
| Backend Developer (Scala) | Obligatorio | Uses existing gRPC services from Scala code through ScalaPB: calls unary RPC methods, understands .proto file structure. Can generate Scala classes from Protobuf definitions through sbt plugin, works with basic message types and enums. |
| Computer Vision Engineer | Understands basics of gRPC & Protocol Buffers for computer vision service communication. Reads proto definitions for image processing request/response schemas. Follows team conventions for defining vision model inference service contracts and streaming image data. | |
| Data Engineer | Understands Protobuf schemas for data serialization. Uses gRPC for high-performance data transfer between services. Works with .proto files for defining data contracts. | |
| Fullstack Developer | Understands gRPC for fullstack: gRPC-Web for browser clients, Protobuf serialization. Generates TypeScript types. | |
| Game Server Developer | Understands basics of gRPC & Protocol Buffers for game server inter-service communication. Reads proto definitions for matchmaking, player state, and game session message schemas. Follows team conventions for defining game service contracts with efficient binary serialization. | |
| LLM Engineer | Understands basics of gRPC & Protocol Buffers for LLM inference service communication. Reads proto definitions for model serving request/response schemas and streaming token generation. Follows team conventions for defining inference endpoint contracts and model metadata messages. | |
| ML Engineer | Understands basics of gRPC & Protocol Buffers for ML pipeline service communication. Reads proto definitions for training job orchestration and model serving schemas. Follows team conventions for defining feature store access contracts and experiment tracking service messages. | |
| MLOps Engineer | Understands basics of gRPC & Protocol Buffers for MLOps platform service communication. Reads proto definitions for pipeline orchestration, model registry, and deployment service schemas. Follows team conventions for defining ML infrastructure service contracts. | |
| NLP Engineer | Knows gRPC and Protocol Buffers basics: service definition, message types, client generation. Uses gRPC to call NLP services: sending text, receiving NER annotations. | |
| Technical Writer | Understands basics of gRPC & Protocol Buffers for writing accurate API documentation. Reads proto file definitions and service descriptions for documentation purposes. Follows team conventions for documenting gRPC service endpoints, message types, and streaming patterns. | |
| Telecom Developer | Understands basics of gRPC & Protocol Buffers for telecom network function communication. Reads proto definitions for signaling, configuration management, and telemetry schemas. Follows team conventions for defining network element service contracts with efficient binary encoding. |
| Rol | Obligatorio | Descripción |
|---|---|---|
| Backend Developer (C#/.NET) | Implements gRPC services: ASP.NET Core gRPC, streaming, interceptors. Configures health checks and deadlines. | |
| Backend Developer (Elixir) | Implements gRPC services in Elixir: server/client through grpc_elixir, streaming, interceptors. Defines proto schema for cross-service communication. | |
| Backend Developer (Go) | Obligatorio | Designs gRPC services in Go: defines .proto contracts with message validation, implements unary and server-streaming RPC. Configures grpc-gateway for REST proxy, applies interceptors for logging, authentication, and tracing via OpenTelemetry. |
| Backend Developer (Java/Kotlin) | Implements gRPC: Spring gRPC integration, streaming, interceptors. Configures health checks, deadlines, retry. | |
| Backend Developer (Node.js) | Implements gRPC services: grpc-js with NestJS, streaming, interceptors. Defines proto schema for inter-service communication. | |
| Backend Developer (PHP) | Develops gRPC services in PHP using grpc/grpc and roadrunner-server/grpc: defines .proto contracts, generates PHP code via protoc, implements server handlers. Configures gRPC clients for interacting with Go/Java services and handles errors through gRPC status codes. | |
| Backend Developer (Python) | Implements gRPC: grpcio with async support, streaming, interceptors. Defines proto schemas. | |
| Backend Developer (Rust) | Obligatorio | Develops gRPC services on tonic with server/client streaming, interceptors for authentication and request metadata. Configures tonic-build for code generation, implements error mapping through tonic::Status and connects reflection service for grpcurl. |
| Backend Developer (Scala) | Obligatorio | Implements gRPC services in Scala through ScalaPB and Akka gRPC: unary and server-streaming RPC, error handling through Status, deadline propagation. Designs Protobuf schemas with evolution in mind, uses oneof for polymorphism and configures interceptors for logging and authentication. |
| Computer Vision Engineer | Independently designs gRPC services for computer vision pipelines — streaming image data with bidirectional gRPC, efficient proto schemas for bounding box and segmentation results, and batched inference request patterns. Writes comprehensive proto documentation and integration tests for vision service contracts. | |
| Data Engineer | Designs Protobuf schemas for data pipelines: schema evolution with backward compatibility, nested messages for complex data. Uses gRPC streaming for real-time data transfer. | |
| Fullstack Developer | Implements gRPC in fullstack: gRPC-Web + Envoy proxy, streaming, type-safe API contracts. Compares with REST/GraphQL. | |
| Game Server Developer | Independently designs gRPC services for game server infrastructure — real-time game state synchronization with server streaming, efficient proto schemas for player actions and world updates, and low-latency RPC patterns for matchmaking. Writes comprehensive proto documentation and tests for game service interoperability. | |
| LLM Engineer | Independently designs gRPC services for LLM inference platforms — streaming token generation with server-side streaming, efficient proto schemas for prompt/completion messages with metadata, and load-balanced inference request routing. Writes comprehensive proto documentation and tests for model serving contracts. | |
| ML Engineer | Creates gRPC services for ML inference. Defines protobuf schemas for ML predictions. Uses gRPC for internal communication between ML services. Configures streaming for batch inference. | |
| MLOps Engineer | Develops gRPC services for ML inference: defines proto schemas for prediction requests with typed tensors, implements streaming RPC for sequence processing. Configures gRPC clients with retry policies and deadlines for model serving calls, optimizes large tensor serialization via Protobuf. | |
| NLP Engineer | Independently designs gRPC API for NLP services: streaming for long text processing, bidirectional streaming for real-time NLP. Defines efficient protobuf schemas for NLP data. | |
| Technical Lead | Independently designs gRPC services for team-owned microservices — defines proto schemas with proper type hierarchies and oneof patterns, implements interceptors for logging and authentication, and establishes proto style guidelines. Writes comprehensive API documentation and integration tests for service contracts. | |
| Technical Writer | Creates gRPC API documentation: service reference, message schemas, streaming patterns, error codes. Configures auto-generation of documentation from .proto files (protoc-gen-doc, buf). Documents proto style guide. | |
| Telecom Developer | Independently designs gRPC services for telecom network management — configuration distribution with streaming updates, efficient proto schemas for network element state and alarm data, and bidirectional streaming for real-time telemetry. Writes comprehensive proto documentation and conformance tests for telecom service contracts. |
| Rol | Obligatorio | Descripción |
|---|---|---|
| Backend Developer (C#/.NET) | Designs gRPC architecture: service-to-service communication, load balancing, proto schema governance. | |
| Backend Developer (Elixir) | Designs gRPC architecture for the Elixir platform: service mesh integration, bidirectional streaming, load balancing. Optimizes serialization performance. | |
| Backend Developer (Go) | Obligatorio | Develops advanced gRPC services in Go: bidirectional streaming, deadline propagation via context, retry policies through grpc-middleware. Optimizes protobuf serialization, configures connection pooling and load balancing via gRPC name resolver. |
| Backend Developer (Java/Kotlin) | Designs gRPC architecture: service mesh integration, load balancing, proto schema governance. | |
| Backend Developer (Node.js) | Designs gRPC architecture: service mesh integration, bidirectional streaming, load balancing. Optimizes serialization. | |
| Backend Developer (PHP) | Designs gRPC API for PHP microservices: Protobuf versioning strategy, backward compatibility, streaming RPC for large data processing. Optimizes gRPC performance on PHP via RoadRunner, configures gRPC-gateway for REST compatibility, and implements interceptors for logging and authentication. | |
| Backend Developer (Python) | Designs gRPC architecture: service-to-service communication, load balancing, schema governance. | |
| Backend Developer (Rust) | Obligatorio | Designs gRPC architecture for Rust services: bidirectional streaming for real-time data, health checking through tonic-health, load balancing with tower. Optimizes serialization through prost with custom codecs and implements graceful shutdown for streaming connections. |
| Backend Developer (Scala) | Obligatorio | Designs gRPC API for Scala microservices: bidirectional streaming through Akka gRPC/FS2-gRPC, retry policies, load balancing. Implements Schema Registry for Protobuf, builds gRPC-Web for browser clients and optimizes performance through connection multiplexing and compression. |
| Computer Vision Engineer | Obligatorio | Designs gRPC API architecture for production computer vision platforms — multi-model inference service mesh with efficient proto schemas, video streaming pipelines with flow control, and versioned vision service contracts supporting model evolution. Defines error handling standards for vision-specific failures and optimizes proto serialization for high-throughput image processing. |
| Data Engineer | Obligatorio | Designs gRPC interfaces for data services: bidirectional streaming for CDC, server streaming for bulk data delivery. Integrates Protobuf with Schema Registry for centralized schema management. |
| Fullstack Developer | Designs gRPC architecture: service-to-service gRPC, browser gRPC-Web, schema evolution strategy. | |
| Game Server Developer | Obligatorio | Designs gRPC API architecture for production game server ecosystems — low-latency game state synchronization with custom flow control, efficient proto schemas for deterministic game simulation, and versioned game service contracts supporting live-service updates. Defines error handling for gameplay-specific failure modes and optimizes serialization for real-time competitive gaming scenarios. |
| LLM Engineer | Obligatorio | Designs gRPC API architecture for production LLM serving platforms — token streaming with backpressure management, efficient proto schemas for multi-modal inference with embeddings, and versioned model serving contracts supporting A/B testing. Defines error handling for inference timeout and rate limiting scenarios and optimizes serialization for high-throughput token generation. |
| ML Engineer | Designs gRPC architecture for ML serving platform. Optimizes serialization for ML data (tensors, embeddings). Configures load balancing for gRPC ML services. | |
| MLOps Engineer | Obligatorio | Architects gRPC API for the MLOps platform: bidirectional streaming for real-time inference, efficient batch prediction serialization, integration with Triton Inference Server via custom proto extensions. Optimizes gRPC performance for ML serving — zero-copy tensor deserialization, connection pooling, and load balancing across GPU replicas. |
| NLP Engineer | Designs high-performance gRPC services for production NLP systems. Optimizes serialization for large text payloads, configures load balancing and connection pooling. | |
| Solutions Architect | Obligatorio | Designs enterprise gRPC API architecture for microservice ecosystems — service mesh integration with gRPC health checking, proto schema registries for cross-team contract management, and multi-language code generation pipelines. Defines versioning and backward compatibility standards and optimizes gRPC performance through connection pooling and load balancing strategies. |
| Technical Lead | Obligatorio | Designs gRPC API architecture for production microservice platforms — interceptor chains for cross-cutting concerns, proto schema evolution with backward compatibility guarantees, and deadline propagation across service boundaries. Defines error handling standards with rich status details and optimizes gRPC performance through connection management and compression strategies. |
| Technical Writer | Documents complex gRPC patterns: bidirectional streaming, interceptors, load balancing, deadlines. Creates architecture docs for gRPC-based microservices. Develops migration guides for proto contract updates. | |
| Telecom Developer | Obligatorio | Designs gRPC API architecture for carrier-grade telecom platforms — network function service mesh with proto schemas for 3GPP-aligned data models, streaming telemetry with gNMI patterns, and versioned network management contracts. Defines error handling for carrier-grade reliability and optimizes gRPC for high-throughput signaling workloads. |
| Rol | Obligatorio | Descripción |
|---|---|---|
| Backend Developer (C#/.NET) | Defines gRPC standards for C# service development — establishes proto governance with protobuf-net and Grpc.Net conventions, error handling policies with rich gRPC status codes, and versioning strategy for .NET gRPC service evolution. Coordinates cross-team proto file management and code generation workflows. | |
| Backend Developer (Elixir) | Defines gRPC standards: proto schema governance, versioning policy, error handling conventions. Implements contract testing and automated compatibility checks. | |
| Backend Developer (Go) | Obligatorio | Defines gRPC communication standards for Go microservices: .proto repository management, buf lint validation, backward compatibility strategies. Implements service mesh integration, standardizes interceptor chains and gRPC metrics monitoring via Prometheus. |
| Backend Developer (Java/Kotlin) | Defines gRPC standards for Java service development — establishes proto governance with protobuf-java conventions, error handling policies with StatusException patterns, and versioning strategy for Spring Boot gRPC service evolution. Coordinates cross-team proto registry management and gradle/maven code generation workflows. | |
| Backend Developer (Node.js) | Defines gRPC standards: proto governance, versioning policy, error handling conventions. Implements contract testing. | |
| Backend Developer (PHP) | Defines gRPC communication standards for the PHP platform: .proto file style guide, CI compatibility validation, service registry. Leads REST to gRPC transition for internal communications, configures service mesh for gRPC traffic management, and trains teams on the Protobuf ecosystem. | |
| Backend Developer (Python) | Defines gRPC standards for Python service development — establishes proto governance with grpcio/betterproto conventions, error handling policies with gRPC status codes and error details, and versioning strategy for Python gRPC service evolution. Coordinates cross-team proto file management and buf/protoc code generation workflows. | |
| Backend Developer (Rust) | Obligatorio | Defines gRPC communication standards for Rust platform: schema registry for .proto files, backwards-compatible message evolution, shared crates with generated code. Develops tower middleware stack for tracing, metrics and circuit breaking in gRPC calls. |
| Backend Developer (Scala) | Obligatorio | Defines gRPC interaction standards for Scala team: .proto file design rules, backward compatibility strategy, mandatory metadata fields. Reviews Protobuf schemas, implements buf for linting and breaking change detection, configures gRPC health checks for Kubernetes readiness probes. |
| Computer Vision Engineer | Obligatorio | Defines gRPC API strategy for computer vision service portfolios — establishes proto governance for vision model serving contracts, designs cross-team schema evolution policies for vision pipeline APIs, and coordinates standardized streaming patterns for image/video processing services. |
| Data Engineer | Obligatorio | Defines serialization strategy: Protobuf vs Avro vs JSON for different scenarios (streaming vs batch, internal vs external). Implements schema management standards and compatibility checking. |
| Fullstack Developer | Defines gRPC standards: when gRPC vs REST vs GraphQL, proto governance, versioning policy. | |
| Game Server Developer | Obligatorio | Defines gRPC API strategy for game server platforms — establishes proto governance for game service contracts across titles, designs versioning policies for live-service game APIs, and coordinates standardized streaming patterns for real-time game state synchronization. |
| LLM Engineer | Obligatorio | Defines API strategy at product level. Establishes design standards. Conducts API design reviews. Coordinates cross-team API interaction. |
| ML Engineer | Defines gRPC strategy for ML infrastructure. Designs service mesh for ML serving. Coordinates protobuf schema evolution. | |
| MLOps Engineer | Obligatorio | Defines gRPC usage standards in the team's ML infrastructure: unified proto definitions for inference APIs, standardized error handling and metadata. Implements gRPC interceptors for prediction logging, latency metric collection, and request tracing via OpenTelemetry across the ML service chain. |
| NLP Engineer | Defines gRPC API standards for the NLP team. Establishes guidelines for protobuf schema design, versioning strategy, and backward compatibility for NLP services. | |
| Solutions Architect | Obligatorio | Defines enterprise gRPC API strategy spanning product domains — establishes organizational proto governance, schema registry management, and cross-team backward compatibility policies. Conducts API design reviews and coordinates unified gRPC standards across engineering teams. |
| Technical Lead | Obligatorio | Defines API strategy at the product level. Establishes design standards. Conducts API design reviews. Coordinates cross-team API interaction. |
| Technical Writer | Defines gRPC/Protobuf documentation standards for the organization. Implements automated pipelines for proto docs. Ensures consistency when multiple teams work on shared proto contracts. | |
| Telecom Developer | Obligatorio | Defines gRPC API strategy for telecom network management platforms — establishes proto governance for 3GPP-aligned service contracts, designs versioning policies for network function APIs, and coordinates standardized streaming patterns for telemetry and configuration services. |
| Rol | Obligatorio | Descripción |
|---|---|---|
| Backend Developer (C#/.NET) | Shapes gRPC strategy: multi-language gRPC ecosystem, schema evolution, governance. | |
| Backend Developer (Elixir) | Shapes gRPC strategy: Elixir gRPC vs REST trade-offs, cross-language service communication, schema evolution governance for microservices platform. | |
| Backend Developer (Go) | Obligatorio | Shapes organizational inter-service communication strategy via gRPC: unified proto-registry, API evolution standards, platform protoc plugins. Develops shared gRPC libraries with tracing, circuit breaker, and automatic client generation. |
| Backend Developer (Java/Kotlin) | Shapes gRPC strategy: multi-language ecosystem, schema evolution, governance. | |
| Backend Developer (Node.js) | Shapes gRPC strategy: gRPC vs REST choice, cross-language communication, schema evolution governance. | |
| Backend Developer (PHP) | Architecturally designs inter-service communication strategy for the PHP ecosystem: gRPC vs REST vs GraphQL for different scenarios, evolution toward event-driven architecture. Defines platform solutions for API governance, SDK auto-generation from .proto specifications, and gRPC integration with the observability stack. | |
| Backend Developer (Python) | Shapes gRPC strategy: cross-language gRPC, schema evolution, governance. | |
| Backend Developer (Rust) | Obligatorio | Shapes organizational gRPC strategy: service mesh integration (Linkerd) with Rust services, backward compatibility protocols, multi-language code generation. Defines gRPC gateway architecture for REST clients and performance tuning standards (HTTP/2 settings, message size limits). |
| Backend Developer (Scala) | Obligatorio | Shapes inter-service communication strategy for Scala platform: gRPC as internal communication standard, Service Mesh integration through Envoy/Istio. Defines API Gateway architecture for gRPC/REST translation, Protobuf schema evolution policies and RPC call observability standards. |
| Computer Vision Engineer | Obligatorio | Defines organizational API strategy. Designs platform API. Establishes enterprise API governance and standards. |
| Data Engineer | Obligatorio | Designs data platform serialization strategy: unified schema registry, cross-format compatibility, schema evolution governance. Defines when Protobuf vs Avro vs Parquet schemas. |
| Fullstack Developer | Shapes API strategy: multi-protocol API architecture, schema governance, API evolution. | |
| Game Server Developer | Obligatorio | Defines organizational gRPC API strategy for game service platforms — designs platform-level proto governance for real-time game communication standards across titles. Establishes enterprise API architecture balancing ultra-low latency requirements with schema flexibility and cross-platform compatibility. |
| LLM Engineer | Obligatorio | Defines organizational API strategy. Designs platform APIs. Establishes enterprise API governance and standards. |
| ML Engineer | Defines communication strategy for enterprise ML. Evaluates gRPC vs REST vs custom protocols for ML workloads. Designs inter-service communication architecture. | |
| MLOps Engineer | Obligatorio | Shapes the inter-service communication strategy for the MLOps platform: gRPC as the standard for internal ML services, REST for external APIs. Designs a unified proto repository for the organization, defines backward compatibility policies for inference APIs, and migration strategy from REST to gRPC for latency-critical serving paths. |
| NLP Engineer | Shapes enterprise gRPC strategy for the NLP platform. Defines inter-service communication architectural patterns, API governance standards, and protocol evolution at organizational level. | |
| Solutions Architect | Obligatorio | Defines organizational gRPC API strategy as a core enterprise communication platform — designs platform-level proto registry and governance supporting hundreds of services. Establishes enterprise API standards balancing performance, developer experience, and cross-team schema interoperability. |
| Technical Lead | Obligatorio | Defines organizational gRPC API strategy spanning all product domains and engineering teams — designs platform-level proto governance, schema registry infrastructure, and enterprise code generation pipelines. Establishes organizational API standards for gRPC service development ensuring consistency and backward compatibility. |
| Technical Writer | Shapes inter-service communication documentation strategy at the company level, including gRPC, event-driven, and hybrid approaches. Defines how proto documentation integrates with the overall developer portal. | |
| Telecom Developer | Obligatorio | Defines organizational gRPC API strategy for carrier-grade telecom platforms — designs platform-level proto governance aligned with 3GPP and IETF standards for network function communication. Establishes enterprise API architecture for telecom service mesh spanning multiple network generations and vendor interoperability. |