Kids Coding Milestones Ages 8-10: A Real Tutor's Checklist

Last updated: June 2026

Kids coding milestones for ages 8-10 are not a fixed timeline. They are a sequence of recognizable shifts in how a child thinks, builds, and recovers from mistakes. Across 200+ kids I have taught, the pattern is consistent enough to checklist, even though the speed varies wildly from one child to the next. What matters is the order, not the calendar.

This article gives you the actual checklist I use in my head when I assess a new 8, 9, or 10-year-old in our Discovery Call. By month, by quarter, by year. With clear red flags so you know when something is off and the kid needs a different approach, not just more time.

Key Takeaways

• An 8-year-old beginner should reach basic Scratch fluency (sprites, motion, simple events) inside the first 8 to 12 weeks of weekly lessons.
• A 9-year-old who has been coding for 6 months should be using if-statements meaningfully, not just dragging them in for show.
• A 10-year-old at the one-year mark is usually mid-Scratch with comfort, or starting to bridge into Python with Turtle graphics.
• The strongest milestone is not technical, it is recall. When a kid can walk in and explain what they built last week, in their own words, they have crossed a real line.
• The biggest red flag at any age is the kid finishing projects only when the tutor or parent is driving every click. If they cannot finish anything on their own attempt, the lessons are not landing.

Table of Contents

• How to read this checklist
• Age 8 milestones
• Age 9 milestones
• Age 10 milestones
• The full age 8 to 10 milestone table
• Red flags by age
• What schools and platforms get wrong about these milestones
• How to use this checklist as a parent
• Frequently Asked Questions

How to read this checklist

Two warnings before you start ticking boxes.

First, every milestone here assumes weekly 1-on-1 sessions of about 45 to 60 minutes, plus light at-home tinkering. Group classes and self-paced apps push every milestone back, sometimes by months, often by a year or more. That is not a sales pitch, it is what I see when I assess kids coming in from those backgrounds.

Second, kids are not numbers. An 8-year-old who is wildly into logic puzzles will hit 9-year-old milestones early. A 10-year-old who has been forced into coding without interest may sit at the 8-year-old line for half a year. The checklist below is a typical arc, not a contract. If your kid is six weeks off, that is normal. If they are six months off, something in the approach needs to change.

The order of the milestones matters more than the dates. A kid who skips comfort with sprites and jumps to if-statements will fall apart later. The sequence below is the one that holds.

Age 8 milestones

At 8, the realistic target is Scratch fluency. Not mastery. Fluency. Comfort with the canvas, the sprite library, motion blocks, basic events, and saving a project they made themselves.

Month 1 to 3 (the first quarter)

By the end of three months of weekly Scratch lessons, an 8-year-old should be able to:

• Open Scratch on their own and load a project they started last week
• Drag a sprite, change its costume, and move it across the stage with arrow keys
• Use the "when green flag clicked" event to start something
• Make a sprite say something with the "say" block
• Save and name a project without help

This is the foundation. It looks small. It is not. An 8-year-old who can do this five-step loop, open, build, save, reopen, modify, has the operational skills to learn anything else.

Month 4 to 6

The second quarter is when storytelling and animation appear. By month 6 an 8-year-old should be:

• Building a 2 to 4 sprite animated scene with dialogue
• Using "wait" blocks to control timing of events
• Switching costumes to create simple animation (walk cycles, mouth movement)
• Using sound blocks to add effects or music
• Showing pride in a finished project they can show a parent

The pride moment is a milestone, not a feeling. When an 8-year-old voluntarily calls a parent over to watch their project run, the work has stopped being a chore. That is the engagement milestone.

Month 6 to 12

In the back half of year one, an 8-year-old typically meets:

• Simple events and broadcasts (one sprite triggering another)
• Their first if-statement, usually around month 8 to 10, often around a touching or key-press check
• Variables for the first time, usually a score or a lives counter in a basic game
• A complete, playable mini-game like a chase, a catch, or a one-screen platformer

By age 9, a kid who started at 8 is usually somewhere in this back-half window. If they are still in month 1 to 3 territory at the one-year mark, the lessons are not working.

Age 9 milestones

Nine is a hinge age. Some kids are still building Scratch confidence, some are starting to ask harder logic questions, and a small group is ready to peek at Python. The milestones split based on whether the child has prior experience.

A 9-year-old beginner (zero prior coding)

Roughly the same arc as the 8-year-old, but compressed. A 9-year-old beginner usually moves through the early Scratch milestones in 2 to 4 months instead of 3 to 6. They tend to be more comfortable reading, which speeds up the "what does this block say" stage. By the 6-month mark they should be at where an 8-year-old gets at month 9 or 10.

A 9-year-old with 6 to 12 months of Scratch

This is where the meaningful 9-year-old milestones live. They should be:

• Using if-statements and if-else with intent, not just to copy a tutorial
• Building games with 3+ interacting sprites and a clear win/lose condition
• Handling at least one variable that changes over time (a score, a timer)
• Asking real "what if" questions: "what if I make it faster when you collect a power-up?"
• Recovering from broken projects without giving up

The recovery one is the milestone parents miss. Up until this point, when something breaks, most 8-year-olds either ask for help immediately or lose the thread. By 9, with experience, a kid should be willing to try one or two things before asking. That is the start of debugger thinking. In my 20 years teaching this age group, the 9-year-olds who learn to sit with a broken project for two minutes before raising a hand tend to be the ones who break into Python smoothly a year later.

A 9-year-old reaching for Python

A small group of 9-year-olds is genuinely ready to dip into Python. The signal is not boredom with Scratch. The signal is curiosity about logic itself. When a 9-year-old asks why the if-statement works, not just how to use it, they are showing what I call the spark. That is when text-based coding becomes possible.

A parent recently told me her 9-year-old daughter had been building Scratch games for six months. She had hit the point where she was asking, in her own words, "is there a way to do this where I do not have to drag blocks." That is the milestone. Not an age. A question.

Age 10 milestones

Ten is the most variable age in the entire 8 to 16 range. I have taught 10-year-olds who are still in the early Scratch quarter, and 10-year-olds who are halfway through a Python turtle curriculum. The milestone you measure them against depends on their experience, not the calendar year on their birthday.

A 10-year-old beginner

A 10-year-old starting from scratch (lower case s) usually compresses the entire 8-year-old year-one arc into about 6 months. They are old enough to read fluently, follow multi-step instructions, and remember what they did last week without a heavy reminder. They will not magically skip the early steps, the same dragging, the same green flag, but they will get through them faster.

A 10-year-old with one year of Scratch

By age 10 with a year of Scratch, the milestones to expect are:

• Comfortable multi-sprite game building with collisions, scoring, and lives
• Use of nested if-statements (an if inside another if)
• Use of loops with intent, not just "repeat 10 times" tutorial style
• The ability to plan a project before building it ("I want a game where...")
• Mid-project debugging, walking back through their code to find the issue

This is when the transition conversation starts. Some 10-year-olds will spend another full year deepening Scratch, building actual game projects, learning broadcasts, building cloning systems. Others are visibly outgrowing the block environment. There is no wrong answer.

A 10-year-old in Python territory

A 10-year-old in early Python should be:

• Comfortable with print, variables, and basic input
• Writing if-statements in Python syntax (the indentation usually clicks within a few sessions)
• Using basic for-loops to repeat actions a known number of times
• Building Turtle graphics projects (shapes, patterns, colors)
• Beginning to read error messages instead of just panicking at red text

The error-message milestone is huge. The first time a 10-year-old reads a Python error and identifies the line number, something clicks. They say "oh, I forgot the colon," and they have crossed into real programmer territory. That is a year-one Python milestone, not a year-three one.

The full age 8 to 10 milestone table

Milestone	Age 8 (typical)	Age 9 (typical)	Age 10 (typical)	What to look for	Red flag if missing
Open and save Scratch projects independently	Month 1 to 3	Month 1 to 2	Month 1	Kid loads last week's project without help	Still needing help at month 4+
First animated scene	Month 4 to 6	Month 2 to 4	Month 1 to 3	2+ sprites, dialogue, motion	Cannot independently move a sprite by month 4
First if-statement	Month 8 to 10	Month 4 to 6	Month 3 to 5	Used in a real game, not just copied	Avoids if-statements when offered
First variable	Month 10 to 12	Month 5 to 7	Month 4 to 6	A score or lives counter that updates	Cannot explain what the variable does
Complete mini-game	Month 10 to 12	Month 6 to 9	Month 6 to 9	Win/lose condition, multiple sprites	Never finishes anything start to end
Debugging attempt before asking	Year 2	Month 9 to 12	Month 6 to 9	Will try one fix before raising hand	Freezes at any error after 6+ months
First Python session	Age 10+	Age 10+	Month 12 to 18	Comfort with syntax in 2 to 4 sessions	Repeated syntax confusion after 8+ sessions
Reading Python errors	Year 2 of Python	Year 1 to 2 of Python	Year 1 of Python	Identifies line number, suggests fix	Panics at any red text after 3+ months

The most important column is the last one. If your kid is on the right track but slower than the typical column, that is fine. If your kid hits any red flag and stays there for more than a few weeks, the lessons need to change, not continue.

Red flags by age

These are the patterns I look for when a parent tells me their kid has been "doing coding" for a while but does not seem to be progressing. Each one is a sign that the format, the teacher, or the curriculum is the problem, not the kid.

At age 8, after 3+ months:

• Cannot independently open and reload a project
• Refuses to try anything without step-by-step instructions
• Does not voluntarily show a finished project to anyone

At age 9, after 6+ months:

• Drags if-statements in without being able to say what they do
• Has never built a project they came up with themselves
• Visibly dreads the lesson before it starts

At age 10, after 9+ months:

• Still in beginner Scratch territory with no signs of pushing past it
• Cannot recall what they built last week, even with prompting
• Switches between Scratch, Python, and other tools without depth in any

That last red flag is the one schools and group classes produce most often. A 10-year-old who has touched Scratch, Python, JavaScript, and Roblox in the same year usually has no real fluency in any of them. Depth beats breadth at this age. Always.

What schools and platforms get wrong about these milestones

Most kids coding curricula I have seen, including some well-known ones, treat milestones as a checklist to complete, not as signals to assess. A kid finishes "Module 4: Variables" and the platform moves them on, even if the kid still cannot explain what a variable is. The CSTA K-12 Computer Science Standards (csteachers.org) do a good job of describing what kids should know at each band. Even so, the gap between knowing the concept on a worksheet and using it in a project they care about is huge. Code.org's own research on K-5 computer science (code.org/research) consistently shows that conceptual exposure is not the same as durable skill.

Scratch's own educator guidance (scratch.mit.edu/educators) is more honest about this. It treats the platform as a creative tool, not a graded ladder. The MIT Lifelong Kindergarten group, which built Scratch, frames learning as project-based with iteration. That is exactly the pattern that produces durable milestones in real kids. The Scratch Foundation's own annual impact reporting (scratchfoundation.org) repeatedly emphasizes creative projects over completion metrics, which is the same reframe parents need.

The two patterns that produce real milestone progress in 8 to 10 year olds:

1. Weekly 1-on-1 sessions. The tutor can see if a milestone is actually internalized or just pattern-matched. Group classes cannot do this.
2. Project-based, not lesson-based. Kids hit milestones inside projects they care about. A worksheet about loops produces a kid who can do worksheets about loops. A platformer game that requires loops produces a kid who understands loops.

If your kid is in a program that does neither of these and is missing milestones, the program is the problem. Not the kid.

How to use this checklist as a parent

Three concrete uses for this list.

Use 1: Reality-check a tutor or program. Ask the tutor where your kid is on this checklist. A good tutor will pull up a recent project and walk you through specific milestones the kid has hit and which ones they are working on. A bad tutor will say "they are doing great" without specifics. The vagueness is the answer.

Use 2: Time the conversation about Python. Watch for the late-Scratch milestones: debugging, nested logic, planning before building. Once your 9 or 10 year old starts hitting those, it is worth talking to the tutor about Python readiness. Not before. For more on the exact signs, see Signs Your Child Is Ready for Coding Lessons and our deeper breakdown in What Should a 9-Year-Old Be Coding in 2026?.

Use 3: Spot stalls early. If your kid has been "doing coding" for six months and you cannot name any milestone above that they have hit, that is the signal. Either the format is wrong (often a self-paced app), the teacher is wrong (often a generalist), or the curriculum is wrong (often too theoretical). For a wider view on what kids actually build at this age, see Best Coding Projects for Kids Age 8-10. For the broader question of when to start, see What Age Should Kids Start Coding?.

Frequently Asked Questions

What coding milestones should an 8-year-old hit in the first year? An 8-year-old in weekly 1-on-1 Scratch lessons should reach independent project save/load by month 3, and animated scenes by month 6. By month 10 to 12, expect a first complete mini-game with an if-statement and variable. If a year passes and the kid still cannot build a simple project on their own, the program is not working.

Is my 9-year-old behind if they are still in Scratch? No. A 9-year-old who is genuinely fluent in Scratch (multi-sprite games, if-statements with intent, variables they can explain) is exactly where they should be. Switching to Python before that fluency is in place usually backfires. The strongest 10 and 11 year old Python students I have taught spent a full year or more in Scratch first.

When should a 10-year-old switch from Scratch to Python? When they show what I call the spark, real recall and logic comfort, not when they hit a specific number of hours. A 10-year-old who can plan a Scratch project before building it and debug their own code is usually ready. The clincher is when they ask "why does this work" instead of just "how." Some 10-year-olds get there at the 1-year mark. Some need 18 months. Both are normal.

What is a red flag in my 8 to 10 year old's coding progress? The biggest red flag is the kid finishing projects only when a tutor or parent is driving every click. By month 6 of weekly 1-on-1 lessons, an 8 to 10 year old should be able to make at least one independent change to a project on their own. If they cannot, the lessons are not landing. The format or teacher needs to change.

How long does it take a kid to learn coding well at this age? Real fluency in Scratch usually takes a full year of weekly 1-on-1 lessons. A real foundation in Python usually takes another full year on top of that. Programs that promise "your kid will build an app in 2 months" are not telling the truth. For a wider answer on timeline expectations, see How Long Does It Take a Kid to Learn Coding?.

Do these milestones apply to kids using Roblox or Minecraft to learn? Partly. Roblox Studio with Lua scripting hits some of the same logical milestones (variables, conditionals, loops), but the structure is incidental, not systematic. A child can spend a year in Roblox and hit none of the Scratch milestones on this list. Or they can hit many of them, depending on whether they are scripting or just building. For more on what game platforms actually teach, see Does Roblox or Minecraft Teach Real Coding?.

Related Articles

• Best Coding Projects for Kids Age 8-10, specific project ideas that align with the milestones in this checklist.
• Signs Your Child Is Ready for Coding Lessons, how to know when to start the clock on these milestones in the first place.
• What Should a 9-Year-Old Be Coding in 2026?, a deep dive into the 9-year-old milestones specifically.

The Bottom Line

Kids coding milestones for ages 8 to 10 are real, predictable, and assessable, but only if you watch for the right signals. Order beats speed. Recall beats coverage. And no milestone in this checklist will hit reliably if the kid is in the wrong format or with the wrong teacher.

Wondering exactly where your 8, 9, or 10 year old falls on this checklist? Book a free Discovery Call and we will walk through their current projects together and map the right next milestone for them.