Senior Technical Producer - Online Platform

Level is a learning technology company dedicated to helping students build real academic and life skills with confidence and joy. We combine proven curriculum principles with world class interactive design to make meaningful practice something students want to come back to, not something they struggle through.

We support what teachers, schools, and parents are already doing by increasing student engagement with high quality, standards aligned practice that reinforces classroom learning. That's why we're building:

For students: Rewarding and motivating learning experiences that meet students where they are to build real academic proficiency.

For educators: Tools that fit naturally into instruction and help students stay engaged while reducing teacher workload.

For parents: Activities that help your kid catch up or get ahead, build confidence, and minimize homework battles, whether learning at school or at home.

We are committed to helping every person maximize their potential and live a life of meaning. It's a difficult problem that requires brilliant people and tremendous effort over time.

Summary

Level is looking for a Senior Technical Producer to be the production and prioritization partner for our platform engineering team: the DevOps, build, test automation, infrastructure, data pipeline, and backend and online services that every Level game and learning product runs on. You will work shoulder to shoulder with platform engineering leaders to turn a steady stream of internal requests into a roadmap they trust, deciding what starts now, what is held until the need is validated, and what is cut. This is an engineer-aligned seat for someone who earns credibility in architecture and tradeoff conversations, and who keeps platform work tied to what Level is building for students, educators, and parents.

What You Will Do

• Run Platform Intake: Own the front door for platform engineering. Take in requests from game, learning, and content teams, dig into the problem behind each ask, and size effort and risk with the engineers who would build it.
• Own the Platform Roadmap: Build and maintain the roadmap with platform engineering leaders, sequencing work across DevOps, build and CI/CD, test automation, infrastructure, data pipelines, and backend and online services.
• Decide What Starts, Waits, or Gets Cut: Make the call with engineering leaders on what starts now, what is held until the need is validated, and what is cut, then communicate each decision and its rationale clearly to the teams who asked.
• Be a Technical Partner to Engineers: Engage directly with architecture proposals, migration plans, and build-versus-buy decisions. Read design docs and pipeline dashboards, challenge assumptions, and surface risks in dependencies, capacity, and rollout before they reach users or other teams.
• Drive Platform Programs to Adoption: Lead cross-cutting initiatives such as CI/CD and build migrations, environment and infrastructure changes, observability, and data pipeline work from scoping through rollout, and make sure internal teams actually adopt what ships.
• Connect Platform to the Rest of Level: Translate what game, EdTech, and content teams are shipping on a weekly live cadence into platform priorities, and translate platform constraints back into plans other teams can use. Keep the whole org aligned on what platform is doing and why.
• Balance Features, Debt, and Reliability: Weigh new capability against technical debt, infrastructure health, and cost, and explain those tradeoffs to engineering and company leadership in terms of business and learner impact.
• Build the Operating Model: Design and refine lightweight intake, planning, release, and incident follow-through processes that fit a growing team. The operating model is still being built, and you will help shape it rather than inherit it.
• Measure What Matters: Define platform success measures such as build and test turnaround, test reliability, deploy frequency, and cloud cost, and use them to inform prioritization and show the value of platform investment.
• Raise the Bar for Production: Mentor producers on technical production practices, partner with QA and SDET on release quality, and influence how Level approaches technical planning across projects.

Qualifications

Need to Have:

• 6+ years producing or program-managing platform, DevOps, build and release, infrastructure, data, or backend and online engineering teams
• Strong engineering credibility: a background as a software, SRE, production, or data engineer is ideal, and many years embedded in backend, infrastructure, or DevOps teams can provide the same depth
• Experience introducing developer productivity tooling, including AI-assisted development
• Owned a platform roadmap or portfolio with engineering leaders, not just schedules or status reporting
• Experience running an intake or prioritization process for internal customers, and the ability to point to work you sequenced, deferred pending validation, or cut, and explain why
• Technical fluency across CI/CD, build systems, test automation, cloud infrastructure (AWS, GCP, or Azure), observability, data pipelines, and distributed or online services
• Track record of shipping platform programs such as migrations, tooling rollouts, or infrastructure changes, and driving adoption by internal teams
• Ability to connect platform work to product, game, or business priorities across teams, and to communicate tradeoffs clearly to engineers and executives alike
• Experience at a games or live-service studio, or at a high-growth tech company such as edtech, SaaS, or mobile, where platform keeps pace with a fast release cadence
• Comfort structuring ambiguous work and building process from the ground up

Nice to Have:

• Hands-on software engineering, SRE, or data engineering experience, or a CS degree
• Experience on platform, central technology, or online services teams at a game studio
• Familiarity with game engines such as Godot, Unity, or Unreal
• Background in educational products, learning platforms, or student-facing applications
• Experience with infrastructure as code, observability tooling, and cloud cost management
• Understanding of data privacy and security practices for products used by children and schools
• Experience defining production practices, tooling standards, or hiring practices for a team