What age should a child start learning to code?

It's the question we hear most often, even before questions about price or curriculum: "What age can my child start programming?" The short answer is from age 7. The longer, more useful answer is that age matters less than how the subject is introduced.

What really matters: teaching approach, not age

A 7-year-old discovering code with Scratch — a visual language where you assemble colourful blocks instead of typing text — doesn't need to type fast or understand algebra. They need curiosity, a bit of patience, and an adult who adapts the pace to their attention span rather than the other way around.

This is where a lot of generic resources found online fail: a course designed for a 14-year-old teenager will bore or discourage an 8-year-old, even if it's "technically" within reach. The reverse is also true: a teenager kept too long on very simple Scratch blocks eventually loses the interest they started with. See our article Scratch vs Python, what's the difference to understand why they aren't two levels of the same tool, but two stages of the same path.

What about before age 7 — is anything really possible?

That's the question that almost always follows, especially from parents of very curious 5 or 6-year-olds. The honest answer: technically, some tools exist for that age (screen-free programmable toys, very simplified apps), but we set our threshold at 7 for a specific reason, not an arbitrary one. Below that, reading is usually not yet fluent enough to follow on-screen instructions independently, and the ability to concentrate on a structured task for several dozen minutes still varies a lot from child to child. A poorly calibrated course at that age is less likely to bore than to create a frustrating first experience with computers — the opposite of the goal. A very advanced 6-year-old can sometimes start a bit earlier; that's exactly the kind of case a free trial lesson can honestly evaluate rather than guessing from a distance.

The main stages, by age group

• 7-9 years old: discovery with Scratch. The child learns basic logic (loops, conditions, events) by creating their own games and animations. The goal at this age isn't code rigor but the joy of seeing a character move because you "gave it an order". A typical session alternates a short explanation (5-10 minutes) with a much longer guided, hands-on time — the child stays active, never just a spectator of a demo.
• 9-11 years old: a gentle transition to text-based code, often via Python Turtle, which keeps an immediate visual result (drawing shapes, patterns) while introducing real syntax. This is the age when most children start wanting to "write real code", motivated by the idea of no longer doing things "like in kindergarten".
• 11 years and up: "pure" Python programming, with more ambitious projects — small games, calculators, simple automations. This is also the age when some children start getting curious about how the internet works, how the apps they use are built, or about artificial intelligence. See Python for kids, where to start for the full step-by-step progression.

These milestones are indicative, not rigid: we have 10-year-olds very comfortable in Python and 12-year-olds who still prefer to consolidate the basics in Scratch before moving on. This is precisely why our classes are one-on-one or in small groups (Solo and Duo plans), rather than following a uniform school-style curriculum.

Does a child need to already be "good at maths"?

No. This is probably the most common misconception among parents, and one of the least accurate. Programming develops logic, it doesn't require an advanced level of it beforehand. Many children actually discover logical reasoning and problem decomposition through code, before encountering it later in maths class — not the other way around.

What genuinely helps, at any age, is a patient teacher, a pace that leaves room to understand rather than just keep up, and the ability to ask questions without feeling judged. That's why our teachers are trained in a pedagogical method designed by EPFL and ETHZ engineers, built specifically for children rather than adults.

Signs it might be worth waiting a little longer

On the other hand, some signals honestly suggest waiting a few months rather than forcing the start: a child who shows genuine reluctance toward screens in general (not just apprehension about something new), an already busy school period full of other changes (start of year, moving house, new school) where adding a structured activity mostly adds pressure, or simply a complete lack of spontaneous curiosity despite several opportunities to bring it up at home. These aren't definitive red flags — just signs that waiting a term or two rarely costs anything, while a failed first experience can leave a longer mark than expected on a child's relationship with computers.

How do you know if the time has come?

Three signals are usually enough:

1. Your child asks questions about "how it works" (a video game, an app, a website).
2. They enjoy building, assembling, solving small problems (Lego, puzzles, logic games).
3. They want to try — even without knowing exactly what "programming" means.

If even one of these signals is present, that's usually enough to try a first session. That's exactly why we offer a free trial lesson of 30 minutes: if it's not the right moment or the right approach for your child, you'll know before enrolling.

Frequently asked questions about starting age

My child is older (13-14) and has never coded — is it too late? Not at all. The order of the steps matters more than the age at which you go through them: an older beginner usually moves through Scratch faster (a few sessions rather than several months) before joining Python, but rarely skips the basics without frustration.

Does my child need to already read well? Fluent reading helps, but isn't a strict requirement from age 7-8 — most of Scratch's vocabulary is visual (coloured blocks, icons), and the teacher covers the rest verbally.

Can two children of different ages take the same class? Yes, in the Duo plan, as long as their starting level is close — it's the dynamic between them that matters, not their age gap as such.

And if your child prefers a more intensive, one-off format, our holiday camps are often an excellent entry point: one week to try it out, with no long-term commitment.