The interview is an opportunity for judges to better understand your project, your learning process, and the teamwork behind your performance. During the interview the Judges will be asking the teams questions and the teams will have the opportunity to demonstrate and explain their robots. Judges are not only evaluating the robot itself, but also how the team prepared for the competition, how well each member understands the project, and what was learned throughout the experience.
See 6.1 of the OnStage rules 2026 and the OnStage Score Sheets for the Technical Interview 2026.
1. Before the Interview: Know Your Story 👀
Judges are not only evaluating the robot — they are ALSO evaluating how you prepare for the competition, how well you understand what you built, and what you have learned through the experience. The judges are not expecting teams to prepare formal presentation slides or follow a scripted presentation. The interview will be conducted as a question-and-answer conversation with the team.
Before the interview, make sure your team can clearly explain:
Why you have chosen this solution
How it works — how you programmed the software and how you built the hardware. Be ready to mention either how you designed the PCB board or why you chose any electronic module
What challenges you faced and how you solved/overcome them
How teamwork contributed to the development of the project (What was the work division? - - What role each person had?).
If you can explain it, you understand it.
Each team member should understand not only their own role, but also the contributions of the other members and how the different parts of the project connect together. If you can clearly explain your project, it demonstrates a strong understanding of what you built.
It is also recommended that teams document the evolution of the project, from the initial ideas to the implementation phases, including testing, adjustments, and problem-solving throughout the development process.
2. Preparing for your Interview 🎙
Teams should be prepared to demonstrate their robots and explain features in practice during the interview, including the live demonstration of selected features. Before you enter the interview room make sure that all robots, controllers, and props to be displayed are fully functional.. Check batteries, sensors, communication systems, and moving parts shortly before the interview to ensure everything is operating properly. Bring evidence of your software and be prepared to show the software environments and your code.
Do your team have the following ready?
☐ All robots are fully functional
☐ Batteries are fully charged
☐ Sensors are working properly
☐ Communication systems are connected and stable
☐ Motors and moving parts are functioning correctly
☐ Controllers are working
☐ Props and stage elements are prepared and functional
☐ Team laptops/computers are charged and available
☐ The latest version of the source code is accessible on the computer
☐ Team members are prepared to explain the programming logic and algorithms used
☐ Backup files or copies of the code are saved and organized
☐ Required software and drivers are installed and working properly
☐ Code and design diagrams are open on the laptop
3. During the Interview: Share Your Story 🎞
During the technical interview, the judges will ask a variety of questions. The team should be able to share your story clearly, responding to the following points. Rather than simply describing the technical aspects of the performance, they should communicate the team’s journey.
3.1. Technical Skills (Software & Programming)
What judges are looking for:
They want to see that the team understands their project including the choices of the language, design, and code, not just that it works. And how and why the team made those choices for the project.
Simple tips:
Explain why you have chosen the programming language (e.g., Python, C++, blocks).
Describe how the code is organized (e.g., functions, modules, comments).
Talk about how you optimized performance (e.g., speed, accuracy, reliability).
If you used libraries, datasets, or models: say what they do and why you used or adapted them.
Mention if you used: Version control (e.g., GitHub, shared files) and testing or debugging strategies.
3.2. System & Hardware Understanding
What judges are looking for:
They want to know if the team understands how the robot was developed and works as a system, not just individual parts.
Simple tips:
Be ready to explain:
Why you have chosen: this microcontroller, these sensors and motors, these materials.
How different parts communicate and work together
How your robot detects the environment, makes decisions, and/or reacts to unexpected situations.
Important details to mention:
Power and battery choices
Stability, balance, and movement;
Sensor choices,
Mechanical design (custom parts, gears, structures);
Sustainability choices, if any.
3.3. Technology Choice & Difficulty Level
What judges are looking for:
They want to see intentional and original design choices, not random ones. For instance, if you chose to use computer vision to guide the robot to a spot on stage instead of using the line following solution, explain the choice of that technology. Why does it fit your performance? What advantages and disadvantages did you consider in the decision process?
Simple tips:
Explain what makes your solution effective or innovative.
Talk about: the precision, reliability, and durability of your project.
3.4. Engineering Design Process
*What judges are looking for: *
They want to understand how your team learned, improved, and made decisions over time, not just the final robot. What they are focusing here is not just the innovative ideas (3.3), but rather the trial and errors in the process and what you learned with each version of the software/hardware.
Simple tips:
Be ready to explain:
Your iteration process: What was your first idea? What worked and didn’t work? Why? What did you change and why?
Collaboration: How did the team work together during design and testing?
Problem-solving: How did you solve software and hardware challenges as a team?
Use of AI: If AI was used, where and how was it used? Did it help and how? What did you train, test, or adjust/modify?
3.5. Learning Outcomes (Skills & Competencies)
What judges are looking for:
They want to see learning during the process, both technical and personal!
Simple tips
Talk about:
New technical skills learned (e.g., coding, electronics, mechanics, AI).
Engineering skill (e.g., testing, debugging, calibration, and/or system thinking).
Soft skills (e.g., communication, teamwork, problem-solving, and/or time management).
3.6. Teamwork
What judges are looking for:
Clear evidence that the whole team contributed.
Simple tips:
Explain who did what, but also how tasks were connected and team members collaborated.
Redirect the judges to the member who contributed to a specific part of the robot development (i.e. coding, design of the electric-circuit, or construction)
Demonstrate that decisions were made together.
Share a story about when the team faced challenges in the project and how the team helped each other to overcome them.
3.7. Live Demonstration of Selected Features during the Interview
The live demonstration of selected features will happen during the interview when you’re asked to explain your four features.
What judges are looking for:
Judges want to see if the four selected features work reliably and consistently. Before the demonstration,
make sure that your robots are stable and well-tested, and
practice demonstrating by focusing on each feature several times before the interview.
Prepare a short explanation for each feature:
What does this feature do?
How does it work?
Why is this feature important to the project?
How does it support the overall storytelling or goal of your performance?
Why did the team choose this feature instead of others?
During the demonstration:
If something goes wrong:
