Candor > Harmony
Say the hard thing when it needs saying, and do it with kindness.
Work at ClassDojo
With over 45 million kids on ClassDojo today, we’re gearing up to the biggest learning boom in history. Are you ready for take off?
Remote first
We're a remote team spread from Canada to Argentina, working across U.S. time zones. We get together in person a couple times a year and our interview process is fully remote.
Dojo made #4 on the list of America's best EdTech companies
Create global impact every time you come to work.
At Dojo, each engineer supports over a million active users a month. We're building the world's largest network for families with kids under 13, and we're already in 180 countries and 95% of U.S. schools. When kids are free to find their spark, the world shines brighter.
Build an education every child loves
From early reading to imaginative play to 1-to-1 tutoring, the products we build reach kids and families around the world.
Learning to read, superpowered!
The revolutionary reading coach that listens, encourages, and grows with your child, one sound at a time.
A world they can shape, build, and imagine
With Dojo Islands, kids can design their own spaces, solve challenges, and explore at their own pace—all while building confidence through play.
Proven. Personal. Effective.
Dojo Tutor pairs your students with certified teachers for 1-to-1 support in reading, math, and more. It's high-impact tutoring that's easy to scale and proven to help students thrive, in school and beyond.
How we roll
Behind the scenes is a hardworking team with strong principles that evolve for every phase along the way.
Trust > Control
Trust people closest to the work, then back it up with context, alignment, and clear agreements.
Humanity > Heroism
Protect downtime and sustainable pace, because burnout isn’t a badge.
Finishing > Starting
Limit work in progress and take work all the way to users, because “almost done” is still not done.
Shared Ownership > Specialization
Own the outcomes together, spread knowledge, and don’t build single-person bottlenecks.
Collaboration > Parallelism
Swarm, ask for help, and communicate clearly so no one gets stuck alone.
Failure Recovery > Failure Avoidance
Prefer fast feedback and quick recovery over chasing “perfect” up front.
Continuous Improvement > Continuous Production
Make time to reflect, learn, and improve the system—“try harder” doesn’t count.
We're always hiring exceptional people to shape Dojo's future. Here are the roles we're actively hiring for.
If the embedded board is blocked by browser privacy settings, view all engineering roles directly on Ashby.
Take it from our team
We're building a world where every child loves learning. Here is what it feels like from the inside.
“We serve millions of teachers and families with a small, focused team. Despite our scale, it somehow never feels chaotic or stressful, and that comes down to the people. Teammates here are genuinely kind, guilds actually function, and when you spot something broken or have a good idea, you raise it and people show up to help you fix it. The work matters, and so do you.”
Sahar B
Software Engineer, Full Stack
“I love how passionate everyone is and how I'm always learning new things, but most of all, I love our work environment. People here care about your mental state and encourage you to keep it healthy. The bar is high, but it’s always a lot of fun. ClassDojo has improved me as an engineer and as a professional in so many ways.”
Puri Bey
Full-stack Engineer, Argentina
“There's a deep focus on ownership, emphasis on the full side of full-stack, and readiness to empower engineers to learn new things. Ownership focus spans an incredible range—from owning features with sophisticated & thoughtful monitoring to the ability to own technical realms. It is very easy & encouraged for an engineer to choose an area to level up in, and make company-wide improvements in that space.”
Noah Wiener
Software Engineer, USA
“We serve millions of teachers and families with a small, focused team. Despite our scale, it somehow never feels chaotic or stressful, and that comes down to the people. Teammates here are genuinely kind, guilds actually function, and when you spot something broken or have a good idea, you raise it and people show up to help you fix it. The work matters, and so do you.”
Sahar B
Software Engineer, Full Stack
“I love how passionate everyone is and how I'm always learning new things, but most of all, I love our work environment. People here care about your mental state and encourage you to keep it healthy. The bar is high, but it’s always a lot of fun. ClassDojo has improved me as an engineer and as a professional in so many ways.”
Puri Bey
Full-stack Engineer, Argentina
“There's a deep focus on ownership, emphasis on the full side of full-stack, and readiness to empower engineers to learn new things. Ownership focus spans an incredible range—from owning features with sophisticated & thoughtful monitoring to the ability to own technical realms. It is very easy & encouraged for an engineer to choose an area to level up in, and make company-wide improvements in that space.”
Noah Wiener
Software Engineer, USA
Top questions
We use TypeScript with Node.js on the back-end and React on the front-end. It's all hosted on AWS, using Terraform, Nomad, and Consul, with MySQL and MongoDB as our databases. Our iOS app is Swift, and our Android app is a hybrid mobile web app.
We are a high-trust, low-control engineering environment with a heavy focus on automation, tests, production monitoring and quality in general.
We have a low reliance on human inspection: pull requests are neither mandatory nor blocking in most cases, and we don't employ manual testers ("QA") at the company at all. We hire people who care about quality and collaboration, and we don't want to police it.
We are probably more collaborative than most places, often pair programming or mob programming (but not all the time). Teams and individual engineers have a lot of autonomy in technical decision-making.
We have a low reliance on human inspection: pull requests are neither mandatory nor blocking in most cases, and we don't employ manual testers ("QA") at the company at all. We hire people who care about quality and collaboration, and we don't want to police it.
We are probably more collaborative than most places, often pair programming or mob programming (but not all the time). Teams and individual engineers have a lot of autonomy in technical decision-making.
Our approach is mostly inspired by Kanban: we don't do sprints or traditional estimates, but we do have many familiar practices such as standups, weekly planning, and retrospectives. We pursue Continuous Development very aggressively, deploying many times per day in almost all codebases.
Yes, we do—but it's straight forward. The rotation currently puts each engineer on-call every 12 weeks or so. We always prioritize fixing issues that occur during off-hours higher than everything else so they don't keep interrupting our lives.
Yes, a lot! We encourage the use of local and remote agents, and are continuously exploring and deploying new AI powered tools and practices. We found that our engineering practices fit agentic workflows very well, and have doubled down on many of the things we’ve been doing for years already such as CI/CD, test automation, and observability. This is of course a fast moving area, and we try to be balanced and not to forget the values that have made us successful so far as an engineering org as we adopt new ways of working.
How we work
Read articles created from our engineering team
Our Approach to Mob Programming
Our teams at ClassDojo have the freedom to choose how they want to work. Many of our teams have started spending a few hours each day mobbing because we've found it to be an effective form of collaboration. Here's how we do it!
P1, P2,...P5 is a broken system: here's what we do instead
Software developers need to prioritize bugs when they are discovered, and most do this with an ordered priority scheme. Tracking tools like Jira provide a column on each ticket, and many organizations use numbers, such as P1, P2, P3, P4, and P5.
Why we don't do blocking pull requests
One aspect of our workflow that people often find odd or new to them is that we don’t require an up-front code review or pull request with signoff from another engineer before pushing to production. This often comes up in interviews or conversations with engineers who are interested in jobs at ClassDojo, with reactions ranging from curiosity to aversion.
Powered by lots of love
Millions of users, millions of smiles — here's a snippet of what teachers and families share every day.