What I learned mentoring a global AI hackathon
I've won 10+ hackathons from the competitor's chair. Anthropic picked me as a Claude Community Mentor — one of a handful from India — for the Build with Opus 4.7 hackathon. From the other side of the table, one gap was obvious.
I've entered 15+ hackathons and won 10. I know the competitor's chair — the caffeine, the last-hour panic, the demo barely holding together as the judges walk up.
This time I was on the other side. Anthropic selected me as a Claude Community Mentor for the Build with Opus 4.7 hackathon — one of a handful from India. For once I wasn't competing. I was watching people build.
You see the gap from the mentor's chair
As a competitor you only ever see your own project. As a mentor you see dozens side by side, and one gap jumps out immediately: the distance between people who prompt and people who build systems.
Prompters treat the model like a magic 8-ball. Ask, hope, paste, repeat. When it fails, they ask again — louder and more frustrated, as if volume were the missing input.
The winners treated the model like a teammate
Clear role, clear inputs, clear definition of done — a teammate with a job description. The winning teams didn't hope for good output; they engineered the conditions that make good output likely.
Same model. Same week. Wildly different results. The delta wasn't the AI — it was how they thought about the AI: a system to design around, not a slot machine to pull.
Prompting is not building
Prompting is a skill. Building systems is a discipline. One gets you a cool demo; the other gets you something that survives contact with reality.
The best teams broke the problem down, gave the model a bounded job, verified its output, and composed the pieces into something real. That's engineering. The prompt was the smallest part of the work — and the part everyone else was obsessing over.
Teaching is how I actually understand things
I've delivered 20+ workshops and run training sessions constantly — not a side hustle, a core part of who I am. Mentoring reminded me why.
You don't really understand something until you can transfer it. Explaining the system-versus-prompt gap to a stuck team forced me to name things I'd done on pure instinct for years. Teaching sharpens the teacher more than the student.
Build, learn, teach, repeat — that's my loop. This hackathon was all three in one week. Honestly, I took more from mentoring it than from most of the ones I won.