Why the Best Kids Coding Tutors Build Around Interests

Last updated: June 2026

The best kids coding tutors build lessons around your kid's obsessions, not around a curriculum binder. The difference between a curriculum-first tutor and an interest-first tutor is the difference between a kid who endures their weekly lesson and a kid who looks forward to it all week. After 20+ years of teaching kids and training other tutors to do the same, this is the single trait I tell parents to screen for above all others.

Specifically, this article gives you the exact questions to ask a prospective tutor, the answers that reveal an interest-first approach, and the warning signs of a curriculum-first one. It is the evaluation guide I would hand a friend who was hiring a tutor for their kid.

Key Takeaways

• Interest-first tutors customize the example every session based on what the kid is into that week. Curriculum-first tutors run the same examples for every kid.
• 4 questions are enough to tell which kind of tutor you are talking to in a Discovery Call.
• Interest-first tutoring is not "soft" or "fun-only." It teaches the same concepts. It just uses better wrapping for the specific kid.
• The biggest tell of a curriculum-first tutor is the answer "we follow our proven X-week program." Real personalization does not run on a binder.
• This is the trait I explicitly train my own tutors on. It is the single highest predictor of whether a kid sticks with coding past year one.

Table of Contents

• The two kinds of kids coding tutors
• Curriculum-first vs interest-first: the comparison
• 4 questions to ask any prospective tutor
• Warning signs to walk away from
• What interest-first tutoring actually looks like in a session
• Why I train my own tutors on this explicitly
• Frequently Asked Questions

The two kinds of kids coding tutors

There are roughly two species of kids coding tutor on the market today. They both have credentials. They both have polished websites. They both teach Scratch and Python. The difference is structural, and it shows up in the first session.

Curriculum-first tutors start with a curriculum. The curriculum has lessons. The lessons have examples. The examples are the same for every kid. Essentially, the tutor's job is to walk the kid through the lessons in order. If your kid is bored or confused or visibly disengaged, the tutor's response is usually to slow down or speed up the same material. They rarely change what the material is about. The lesson plan is the boss.

Interest-first tutors start with the kid. They spend the first 5 minutes of every session finding out what the kid is into right now, this week. Then they pick the concept the kid needs to learn next and wrap it in that interest. For example, a kid into Pokemon learns variables through pokemon_health. A kid into Stranger Things learns loops by iterating through the kids in the party. The concept is the same. The wrapping is custom. The kid is the boss.

Both types of tutors can teach a kid Python. Only one type produces a kid who is still coding two years later, of their own volition.

Curriculum-first vs interest-first: the comparison

Trait	Curriculum-first tutor	Interest-first tutor
First-session pattern	Asks kid's age, dives into Module 1	Asks what kid is into, picks first project around it
Example variables	car, age, temp (textbook defaults)	pokemon, wand, score (kid-specific)
When kid disengages	Slows down or repeats same material	Changes the example to something more compelling
Response to kid's "I want to build X"	"We will get there in module 6"	"Let us start that next session"
Lesson preparation	Same prep for every kid	Custom prep per kid per week
Visible to parents	Polished, predictable, repeatable	Looks improvised; is actually highly intentional
Cost to tutor's time	Low (one prep, many kids)	High (custom prep per kid per session)
Risk if tutor is mediocre	Kid is bored but at least covers material	Kid is hooked but might cover material out of order
Long-term outcome	Kid completes curriculum, drops coding	Kid keeps coding past the lessons

The cost column matters. Interest-first tutoring is more work per session, which is why most platforms and group classes do not do it. They cannot afford to. However, a 1-on-1 tutor working with 10 kids can. That is one of the structural advantages of 1-on-1 over group classes. See Group Classes vs 1-on-1 Tutoring for Coding for the wider picture.

4 questions to ask any prospective tutor

These are the four questions I tell parents to ask in a Discovery Call. The answers will sort tutors into the two groups above within about 5 minutes.

Question 1: "How do you start the first session with a new kid?"

• Curriculum-first answer: "We do an assessment and place them in our framework, then start with the first module."
• Interest-first answer: "I ask what they are into and build the first project around it. The assessment happens by watching them work, not by quizzing them."

The word "framework" is a flag. Frameworks are made to be followed, not bent.

Question 2: "Tell me about a kid you taught recently. What were you doing in your last session with them?"

• Curriculum-first answer: A generic description of a concept (loops, conditionals, functions).
• Interest-first answer: A specific story with the kid's interest in it. "Last session I had a 10-year-old who is really into Minecraft, so we built a Python program that calculates how many blocks you need to build different structures."

You are listening for specificity. A curriculum-first tutor cannot give you specifics because every session looks like every other session.

Question 3: "What do you do if my kid loses interest mid-session?"

• Curriculum-first answer: "We have engagement techniques, breaks, games, etc."
• Interest-first answer: "I change what we are working on, mid-session if I need to. If the concept is not landing because the example is dull, I swap the example. The concept stays the same."

The first answer treats disengagement as a behavior to manage. The second treats it as feedback to act on.

Question 4: "How do you know what each kid is interested in?"

• Curriculum-first answer: "We have an intake form."
• Interest-first answer: "I ask at the start of every session. Kids' obsessions change every few weeks at this age. The intake form goes stale fast."

The intake form answer is the killer. Static information about a kid will not produce interest-first lessons over months and years. The asking has to be continuous.

For more on the broader tutor-selection process, see How to Choose the Right Coding Tutor for Your Child.

Warning signs to walk away from

A few patterns are nearly always disqualifying for me when I help parents vet a tutor.

"We have a proven X-week program." No real personalization runs on a fixed-length program. A proven program is a sales line. A real tutor's program length depends on the kid.

Every kid builds the same first project. Ask: "What is the first project most kids build with you?" If the answer is one specific project (always a calculator, always a guessing game), it is curriculum-first. Different kids should build different first projects.

The tutor cannot name a kid they taught recently and what that kid was into. Anonymized is fine. Specific is required. "A Pokemon-obsessed 9-year-old" or "a basketball kid who wanted to track stats" is the right level of detail. "We have kids of all ages" is the wrong level.

The tutor never asks about your kid in the Discovery Call. This is the biggest one. Imagine 30 minutes of a Discovery Call go by and you have heard about the tutor's qualifications, the curriculum, the pricing, and the schedule. If the tutor has not asked you a single question about what your kid is into, that tutor is not going to ask your kid either.

For the bigger picture on whether 1-on-1 is even the right format, see Is 1-on-1 Coding Tutoring Worth It?.

What interest-first tutoring actually looks like in a session

A composite of how an interest-first first session usually runs in my practice.

Minute 0 to 5. Tutor asks the kid what they have been doing this week, what they are watching, what game they are into right now. Not as small talk. As intake. The tutor is taking notes.

Minute 5 to 15. Tutor pulls up Scratch or Python and says: "I want to show you something." They build a tiny working example, two or three minutes of code, that does something connected to the kid's interest. A sprite of the kid's favorite character. A Python program that prints a quote from the kid's favorite show. The point is not the example. The point is the visible "this is about me" moment.

Minute 15 to 35. The actual lesson. Same concept the curriculum would teach (variables, conditionals, whatever). But every example is wrapped in the kid's interest. The tutor is teaching the concept properly. They are just using the kid's nouns.

Minute 35 to 45. The kid builds something themselves. Tutor watches and intervenes minimally. The thing the kid builds is in the kid's interest space.

Minute 45 to 50. Tutor asks what the kid wants to build next. The kid's answer determines half of the next session's lesson plan. This is the loop that compounds, and it is what curriculum-first tutoring cannot replicate.

Anthony, a parent of a 12-year-old learning Python, summed up what made our sessions different. He said the best part was being shown something, then being let try it before having it re-explained. Unlike group lessons where you just copy, this method makes things click. The "letting you try" only works when the thing you are trying is something you care about. That is interest-first in practice.

For more on the deeper pedagogy, see The 30-Second Trick That Makes Kids Care About Code. For what 30 sessions of this approach actually looks like over months, see What 30 Sessions of 1-on-1 Coding Actually Look Like for a Kid.

Why I train my own tutors on this explicitly

When I bring on a new tutor for my own program, this is the first thing I train them on. Not the curriculum. Not the schedule. The interest-first reflex.

Specifically, I train them to:

1. Open every session with a real question about the kid's week, not as ritual but as data collection.
2. Keep a running note per kid of current obsessions, updated every session.
3. Substitute kid-specific variable names and example domains in every new concept they teach.
4. If a kid is disengaged for more than 5 minutes, change what the lesson is about, not how it is being delivered.
5. Plan each kid's next session based on what they said at the end of the last one, not based on a master schedule.

This is the most expensive part of running my tutoring service in tutor-time terms. It is also the highest-leverage. Additionally, research from the MIT Lifelong Kindergarten group's foundational work on creative learning (scratch.mit.edu/research) consistently identifies "passion projects" as the strongest predictor of sustained engagement in kids. The interest-first approach is the operational expression of that finding.

The kids who stick with coding for years are the kids whose tutors did this. It is not optional. It is the job.

Frequently Asked Questions

Do interest-first tutors still cover the same coding concepts as curriculum-first ones? Yes, fully. The concepts are identical: variables, conditionals, loops, functions, data structures, debugging. Interest-first tutors teach all of them. The difference is the wrapping. A kid learns if-statements equally well whether the example is if temperature > 30 or if Harry > Voldemort. The second one just produces a kid who actually pays attention.

Is interest-first tutoring just "fun coding" without rigor? No. Interest-first is more rigorous, not less, because the kid is actually engaged with the material. A kid bored by a generic example will pattern-match without understanding. A kid hooked by a personalized example will internalize the concept. The rigor comes from internalization, not from how dry the material is.

My kid's interests change constantly. Does this still work? Yes, it works better, because the tutor is asking at the start of every session anyway. A kid who was obsessed with Roblox last month and obsessed with anime this month is normal. The tutor's job is to update the wrapping. The concepts they are teaching do not change.

How do I know if my current tutor is interest-first or curriculum-first? Ask your kid one question: "What did you and your tutor work on last week, and what was it about?" An interest-first tutor produces an answer like "we made a Pokemon battle simulator." A curriculum-first tutor produces an answer like "I think we did variables?" The specificity of the answer is the test.

Related Articles

• How to Choose the Right Coding Tutor for Your Child, the full tutor-selection guide.
• Is 1-on-1 Coding Tutoring Worth It?, why personalization at this level requires 1-on-1.
• The 30-Second Trick That Makes Kids Care About Code, the parent-applicable version of this pedagogy.

The Bottom Line

The best kids coding tutors build lessons around your kid's obsessions because that is what produces kids who are still coding two years later. Everything else, the credentials, the curriculum, the platform, matters less than this single trait. If a tutor cannot personalize the example to your kid this week, every week, find a different tutor.

Have you ever screened a tutor for this specifically? Book a free Discovery Call and we will start by asking what your kid is into right now, then map a first project that fits.