Member of Technical Staff, Platform Engineer (Console & SDK)

Orbifold AI, Inc.; Palo Alto, Northern (CA, KY); Hybrid; USD 180,000 - 260,000; Full time

Job summary

Orbifold AI in Palo Alto is seeking a Member of Technical Staff, Platform Engineer to build the partner console, viewer, and SDK. This role shapes the surface of our platform used by research engineers to run workloads and inspect results.

You will work across the stack, including TypeScript frontend and Python services, crafting robust API contracts and developer-facing tools in close collaboration with partners.

Qualifications

• 4+ years shipping production web applications.
• Strong modern TypeScript and frontend depth.
• Experience designing APIs or SDKs for external users.
• Experience with Python services or infrastructure.

Responsibilities

• Build the partner console to submit and monitor workloads.
• Design and own the SDK and public API.
• Create internal tooling for operators and researchers.
• Own the vertical end to end: TS frontend, Python services, contracts.
• Collaborate with partners to capture actual needs.

Skills

TypeScript proficiency

Frontend engineering depth

Self-driven

Product instinct

Tools

TypeScript frontend

Python backend

SDK development

API design

Job description

Member of Technical Staff, Platform Engineer (Console & SDK)

Build the product surface of our platform: the console partners run workloads from, the viewer they inspect results in, and the SDK that puts both in their own code.

About Orbifold AI

Orbifold AI is building the infrastructure layer for Physical AI. As intelligent systems move beyond language into the physical world, they require a fundamentally new understanding of physics, action, and interaction.

We partner with leading robotics and world model research teams to advance the foundations of embodied intelligence, enabling intelligent systems to perceive, understand, and operate in the real world.

The standards we set, and the infrastructure we build to scale them, will define the next frontier of robotics and Physical AI.

Role Overview

The infrastructure underneath is good and almost entirely invisible. Partners reach it today largely through us, through conversations, handoffs and engineers on both sides. That is how every infrastructure company starts, and it is not how any of them scale.

You will build what the partner touches. The console where a research team submits workloads and watches them run. The viewer where they inspect a result properly rather than taking our word for it. The SDK and API that let them do all of it from inside their own pipeline, without talking to anyone. This is the difference between a service and a platform, and right now it is one seat.

What You Will Work On

• Build the partner console: submit and monitor workloads, see status, throughput and progress, and understand what is happening without asking us.


• Design and own the SDK and public API. Clean, versioned, documented, and adoptable by a research engineer in an afternoon. This is the surface our reputation as a platform will rest on.


• Build the internal tooling our own operators and researchers use, on the same foundations, the same primitives should serve both.


• Own the vertical end to end: TypeScript front end, Python services behind it, and the contracts in between.


• Work directly with partners on what they actually need, rather than through a layer of translation.

What We Are Looking For

• 4+ years shipping production web applications, with strong modern TypeScript and real front-end engineering depth.


• Demonstrated API or SDK design for external consumers, and opinions about what makes one pleasant to adopt.


• Comfortable across the stack into Python services and infrastructure, rather than stopping at the API boundary.


• Product instinct. You will often be the person who notices the workflow is wrong, not just the code.


• Self-driven and high agency, with experience in fast-paced applied research or startup environments.

Nice to Have

• Video or 3D tooling: players, annotation interfaces, timeline editors, point-cloud or mesh viewers.


• A developer-facing SDK you shipped that external engineers actually adopted.


• ML tooling, labeling, or experiment platforms.


• Familiarity with distributed compute (Ray, Kubernetes) and what it is like to build a UI over something that is genuinely distributed.


• Design sensibility, and the willingness to use it.

Why This Role

• You build the first product surface this company has had. Almost nothing is decided yet, including the shape of it.


• Your users are research engineers at frontier labs: demanding, specific, and quick to tell you when something is wrong.


• Turn a service into a platform. That transition is the single highest-leverage thing an engineer can do at our stage, and this is the seat that does it.


• Real range: 3D rendering, distributed systems, developer experience, rather than one screen for two years.