I’ve sat through enough “coding classes” for kids to last three lifetimes. I’ve seen the good, the bad, and the “this is just a YouTube video with a $20 price tag” variety. If you are looking to get your child started with block-based programming—the gold standard for introducing logic to kids ages 5-10—you are likely browsing Outschool. It’s a massive marketplace, and that’s both a blessing and a trap.
Parents often come to me asking, “How do I know if this person can actually teach?” They want to avoid the programs that promise to “make your child a coder in three hours” (a lie) or the classes that claim to be “interactive” but are really just a screen-share of someone else building a game while the students watch in silence. Let’s cut through the marketing noise.
The Difference Between "Showing" and "Teaching"
When you are evaluating an outschool teacher background, the most important filter is this: Do they prioritize student agency, or do they prioritize a polished final product?
In the world of Scratch, where kids use "snap together command blocks" to build, it is incredibly easy for a teacher to simply say, "Put the blue block here, then the yellow one, then the green one." That isn’t teaching. That’s an assembly line. A real teacher focuses on the why. If your child can’t explain why the character moved to the left after the class is over, they didn’t learn to code; they learned to follow instructions.
Before you commit, check the class description for these markers:
- Does the teacher mention troubleshooting? Do they talk about the "logic" behind the code? Is the class size small enough for them to actually see your child’s screen?
The "Kid Gets Stuck" Moments: Where the Real Teaching Happens
Every Scratch instructor who has actually taught a child—and not just recorded a tutorial—knows the exact moments where a student will hit a wall. These are https://americanspcc.org/best-scratch-coding-classes-for-kids-2026-guide/ the "frustration points." If a teacher hasn't anticipated these, they aren't prepared.
1. The Logic of Loops
Kids understand "do this" easily. They struggle when they have to tell the computer to "do this, five times." If a teacher explains loops using a real-world analogy (like tying shoes or brushing teeth) before touching the computer, they know their stuff.
2. The "Broadcast" Block
This is the bane of every 8-year-old’s existence. When a child learns how to make one character "tell" another character to start an action using the Broadcast block, they've unlocked a massive power-up. If the teacher glosses over this, your kid will be lost the second they try to make a multi-scene story.
3. Clones
Clones are where kids start making professional-looking games (like shooters or clickers). They are also where kids start crashing their browsers. A good teacher will show them how to use the "delete this clone" block before they go crazy spawning thousands of sprites.
Evaluating Scratch Teacher Credentials
When you look at scratch teacher credentials, don't just look for "Software Engineer" or "Computer Science Degree." Honestly, sometimes a CS major is the worst teacher for a 7-year-old because they don't remember what it's like to struggle with the concept of an X-Y coordinate plane. Look for teachers who have experience in:
Early Childhood Education (ECE). After-school STEM programs. A portfolio of student projects (not just their own).If their profile only shows off their own high-level coding projects, keep scrolling. You need a teacher who specializes in pedagogy, not just programming.
Live Instruction vs. Pre-Recorded Content
There is a massive trend on educational platforms toward "self-paced" or "pre-recorded" classes. Parents, steer clear of these for beginners. When a child is 6 or 7, coding is about the immediate "Why isn't it working?" moment. If they have to wait for an email response from an instructor to know why their cat sprite isn't moving, the momentum is dead. That interest? It’s gone.
Live instruction provides the feedback loop necessary to keep a child engaged. They need to hear, "Oh, you accidentally put the 'forever' block outside the movement command—that's a classic mistake, let's fix it." That’s gold.
Format Best For Feedback Speed Risk of Frustration Pre-recorded Video Advanced teens Slow/None High Group Live Class Social learners Moderate Medium 1:1 Live Instruction Ages 5-9/Beginners Instant LowThe 1:1 Advantage for Younger Kids
If you have a child on the younger end of the spectrum (ages 5-7), I cannot stress this enough: look for 1:1 tutoring. In a group of six kids, one kid will inevitably get stuck on a broken block, and the teacher will have to pause the whole class. The faster kids will get bored, and the slower kids will feel embarrassed. 1:1 allows the teacher to adapt the pace to the child’s brain. It’s an investment, but it’s the difference between a child loving coding and a child deciding they are "bad at computers."
How to Read Outschool Class Reviews
When you’re digging through outschool class reviews, don't just look for the five-star counts. Look for specific language. If a review says, "My son loved it, he had so much fun," that’s nice, but it doesn't tell you anything about the pedagogy.
Look for reviews that say things like:
- "The teacher helped my daughter fix a bug in her code rather than just fixing it for her." "He explained the concept of variables in a way my 8-year-old actually understood." "The teacher stayed a few minutes late to help my child finish their animation."
Those are the teachers you want. They respect the student's process.
The "Small First Project" Test: A Pro-Tip
Here is my secret weapon for vetting a teacher: Ask them, "What is the first thing my child will build?"
If they say, "We are going to build a platformer game like Mario," run away. That is a massive project that will take weeks and involve 15 different concepts. Your kid will get stuck, get overwhelmed, and quit.
If the teacher says, "We’re going to start with a simple timer or a basic animation of a cat walking across the screen," hire them immediately. They understand that success comes from small, "snap together" wins. Building a timer or a simple sprite animation teaches:
- The Green Flag start. Basic motion blocks. The concept of "Events" (when this happens, do that).
Final Thoughts: Don't Fall for the Hype
Avoid any teacher who promises "fast" results. Coding is a language, and learning a language takes time. It takes patience, and it takes the ability to sit with a bug for five minutes without screaming. If your teacher creates an environment where that "bug-hunting" is framed as a fun puzzle rather than a failure, you’ve found a winner.
Don't be afraid to message a teacher before you book. Ask them, "How do you handle it when a student gets stuck on a loop?" If they give you a clear, pedagogical answer, you're on the right track. Good luck, and keep those blocks snapping!