LogoLogo
  • Welcome!
  • Mission Statement
  • Contributing Guidelines
    • Embed CADs in Wiki Articles
  • VEX Worlds Livestream Archive
    • VEX U
    • V5RC High School
    • V5RC Middle School
    • VIQRC Middle School
    • VIQRC Elementary School
    • JROTC
  • ⚙️Hardware
    • Design Fundamentals
      • Gear Ratios
      • Internal Forces (Stress)
      • Torque
      • RPM
      • Center of Mass
    • Introduction to VEX Parts
      • Structure
        • C-Channels and Angles
        • Fasteners
        • Retainers
        • Gussets and Brackets
        • Bearings
        • Plate Metal and Flat Bars
      • Motion
        • High Strength Components
        • Gears and Sprockets
        • Traction Wheels
        • Mecanum Wheels
        • Omnidirectional Wheels
        • Flex Wheels
    • Robot Decorations
      • Part Dyeing
      • Metal Coloring
      • License Plate Holders
    • Lifts
      • Double Reverse Four Bar (DR4B or RD4B)
      • Four Bar
      • Scissor Lift
      • Six Bar
      • Other Lifts
      • Best Practices
    • Shooting Mechanisms
      • Catapult
      • Flywheel
      • Linear Puncher
    • Drivetrains
      • Tank Drive
      • Mecanum Drive
      • Holonomic Drive
      • Designing a Drivetrain
      • Best Practices
    • Pivots & Joints
    • Pneumatics
      • Best Practices - Pneumatics
    • Intakes
    • Flip Out Mechanisms
    • Defensive Mechanisms
    • Misc. Building Techniques
    • VexU
      • Common Manufacturing Techniques
        • 3D Printing
        • Laser Cutting
      • Custom Manufactured Parts Library
      • Commercial Off The Shelf Parts Library
  • 👑Team Administration
    • New Team Resources
      • Creating The Team
      • Gaining Interest for Robotics Teams
      • Attending Competitions
        • Elimination Bracket
    • Team Dynamics
      • Organization Structure and Longevity
      • Member Allocation and Management
      • How *Not* To Run a Team
    • Team Finances
      • One-Year Team Financial Breakdown
      • Funding Your Teams
    • Hosting Competitions
      • Live Streaming
      • Tournament Manager
        • Competition Electronics
        • Creating a Tournament
        • Tools
          • Field Set Control
          • Connecting Mobile Devices
          • Connecting Raspberry Pis
        • Match Control
          • Inputting Match Scores
          • Inputting Skills Scores
          • Inputting Scores on TM Mobile
        • Displays
        • Alliance Selection
      • Additional Event Partner Resources
    • VexU Organization Management
      • Getting Started in VexU
      • Team / Personnel Management
      • Volunteering At Local Events
  • 📚The Judging Process
    • The Engineering Design Process
      • Test and Refine
    • The Engineering Notebook
      • Segments of the Notebook
      • BLRS2 '23-'24 Engineering Notebook
      • Integrating Inventor Models into Documentation
      • Engineering Notebook Rubric Breakdown
    • The Interview
      • Interview Rubric Breakdown
    • Using Notion for an Engineering Notebook
      • How to Setup a Notebook
      • How to Create Entries
      • How to Export a Notebook
      • Purdue SIGBots Notion Template
        • Game Analysis
        • Identify The Problem
        • Brainstorm Solution
        • Select Best Approach & Plan
        • Build Log
        • Programming Log
        • Testing Solution
        • Tournament Recap
        • Innovative Feature
  • 🖥️VEX CAD
    • CAD Programs
      • Inventor
      • Fusion 360
      • Solidworks
      • OnShape
      • Protobot
    • Making a Chassis
      • Inventor Chassis: The Basics
        • Installation
        • User Interface Overview
        • Dark Mode
        • Assemblies
        • Placing Parts
        • Navigating CAD
        • Changing Visual Style
        • Grounding
        • Connecting Two C-Channels
        • Modifying Existing Constraints
        • Toggling Visibility on Existing Parts
        • Completing Half of the Chassis
          • Inner Drive Channel
          • Bearing Flats
          • Motors
          • Wheels
          • Sprockets
          • Spacers, Washers and Standoffs
          • Spacers Cont.
        • Creating Mid-Plane
        • Mirroring
      • Inventor Chassis: Best Practices
        • File Structure
        • Subassemblies
        • Wheel Subassembly
        • Origin Planes
        • Cross Brace
        • Drive Channels
        • Simple Motor iMates
        • Replacing Simple Electronics
        • Completing Half of the Drive
          • Bearing Flats (Best Practice)
          • Wheels
          • Powered Gear
          • Spacer Boxing
          • Spacers, Washers and Standoffs (Best Practice)
        • Model Browser Folders
        • Mirroring (Best Practice)
        • Model Browser Folder (Right)
        • Main Assembly
      • Fusion 360 Chassis
      • Solidworks Chassis, Chain, and Custom Plastic
    • Remembering The Best
      • 62A Skyrise
      • 400X Nothing But Net
      • 2587Z Nothing But Net
      • 365X Starstruck
      • 62A In The Zone
      • 202Z In The Zone
      • 5225A In The Zone
      • 169A Turning Point
      • 929U Turning Point
      • 7K Tower Takeover
      • 5225A Tower Takeover
      • 62A Change Up
    • Scuff Controller
  • 💻Software
    • Odometry
    • Path Planning
    • Robotics Basics
      • Arcade Drive
      • Tank Drive
      • Joystick Deadzones
      • Curvature (Cheesy) Drive
      • Subsystem Toggling
    • Organizing Code
      • Code Style
      • Code Styling Guide
      • Writing Good Comments
      • Version Control
    • Control Algorithms
      • Bang Bang
      • PID Controller
      • Basic Pure Pursuit
      • Flywheel Velocity Control
      • Kalman Filter
      • Take Back Half (TBH) Controller
      • RAMSETE Controller
    • Competition Specific
      • Operator Control
      • Autonomous Control
    • C++ Basics for VEX Robotics
      • Basic Control Flow
      • Enumerations
      • Namespaces (::)
      • Multiple Files (C/C++)
    • VEX Programming Software
      • PROS
        • OkapiLib
      • vexide
      • Robot Mesh Studio (RMS)
      • EasyC
      • RobotC
      • VEXcode
      • Midnight C
    • General
      • Stall Detection
      • Register Programming
      • Sensors and Odometry in Autonomous
      • Embedded Programming Tips
      • Debugging
      • Bit Shift
      • Bit Mask
      • Autoformatting
      • Finite State Machine
      • Data Logging
    • Object Recognition
      • Red Green Buoy
      • AMS
      • OpenCV
      • OpenNI
    • 🤖AI in VRC: Pac-Man Pete
  • ⚡VEX Electronics
    • V5 ESD Protection Board
    • VEX Electronics
      • VEX V5 Brain
        • V5 Electronics Observations and Issues
      • VEX Controller
      • VEXnet and V5 Robot Radio
      • VEX Battery
      • VEX Motors
    • VEX Sensors
      • 3-Pin / ADI Sensors
        • Encoder
        • Potentiometer
        • Limit Switch
        • Bumper Switch
        • Accelerometer
        • Gyroscope
        • Ultrasonic
        • Line Tracker
        • LED Indicator
      • Smart Port Sensors
        • GPS Sensor
        • Rotation Sensor
        • Vision Sensor
        • Optical Sensor
        • Distance Sensor
        • Inertial Sensor (IMU)
        • 3-Wire Expander
    • V5 Brain Wiring Guide
    • Legacy
      • VEX Cortex
      • Power Expander
      • VEX Motor Controller
      • VEX Cortex Wiring Guide
  • General Electronics
    • General Topics
      • External Boards
        • ASUS Tinker Board S
        • Arduino
        • Beagleboard
        • Leaflabs Maple
        • LattePanda
        • Meadow F7 Micro
        • Netduino
        • ODROID-XU4
        • Pandaboard
        • Raspberry Pi
      • Analog-Digital Converter (ADC)
      • Bit-Bang
      • GPIO
      • I2C
      • Jitter
      • Line Noise
      • List of Tools
      • Output Drive
      • Power Consumption
      • Radius Array
      • Resettable Fuse (PTC)
      • SPI
      • Slew Rate
      • Stalling
      • USART
      • UART
      • 5 Volt Tolerant
      • DC Motor Basics
Powered by GitBook
LogoLogo

This work is licensed under a Attribution-ShareAlike 2.0 Generic License

On this page
  • Pit Interviews
  • Secondary Interviews

Was this helpful?

Edit on GitHub
Export as PDF
  1. The Judging Process

The Interview

An integral component in the tournament judging process, the Design Interview is a great way for teams to grow public speaking skills while discussing robotics in a friendly environment.

There are two main types of interviews, both equally important, that will take place at a competition. The first are pit interviews, where all teams will speak to the judges either in the pits or in a dedicated judging room, where the team will present their robot and overall design process. Additionally, some teams will receive a secondary interview, where judges will ask specific questions pertaining to specific aspects of a team's performance.

Pit Interviews

Pit interviews are the first type of interview that teams will experience at a competition, with judges usually interviewing every team at a given competition in this format. As a minimum baseline, teams should aim to follow the rubric as closely as possible, in order to gain maximum points on the judging rubric (linked below). In most regions, there will be multiple teams at the same competition that score very high on the rubric, meaning that it will come down to various other factors to differentiate teams when it comes to picking who wins awards. These other factors could include a unique design process; an extremely well designed, programmed, or built robot; unique circumstance to the team; as well as a myriad of other factors that could set teams apart in the interview process.

How to Prepare

  • Introduce each team member to the judges.

    • Aside from being polite, telling the judges a bit about "the team" helps to personalize the interview, and stand out compared to other teams.

  • Plan ahead for roles during the interview.

    • Every team member should be talking during the interview, in order to show that the whole team is actively involved in the design process.

    • Be sure to practice transitioning topics from one team member to the next!

  • Use the Engineering Design Process (EDP) to describe the journey to the current robot.

    • In addition to scoring points on the rubric, tying the EDP into the progression of your interview helps to establish a flow and logical progression through your interview.

    • As an example, starting off the interview with Step 1 of the EDP could elaborate on the specific game challenges a robot could be trying to solve, with Steps 2 and 3 leading into the team's research of which designs could end up being pursued. Step 6 could be used to describe previous iterations of the robot that led up to a current design.

  • Plan around being adaptable.

    • Not every judging process will be the same - some judges will opt to solely listen to teams, allowing for teams to give a "presentation" of sorts. Other judges, however, will ask specific questions about the team, in order to score and note down any notable responses.

    • While it's good to have a plan and practice going into the pit interview at a competition, it's always a bonus to keep flexibility in mind as well. Whether the interview is in a presentation or question and answer format, the team should be ready to adapt their responses to fit any way the judges may require - getting all intended information across regardless.

  • Keep the pit interview fairly broad.

    • In the pit interview, the most important things are to cover every point on the rubric to the fullest extent and to differentiate oneself from other top contending teams, keeping in mind the relatively limited time limit as well. Because of this, it is important to keep the scope of the interview fairly broad, touching on every important, necessary topic - rather than tunneling in on only one or two aspects of the team.

    • In keeping the scope of the interview fairly broad, this allows the judges to ask questions about many different aspects of the team, from which further elaboration can be spawned. This also allows judges to note various topics to return to in the secondary interview, as well!

    • Keep in mind, while you want to keep the interview broad enough to cover every important aspect of the team, be sure not to leave out important details to cover too many topics! In practicing the interview, cutting out unnecessary fluff can strengthen the core material of the interview, and allow the team to cover the EDP to the fullest extent.

  • At the end of the day, the judges are just people interested in VEX Robotics and the teams behind them!

  • Follow the rubric.

  • Practice, Practice, Practice!

Secondary Interviews

Top contenders from the pit interviews and Engineering Notebook rubrics, at most competitions, will be granted a secondary interview. The secondary interview is a chance for judges to ask more specific questions about the team, usually pertaining to one of the awards offered at the competition in question. Secondary interviews generally go more in depth on a select few topics, rather than the overall broadness of the pit interview - and there is no specific rubric for the secondary interview outside of specific award criteria.

How to Prepare

  • Read the award rubrics to know how to best prepare.

    • There are many different awards offered in VEX Robotics Competition, for many different aspects of the competition, with most involving the judging and interview process in some way. As such, it is best to read through and understand all of the criteria for each award, in addition to the standard pit interview and Engineering Design Notebook rubrics.

    • While a team may wish to target a specific award, the judges may decide to ask your team questions about a different, or even multiple, awards. Therefore, it is always best to have a response prepared for each question, should the need arise.

  • Practice with mentors and have them ask questions.

    • For the type of in-depth response a good secondary interview will require, it is best to practice what should be said for each topic in advance, or at the very least knowing enough about your robot to improvise an answer. Having a coach or mentor ask specific questions pertaining to each award category can help develop the knowledge and reasoning behind exceptional answers.

  • Have visuals, demonstrations, or references to the Engineering Design Notebook if applicable.

    • Being able to show off various features of the robot working effectively during an interview is an easy way for the judges to see interesting, unique, or effective parts of the robot that have been called into prominence during the secondary interview.

    • For instance, a demonstration relating to the Think Award could be demonstrating a small, point to point movement algorithm that has been used in the larger autonomous code. In addition to receiving a detailed, well thought out answer verbally, the judges are able to see tangible proof of the team's effectiveness in action.

    • Referring to specific pages in the Engineering Design Notebook is a good way to call back to more in-depth explanations that have been written in the past. This way, the judges are able to see evidence that the team's answers have been thought through based on true experience, rather than making things up on the spot to seem more knowledgeable.

  • Make sure to switch between speaking team members often and act as if it is a conversation over a presentation.

    • In addition to covering more in-depth material, secondary interviews are a way for judges to get a better read on the team themselves. It is still good to carry a professional manner, but don't let that get in the way of letting the conversation flow effectively. The judges are there to learn more about the team, and an effective way to accomplish that is for teams to talk with them, rather than "at them."

PreviousEngineering Notebook Rubric BreakdownNextInterview Rubric Breakdown

Last updated 10 months ago

Was this helpful?

The Interview Rubric can be found on the , make sure to read the rubric thoroughly, in order to practice scoring as many points as you can!

📚
RECF Website