Playlab Staff Platform Engineer at Playlab to build infrastructure and APIs for deploying safe edtech apps. Focus on designing platform blocks, Terraform, monitoring, alerts, and incident management.
Responsibilities
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.
Build the building blocks
Make powerful capabilities right for education. Build capabilities like agent memory, image generation, and data storage with the shape it needs before it reaches a classroom. You'll design these with product, privacy and security, and trust and safety experts, grounded in what we learn in schools, then build them in so every app and agent gets them by default.
Design blocks others can build. You'll play a pivotal role in the team deciding how new core infrastructure works - designing APIs and leading builds, so new features and experiences can be scaffolded on solid foundations.
Turn our data into something schools can learn from. Grow our warehouse and data vault into the place where schools and their research partners can answer questions about AI in their classrooms.
Ship early and learn. You can expect to ship major new infrastructure in production within your first month, and evolve it as new usage patterns emerge.
Own where agents run
Give educators' agents a powerful place to run. A runtime where the agents and apps educators build can use tools, run code and work for hours on a teacher's behalf, safe enough for classrooms by default.
Build the infrastructure for educational evaluations. Make it easy to run, store and compare evaluations at scale that help teachers and students understand where the things they build are performing or not, and help the field learn from what they build.
Set the standards and open them up
Qualification
Experience working with privacyHands-on experience with AWSBuilding MCP serversWorking with student or children's dataTypeScript
Required
Experience designing systems that work together as a platform with shared conventions and consistent APIs
Experience working with privacy, safety, or policy experts to incorporate requirements
Experience leading engineers through infrastructure projects from design to production
Hands-on experience with AWS, Kubernetes, and Terraform
Experience building systems behind LLM or agent products
Experience building APIs or SDKs used by product engineers
Ability to change designs based on real user behavior
Preferred
Building safety or fairness controls into an AI product.
Maintaining an open source project other people depend on.
Building MCP servers, agent runtimes, sandboxes for untrusted code or LLM gateways, including model routing and cost optimization (we use LiteLLM).
Building identity and auth that other products rely on (SSO, OAuth, "sign in with" flows).
Building data warehouses or research data pipelines that protect personal data.
Working with student or children's data, or in education.