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’re building a world
where every kid gets an education they love
See open roles
ClassDojo raises $125 million in Series D
We transformed a decade of grassroots growth into a valuation of over $1.2 billion
Remote first
Our team hails from all around the globe, and we like it that way.
As a remote team, we are spread from Canada to Argentina, working in U.S. time zones. We also understand the value of working and building relationships face to face, so we make an effort to get together a couple of times a year. Our interview process is fully remote, too; we'll start with a quick call to get to know each other before moving onto a coding challenge and, if things go well, a virtual onsite.Dojo Islands is the first and largest digital playground of its kind. Our culture makes it possible.
How we roll
Behind the scenes is a hardworking team with strong principles that evolve for every phase along the way.
Collaboration > Parallelism
Two brains (or three, or four) are better than one, so we tackle almost everything as a team. We ask for help when we need it, but we also take the responsibility to proactively ask each other how we can offer support. We’re always unblocking each other.
Trust > Control
Everyone on the team has the same goals and world-class expertise, so there’s no micromanagement here—just a supportive community backing you up as you own your projects.
Candor > Harmony
Serious teamwork requires serious communication skills, so we always say the hard things with respect and kindness. Anything else cheats everyone out of growth opportunities.
Finishing > Starting
Multitasking is a great recipe for iffy work, so we do just a few things at a time with extra precision and urgency. When we say “finished,” we mean “in users’ hands.” It’s a high bar, but intense focus makes it possible.
Humanity > Heroism
We know that downtime isn’t an indulgence—it’s a necessity. We take rest seriously because it increases productivity, and we minimize interruptions that can throw workflows out of whack.
Continuous Improvement > Continuous Production
We’re constantly evaluating not just our product, but our productivity: we regularly schedule retrospectives and post mortems to find better ways forward. By investing in ourselves, we’re planting the seeds for better work and better work-life balance.
Take it from our team
Sahar BSoftware Engineer, Full Stack“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.”
Puri BeySoftware 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.”
Noah WienerSoftware Engineer, Full Stack“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.”
Built on lots of LOVE
Millions of users = millions of smiles
Mrs. K@artwithmrs_k
Julissa R.@jd_rowell
Mrs. K@artwithmrs_k
Julissa R.@jd_rowell
Mrs. K@artwithmrs_k
Jennifer H. Ed.D@jennifermhardin
Katie E.@katieerb
Mrs. W@mrswscholars
Mrs. K@artwithmrs_k
Jennifer H. Ed.D@jennifermhardin
Katie E.@katieerb
Mrs. W@mrswscholars
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
