Interview Template: Questions to Ask a Coding Tutor or AI Coach Before You Hire

Why this interview matters (and what “good” looks like)

Hiring a tutor can feel like choosing a teammate for your child’s future. The right coach doesn’t just “teach code”—they build confidence, problem-solving habits, and the kind of curiosity that makes kids want to keep going when things get tricky.

If you’re searching for questions to ask a coding tutor, here’s the goal of the interview:

• Confirm they can teach at your child’s level (not just their own).
• Ensure they’re safe, reliable, and structured.
• See how they handle frustration, motivation, and mistakes.
• For older learners, check whether they can be a thoughtful AI tutor for teens—someone who teaches responsible AI use, not just shortcuts.

A great session should look like this:

• Your child talks more than the tutor.
• The tutor asks guiding questions instead of grabbing the keyboard.
• The lesson ends with something finished (even small) and one clear next goal.

Below is a practical coding coach interview checklist you can copy into notes and use right away.

The interview template: questions to ask (with what to listen for)

Use these questions in a 20–30 minute call. You don’t need to ask all of them—pick the ones that match your child’s age and goals.

1) Fit, experience, and teaching style

• “Who do you typically teach (ages/levels)?”
  • Listen for: clear examples (e.g., “8–10 beginners in Scratch,” “middle school Python,” “teens building portfolios”).
• “How do you explain a hard concept to a 9-year-old vs. a 15-year-old?”
  • Listen for: different strategies, not the same explanation with bigger words.
• “What’s your approach when a student is stuck?”
  • Look for: hints, debugging habits, asking the student to predict what will happen.
• “How do you keep sessions engaging without turning it into pure entertainment?”
  • Strong answer: project-based learning with structure (mini-goals, checkpoints).
• “What does a typical first month look like?”
  • Best: an assessment + a plan, not “we’ll see what happens.”

2) Curriculum, projects, and outcomes

These questions help with how to choose a programming tutor for kids who will actually move your child forward.

• “What projects would you recommend for my child in the first 4–6 lessons?”
  • Listen for: age-appropriate projects (games, animations, simple apps, data projects) and why those choices fit.
• “How do you balance fundamentals with projects?”
  • Strong: fundamentals taught inside projects (variables inside a game score, loops inside animations).
• “How do you measure progress?”
  • Look for: skill checklists, milestone demos, small assessments, and reflection (“What did you change and why?”).
• “Do you provide homework or practice?”
  • Good: optional, short, and specific (10–20 minutes, clear goal).
• “Can you share an example of a student outcome after 3 months?”
  • Best: a portfolio link, repo, or demo (with permission), plus what the student learned.

3) Tools, safety, and parent communication

A tutor may be wonderful technically and still be a poor fit if logistics are messy. Ask:

• “Which platforms and tools do you use, and why?”
  • Kids: Scratch, MakeCode, Roblox Studio (with clear guardrails), beginner web tools.
  • Teens: Python, JavaScript, HTML/CSS, GitHub, Replit/VS Code.
• “How do you handle online safety and student privacy?”
  • Look for: no sharing personal info, careful use of community platforms, parental visibility, secure communication.
• “How will I know what my child did each week?”
  • Ideal: short weekly notes + a link to the project or a quick summary.
• “What’s your cancellation/rescheduling policy?”
  • You want: clear boundaries and consistency.
• “Do you require a parent nearby for younger kids?”
  • Strong tutors set expectations (especially ages 5–8).

4) AI-specific questions (especially for teens)

If you’re hiring an AI tutor for teens or a coach who uses AI tools, ask directly how they handle it. You’re not trying to ban AI—you’re trying to make it educational.

• “How do you teach students to use AI tools responsibly?”
  • Look for: verifying outputs, citing sources, understanding limitations, and not treating AI as an answer machine.
• “When is it okay for a student to use ChatGPT/Copilot, and when is it not?”
  • Strong: use it for hints, debugging, explanations; avoid copying solutions before attempting.
• “How do you prevent ‘AI dependence’?”
  • Best: require the student to explain the code, modify it, and predict behavior.
• “Do you cover AI basics like data, bias, and model limits?”
  • Good: age-appropriate conversations, not a graduate lecture.
• “Can you help build an AI-related portfolio project?”
  • Great examples: a simple image classifier demo, sentiment analysis, a “smart” study helper with clear ethical boundaries.

A simple scoring checklist you can use while interviewing

It’s hard to compare tutors based on vibes alone. Use this quick rubric to score each candidate from 1 (weak) to 5 (excellent). Then add notes.

Category	What “5/5” sounds like	Score (1–5)	Notes
Age/level fit	Teaches your child’s exact level regularly; gives examples
Teaching approach	Guides with questions; uses mistakes as learning
Structure & plan	First-month roadmap + milestones + flexibility
Project quality	Projects are fun and skill-building; clear outcomes
Communication	Weekly summaries, clear expectations, responsive
Safety & professionalism	Privacy-aware, boundaries, policies are clear
AI responsibility (if relevant)	Teaches verification, ethics, and independence
Motivation & mindset	Uses growth mindset; keeps kids engaged without pressure

Tip: After the interview, write a one-sentence summary like: “This tutor seems best for ___ because ___.” If you can’t fill that in, keep looking.

Red flags (and green flags) parents can spot quickly

Even with the right questions, you’ll want to notice patterns.

Green flags

• They ask about your child’s interests (games, art, robotics, sports) and use that to shape projects.
• They describe debugging as a normal, teachable skill—not a failure.
• They can explain concepts simply (loops, variables, functions) without talking down.
• They welcome parent check-ins but keep the student in charge.
• They show you what success looks like: demos, portfolios, milestones.

Red flags

• They promise unrealistic results (“Your child will be advanced in two weeks”).
• They do most of the talking and don’t ask about your child.
• They rely on copy-paste solutions or encourage heavy AI use without understanding.
• They can’t describe how they handle frustration, distractions, or motivation.
• They avoid clear policies (payments, cancellations, communication).

If you hear a red flag, you don’t need to “prove” it. Tutoring is personal—move on.

Next steps: how to choose the best tutor after the call

Once you’ve done 2–3 interviews, here’s a practical way to decide.

• Ask for a trial lesson with a clear goal.
  • Example goal: “Build a mini-game with a score and one bug to debug together.”
• Watch for the right struggle.
  • The best tutors let kids think. If your child never struggles, it may be too easy; if they’re overwhelmed, it’s too hard.
• Request a simple learning plan.
  • Ask: “What are 3 skills you’ll target in the next 4 weeks?”
• Set a communication rhythm.
  • A weekly note is often enough: what they built, what they learned, what’s next.
• Re-evaluate after 4 sessions.
  • Use three questions:
    • Does my child feel more confident?
    • Can they explain what they made?
    • Are they building momentum (even if slowly)?

If you want extra structure, consider pairing tutoring with a guided learning platform that reinforces skills between sessions. At Intellect Council, many families use lessons and quests for practice, then use coaching time for deeper projects, debugging, and confidence-building.

Bring this interview template to your next call, score each tutor, and trust the data and your child’s experience. The right coach should make learning feel achievable—and exciting—one session at a time.