API Styles & Formats
REST, GraphQL, gRPC and the data formats they carry.
Backend Engineer track
Junior
Write correct code, ship small changes safely, ask good questions.
Core: start here
- EndpointA specific URL and method an API exposes, like POST /orders.
- JSONThe text data format most APIs speak.
- Request and Response BodyThe payload sent with a request or returned in a response, usually JSON.
- RESTAn API style built on resources, URLs and HTTP methods.
4 more junior concepts
- APIAn interface that lets programs talk to each other.
- Resource NamingPlural nouns, nested paths and consistent URL design.
- SerializationConverting objects to bytes or text for storage or transfer.
- YAMLA human-friendly data format common in configuration files.
Mid-level
Own a feature end to end without hand-holding.
- API Client / SDKA library wrapping an API so callers don't hand-write HTTP.
- GraphQLA query language that lets clients ask for exactly the data they need.
- GraphQL Schema and ResolversTypes describing the data, and functions that fetch each field.
- gRPCA fast RPC framework built on HTTP/2 and Protocol Buffers.
- JSON SchemaA vocabulary for validating the structure of JSON.
- OpenAPIA standard format for describing REST APIs.
- Protocol BuffersA compact, schema-based binary serialization format.
- Resource ModelingDeciding what your API's resources are and how they relate.
- REST ConstraintsStatelessness, uniform interface, cacheability and REST's other rules.
- RPCCalling a function on another machine as if it were local.
- XMLA verbose markup format still common in enterprise and legacy systems.
Senior
Own a system, its failure modes, and its trade-offs.
- AvroA binary serialization format whose schemas are designed to evolve.
- DataLoader / N+1 in GraphQLBatching resolver lookups so nested queries don't explode.
- MessagePackA compact binary alternative to JSON.
- REST vs GraphQL vs gRPCChoosing an API style for the clients and teams you have.
- Richardson Maturity ModelLevels of REST maturity, from one endpoint to hypermedia.
- Schema EvolutionChanging data formats so old and new readers and writers keep working.
- SOAPAn older XML-based protocol for web services.
Staff
Shape how many teams build, across systems.
Nothing here yet.
Principal
Set technical direction for the organization.
Nothing here yet.
Data Analyst track
Junior
Write correct SQL, build trusted dashboards, ask good questions.
Mid-level
Own an analysis end to end, from vague question to recommendation.
Nothing here yet.
Senior
Own experimentation and metrics design; call out bad numbers.
Nothing here yet.
Staff
Shape how the organization measures and decides.
Nothing here yet.
Principal
Set measurement strategy across the company.
Nothing here yet.
Data Engineer track
Junior
Build and fix pipelines from clear specs; write correct SQL.
- APIAn interface that lets programs talk to each other.
- EndpointA specific URL and method an API exposes, like POST /orders.
- JSONThe text data format most APIs speak.
- Request and Response BodyThe payload sent with a request or returned in a response, usually JSON.
- Resource NamingPlural nouns, nested paths and consistent URL design.
- RESTAn API style built on resources, URLs and HTTP methods.
- SerializationConverting objects to bytes or text for storage or transfer.
- YAMLA human-friendly data format common in configuration files.
Mid-level
Own pipelines and models end to end, including their quality.
Core: start here
- Schema EvolutionChanging data formats so old and new readers and writers keep working.
11 more mid-level concepts
- API Client / SDKA library wrapping an API so callers don't hand-write HTTP.
- AvroA binary serialization format whose schemas are designed to evolve.
- GraphQLA query language that lets clients ask for exactly the data they need.
- gRPCA fast RPC framework built on HTTP/2 and Protocol Buffers.
- JSON SchemaA vocabulary for validating the structure of JSON.
- OpenAPIA standard format for describing REST APIs.
- Protocol BuffersA compact, schema-based binary serialization format.
- Resource ModelingDeciding what your API's resources are and how they relate.
- REST ConstraintsStatelessness, uniform interface, cacheability and REST's other rules.
- RPCCalling a function on another machine as if it were local.
- XMLA verbose markup format still common in enterprise and legacy systems.
Senior
Design the platform's storage, processing and modeling choices.
- MessagePackA compact binary alternative to JSON.
- REST vs GraphQL vs gRPCChoosing an API style for the clients and teams you have.
- Richardson Maturity ModelLevels of REST maturity, from one endpoint to hypermedia.
Staff
Shape how the whole organization produces and uses data.
Nothing here yet.
Principal
Set data strategy and architecture across the company.
Nothing here yet.
Frontend Engineer track
Junior
Build UI that works, ship small changes safely, ask good questions.
Core: start here
- EndpointA specific URL and method an API exposes, like POST /orders.
- JSONThe text data format most APIs speak.
- Request and Response BodyThe payload sent with a request or returned in a response, usually JSON.
- RESTAn API style built on resources, URLs and HTTP methods.
4 more junior concepts
- APIAn interface that lets programs talk to each other.
- Resource NamingPlural nouns, nested paths and consistent URL design.
- SerializationConverting objects to bytes or text for storage or transfer.
- YAMLA human-friendly data format common in configuration files.
Mid-level
Own a feature end to end without hand-holding.
- API Client / SDKA library wrapping an API so callers don't hand-write HTTP.
- GraphQLA query language that lets clients ask for exactly the data they need.
- GraphQL Schema and ResolversTypes describing the data, and functions that fetch each field.
- JSON SchemaA vocabulary for validating the structure of JSON.
- OpenAPIA standard format for describing REST APIs.
- Resource ModelingDeciding what your API's resources are and how they relate.
- REST ConstraintsStatelessness, uniform interface, cacheability and REST's other rules.
- RPCCalling a function on another machine as if it were local.
- tRPCEnd-to-end type-safe APIs for TypeScript without a schema language.
- XMLA verbose markup format still common in enterprise and legacy systems.
Senior
Own an app's architecture, performance, and failure modes.
- DataLoader / N+1 in GraphQLBatching resolver lookups so nested queries don't explode.
- MessagePackA compact binary alternative to JSON.
- REST vs GraphQL vs gRPCChoosing an API style for the clients and teams you have.
- Richardson Maturity ModelLevels of REST maturity, from one endpoint to hypermedia.
- Schema EvolutionChanging data formats so old and new readers and writers keep working.
Staff
Shape how many teams build, across apps.
Nothing here yet.
Principal
Set technical direction for the organization.
Nothing here yet.