You have 10–15 minutes. Most teams waste half on one topic and half the team never speaks. This guide teaches you to run it as a conversation — and send every member home knowing what they did right.
This is the most important idea in this guide. Teams with a memorized speech usually score lower than teams ready to talk. A judge is not your audience — they are a curious engineer asking questions. Respond to what they actually ask, not to what you planned to say.
The Innovate Award recognizes a creative, novel design solution. It is not automatically considered — your team must submit a written form included in your engineering notebook. Here is exactly what that requires and how to do it well.
The strongest submissions are usually not the robot’s primary mechanism — they are the clever solution to a secondary problem that most teams solved poorly or ignored entirely. Ask: what does your robot do that makes other engineers say “how did you do that?” That’s your candidate.
Before every competition, agree on who speaks first for each category. Saves awkward pauses in the actual interview.
Intellectual honesty scores higher than a confident wrong answer.
Open it at the start. Hand it to the judge. Then use it actively:
“The game required scoring blocks from the center reliably — our problem statement. We brainstormed three intake approaches and used a decision matrix to choose rollers based on cycle speed and jam rate. Our first design had 15% jam rate on tilted elements — page 12. We increased roller gap 4mm, brought it below 3%, and held that for 8 sessions.”
That answer covers: problem → brainstorm → selection criterion → test result → specific change → verification. Rubric categories 1, 2, 3, 5, and 6.
Before competition, know: what specific situation your robot targets, the expected point value, and how your mechanism choice reflects the scoring math. See Game Analysis.
Know your autonomous consistency (n=10, %), your mechanism’s key metric, and one specific change made from data with its before/after result. See Testing, Data & Iteration.
Every strong answer has all three. Every weak answer is missing at least one.
Judges notice immediately. If the team lead carries the whole interview, judges assume the others do not understand the work.
Teams describing what the robot does run out of time for process, iteration, and STEM categories.
A memorized speech survives until the first unexpected follow-up. Then the team freezes.
“We ran 10 tests” when the notebook shows 3. Judges read the notebook at the same time you are talking.
When students use vocabulary that clearly is not theirs, judges notice. Follow-up questions expose it immediately.
Set the length and press start. The phase label tracks which category you should be on.
One person reads these aloud. Everyone else answers. Rotate who answers each one.
Every question below has 8–12 different phrasings. The randomizer picks a different wording each time — so your team practices answering the idea, not memorizing a script.
Rate your team. 1 = never discussed. 5 = we have data, page references, and can handle any follow-up.