How are Developer Platform engineers evaluated at scale (Alphabet-style orgs)?

For those who’ve worked on

Developer Platform / Internal Platform teams at large-scale organizations : How do teams typically evaluate platform engineers compared to product-focused engineers duri

For those who’ve worked on

Developer Platform / Internal Platform teams at large-scale organizations : How do teams typically evaluate platform engineers compared to product-focused engineers during hiring? I’m interested in perspectives on: * The balance between hands-on coding and architectural/system-level reasoning * Whether system design is usually expected for platform roles, and at what depth (APIs, abstractions, reliability, DX, guardrails, etc.) * What tends to differentiate strong platform candidates: implementation quality, tradeoff analysis, operability, developer experience, or collaboration * How panel-style evaluations are commonly structured for platform engineers versus feature teams I’ve seen expectations vary widely depending on org size and platform maturity, so I’m curious how this is handled in practice at scale and what experienced engineers have found to be most consistent. Not looking for interview questions or prep more interested in how experienced teams think about evaluating platform engineers.