What Teaching Robotics Taught Me About Engineering

Alongside writing software early in my career, I spent time as a robotics instructor. I expected it to be a break from engineering. Instead it turned out to be some of the most useful engineering training I’ve had — because nothing exposes shaky understanding faster than trying to explain it to a beginner.

The unexpected lesson: if you can’t explain it, you don’t understand it

Teaching robotics means taking something with many moving parts — sensors, motors, logic, the messy physical world — and making it land for someone who’s never seen it. You can’t hide behind jargon. Every time a student looked confused, it was usually because my mental model had a gap I’d been papering over. Teaching forced me to actually understand the things I thought I knew.

Debugging is a mindset, and robotics teaches it raw

Software bugs are abstract; a robot that won’t move is right there refusing to work. Is it the code, the wiring, the sensor, the battery, the physical world? Teaching beginners to isolate variables and test one thing at a time — instead of changing five things and hoping — is exactly the debugging discipline that makes you effective in software. The feedback loop is just more honest with hardware.

Communication is a core engineering skill

The habit of meeting someone at their level, checking for understanding, and adjusting my explanation didn’t stay in the classroom. It’s the same skill I now use in code review, in design discussions, and in leading teams — translating between people who hold different pieces of the picture.

What I took away

• Explaining something is the real test of understanding it.
• Systematic debugging beats guessing — and robotics makes that visceral.
• Communication is engineering, not a soft add-on. The best technical work is worth little if you can’t bring others along.

Takeaways

Teaching robotics looked like a detour, but it sharpened the exact skills — clarity, debugging discipline, communication — that I’ve leaned on at every step since. Years later, leading backend teams, I realised I’d been practising for it in a room full of curious kids and stubborn robots.