What a mentor actually does in the room

Parents ask what the mentors do less often than you'd think, and it's a question we wish came up more, because the honest answer doesn't match what most people picture when they hear "instructor."

A mentor is not lecturing. There's no whiteboard, no slide deck, no "today we're learning loops." A mentor is also not a babysitter, watching from the side while kids entertain themselves. The actual job sits in a narrower, less obvious space between those two, and it's the hardest role in the building to do well.

The main skill is knowing when not to help

This is the part that surprises people. The single most-used skill a mentor has isn't explaining something — it's recognizing the moment a kid is stuck in a way that's productive, and staying out of it.

A kid's object detector keeps misidentifying a coffee mug as a bowl. The instinct of almost every well-meaning adult is to walk over and fix it. A mentor's job is to resist that instinct, because the ten minutes that kid spends annoyed and reasoning through why the model is wrong — bad lighting, an unfamiliar angle, training data that never saw this exact mug — teaches more about how machine learning actually behaves than a mentor's explanation would in a tenth of the time. We've written about this specific example before. It generalizes past robotics: a story that isn't landing, code that won't compile, a trailer script that's flat. The fix is rarely to fix it for them.

The second skill is knowing when a mentor genuinely is needed

Staying out of the way isn't the same as being absent. There's a real difference between a kid who's productively stuck — wrestling with a problem that's teaching them something — and a kid who's just stalled, spinning on something they don't have the tool to get past on their own. A mentor watching six kids at once has to tell those two states apart in real time, for each kid, continuously. That's the actual craft. Anyone can hover uselessly or intervene too fast; doing neither, consistently, across a room of different kids at different points in different projects, is what separates a mentor from either extreme.

What that looks like practically

In an hour, a mentor might: sit down next to a kid for ninety seconds and ask one question that reframes the problem, then leave; stop a different kid from giving up on a genuinely broken setup that has nothing to teach them by fixing the actual bug; notice a third kid has gone quiet in a way that isn't focus, it's discouragement, and go find out which; and spend most of the remaining time watching, not talking. The room looks unstructured from the outside. It isn't. The mentor is the structure — it's just invisible, because it mostly shows up as restraint.

Why this is harder to hire for than it sounds

"Knows the material" is easy to screen for. "Knows when to shut up" is not, and it's the rarer trait. Someone who's genuinely excellent at a subject often struggles the most here, because the instinct to demonstrate expertise — to jump in with the answer — is exactly the instinct the job requires suppressing, over and over, for kids who are not going to thank them for it in the moment.

If you've watched a session and it looked like "not much happened, the mentor mostly just walked around" — that's usually the job going well, not the job going undone.