Staff Platform Engineer
Playlab, Remote
The role
Playlab is looking for a Staff Platform Engineer to build the infrastructure and APIs that let anyone deploy edtech apps that are good and safe for students by default. Every new AI capability, from image generation to agent memory, arrives built for adults and businesses. On Playlab, students and teachers use these capabilities to build their own apps and agents, so each one has to work differently: web search with safety controls a district can tune, memory that doesn't harden into assumptions about a student, storage APIs that understand relationships between people in the school.
We're adding capabilities Playlab doesn't have yet and breaking the app we grew up as into composable, reusable building blocks for building the next generation of edtech. Our own engineers build on them first, then teammates who don't write code, then educators and students making apps tailored to their own classrooms. You'll join the platform team we're building to shape what those blocks are and lead the design and implementation of key pieces. We're committed to open sourcing our infrastructure over time, so your design decisions will be used well beyond Playlab.
This is a staff level individual contributor role reporting to engineering leadership. You'll stay close to schools and users and work with product, privacy and security, trust and safety, learning engineering, and machine learning to build products and agents on top of your work.
What you need
You're a systems designer who starts from the people using what you build and still loves to ship. You'd rather make ten engineers faster than be the fastest one yourself, and building for students makes a problem more interesting to you, not less.
- Have designed several systems that worked together as a platform: shared conventions, consistent APIs, and other teams building on them as usage and requirements changed.
- Have worked with privacy, safety or policy experts to make their requirements part of the product.
- Have led a few engineers through building new infrastructure: shaped the design with them, broke it into work, got it to production, and left conventions the team kept using.
- Are hands-on enough with AWS, Kubernetes and Terraform to take what you design to production yourself.
- Have built systems behind LLM or agent products, and have opinions about what agents need from infrastructure (state, memory, tool access, long-running work).
- Have built APIs or SDKs that product engineers loved using: clear abstractions, good docs, and a short path from idea to a first working feature.
- Have changed a design because of what you saw real users do, not just what they asked for.
If you meet most of these and the work excites you, we'd love to hear from you.