Senior/Principal Platform Engineer, ML Platform

The role is titled 'Principal Platform Engineer' but the requirements gate on only 5+ years of experience and a Bachelor's degree — scope and experience requirements are consistent with a Senior-level individual contributor, not a true Principal (org-wide technical authority). Seniority is assessed as Senior accordingly.

The posting is headquartered in San Mateo, CA (San Mateo County), which falls within the San Francisco-Oakland-Hayward, CA CBSA (41860). The role requires in-office presence Tuesday–Thursday, so remote=false.

SOC classification is Medium confidence: the role is primarily a platform/backend software engineering role (building APIs, SDKs, CLIs, control planes) that also spans ML infrastructure. 15-1299 is noted as a runner-up given the ML platform specialization, but the primary day-to-day work is shipping software.

API design, gRPC/REST, SDK/CLI development, ML lifecycle (serving, training, CI/CD), GPU management, and infrastructure-as-code are all listed under the 'You Have' requirements section and are treated as hard gates.

Model Registry and Pipeline Orchestrator are specific platform components mentioned in the responsibilities ('You Will') section rather than the requirements section, so they are marked as preferred context rather than hard gates.

Hands-on ML experience is explicitly called 'a plus' in the posting intro, so no ML-specific framework skills (e.g. PyTorch, TensorFlow) are listed — none were named as required or preferred in the JD.

Ignored 5 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): API design, SDK development, CLI development, ML model training infrastructure, GPU resource management.