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.
Spartan practice: Recall your own work, decisions, failures, learning, and collaboration. These questions and examples are prompts, not a speech to memorize or a required question order. Use real evidence, acknowledge uncertainty, and let the students involved explain their contributions. See the current interview rubric guide and student-centered policy guidance.
This is the most important idea in this guide. Prepare to talk about your work and respond to follow-up questions. 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.
Use this planner to remember who worked on each topic. These are starting points for practice, not exclusive speaking roles or a required presentation order.
Say what you know, what you are uncertain about, and who or which record could clarify it.
If your notebook is available, consult it when it helps you explain or recall evidence:
“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.
Example analysis: notice which details explain the reasoning. Do not memorize these sentences or borrow the measurements. Use your own experience, and include real teamwork and individual contributions where relevant.
Use this optional framework when it fits the question. A short factual answer, an honest uncertainty, or a teamwork example may need a different structure.
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.
Practice listening across all six criteria: 0 = Not Yet Heard; 1 = Heard; 2 = Heard, with Specifics. This is a practice observation, not a predicted official score. Identify one real experience to clarify next.