Product Operations Lead

Toddle is an AI-powered teaching and learning platform for K–12 schools. Built by educators, for educators, it is used by over 200,000 educators across 2,500+ schools in 100+ countries.

Teachers today work 50+ hours a week. Too much of that time is spent navigating fragmented systems and administrative overhead. Our BHAG (Big Hairy Audacious Goal) is to save teachers 10+ hours every week while helping elevate their practices, so that time can go back to what matters most - teaching, learning, and meaningful time with students.

Our approach is three-pronged.

First, Toddle brings the entire teaching and learning lifecycle into one place . Teachers plan and map curriculum, create assessments and gradebooks, maintain student portfolios, communicate with families, and generate progress reports and transcripts - all from a single, coherent system. Toddle also supports adjacent workflows where teachers are closely involved, including attendance, timetables, calendars, accreditation, behaviour management, analytics, and insights.

Second , every layer of the platform is deeply AI-powered. Educators work with a thoughtful AI partner to plan curriculum, create lessons and assessments, assist with grading, write progress report comments, and derive insights from data. Toddle also offers student-facing AI Tutors, enabling highly personalized and immersive learning experiences.

Third, Toddle integrates seamlessly with the broader school technology ecosystem. The platform supports 50+ integrations across SIS platforms, content providers, data & integration platforms, and workspaces such as Google, Apple, and Microsoft.

You can watch our founder and CEO’s overview of Toddle here .

Headquartered in India with a multicultural team across 20+ countries, Toddle is built by former educators and school practitioners who understand the realities of classrooms firsthand. We care deeply about craft, clarity, and reducing unnecessary complexity for teachers. People who thrive at Toddle enjoy building thoughtful systems, care about real-world impact, and are motivated by long-term change in K-12 education.

About the role

As Product Operations Lead, you will work closely with our Co-founder and Head of Product to bring clarity and follow-through across eight teams and 70+ modules. You will keep roadmaps and priorities aligned, lead release planning, validate important school workflows before launch, and ensure teams review the results after release.

This is a hands-on role for someone who enjoys understanding complex software, asking precise questions, and helping teams turn decisions into dependable execution. You will build your education and product context progressively, working closely with designers, engineers, QA, curriculum specialists, customer-facing teams, and analytics.

You will own the planning and release-readiness process, recommend trade-offs, and bring unresolved priorities to a decision with the appropriate leads. Product direction remains with the founder and designated product and design leads, while engineering owns technical readiness.

Here’s what you’ll be doing

Keep roadmaps and priorities clear

Maintain a reliable view of active initiatives, owners, intended outcomes, priorities, dependencies, and milestones. Work with team leads to keep commitments current, identify conflicting priorities, and bring clear recommendations to product leadership.

Lead release planning

Coordinate release scope, dependencies, engineering-informed timelines, pilots, and wider rollouts. Bring together the people responsible for testing, documentation, internal enablement, and release communication. Surface risks early and follow decisions through to completion.

Validate product quality before release

Test realistic school workflows against agreed acceptance criteria. Identify incomplete flows, confusing experiences, unexpected behaviour, and relevant edge cases; document issues clearly and verify fixes. Partner with designers and domain owners to understand expected behaviour.

Coordinate readiness reviews and escalate unmet release criteria. Your hands-on validation will focus on selected important workflows, while engineering and QA retain ownership of regression coverage, automation, performance testing, and technical readiness.

Build useful goals and outcome reviews

Help product, design, and engineering leads establish clear team goals, initiative outcomes, and ownership. Work with analytics to define meaningful adoption measures, identify gaps in measurement, and ensure released work receives an outcome review. Track the actions agreed in response.

Connect customer evidence to planning

Bring together Canny requests, customer conversations, support issues, and adoption findings. Organise recurring problems into useful themes and help teams understand the evidence behind priorities. Develop your understanding of school workflows through direct customer exposure.

Keep leadership informed and teams aligned

Prepare concise weekly updates covering progress, priority changes, release risks, and decisions needed. Maintain a clear record of decisions and follow-up owners. Improve planning and reporting processes so teams can keep information current with less effort.

What you will bring

• •4+ years of experience in product operations, programme management, product management, or software delivery.
• •Relevant experience working with software product, design, and engineering teams. B2B SaaS experience is valuable.
• •Experience coordinating software releases across teams, identifying dependencies, and resolving competing priorities. You have personally validated important user workflows and followed issues through to resolution.
• •Strong analytical judgement and clear writing. You can turn customer feedback, product data, and delivery updates into useful recommendations.
• •Comfort learning complex software, testing realistic workflows, questioning assumptions, and documenting issues precisely.
• •Curiosity about education, attention to detail, and confidence to challenge constructively. Education-sector experience is helpful, but not essential.

Your first year at Toddle

We will establish baselines during your first three months for release readiness, unresolved priority conflicts, and time spent gathering updates. We will then agree numerical targets with you based on those baselines and your scope.

Within the first three months

• •Understand Toddle’s strategy, the teams you support, and the main school workflows in your initial scope.
• •Build relationships across design, engineering, QA, curriculum, customer-facing teams, and analytics; participate in customer conversations and review Canny themes.
• •Establish a trusted consolidated roadmap and release calendar for the teams in your initial scope, showing owners, priorities, dependencies, intended outcomes, and current commitments. Provide a concise weekly update on progress, risks, and decisions needed.
• •Coordinate an initial release from planning through rollout and validate selected school workflows alongside experienced colleagues. Document outstanding issues, decisions, and follow-up owners, while learning how adoption is measured.

Within six months

• •Independently run a consistent planning and release cadence for your agreed scope, with roadmaps and release calendars kept current and changes communicated to the relevant teams.
• •Surface dependencies and priority conflicts early enough for leads to act, with clear recommendations, decision owners, and agreed next steps.
• •Make readiness reviews a consistent part of selected releases, with agreed acceptance criteria, hands-on workflow checks, documented open issues, and readiness confirmed by the relevant owners. Follow release issues through to resolution.
• •Ensure significant initiatives have clear outcomes and owners. Review launches with analytics and product leads against agreed adoption measures, and track actions from those findings with n