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
  • Design Interview Rubric
  • Criteria 1: Engineering Design Process
  • Criteria 2: Game Strategies
  • Criteria 3: Robot Design
  • Criteria 4: Robot Build
  • Criteria 5: Robot Programming
  • Criteria 6: Team and Project Management
  • Criteria 7: Teamwork, Communication, Professionalism
  • Criteria 8: Respect, Courtesy, Positivity

Was this helpful?

Edit on GitHub
Export as PDF
  1. The Judging Process
  2. The Interview

Interview Rubric Breakdown

PreviousThe InterviewNextUsing Notion for an Engineering Notebook

Last updated 10 months ago

Was this helpful?

This analysis uses the up-to-date rubrics as of September 2023. As new versions of each rubric are announced, this article will be updated shortly following. The up-to-date rubrics can be found in this article and on the .

Design Interview Rubric

Criteria 1: Engineering Design Process

Team shows evidence of independent inquiry from the beginning stages of their design process. This includes brainstorming, testing, and exploring alternative solutions.

When considering this step of the interview, it is important to reference the recorded in the throughout the entire interview. Structuring the interview around each step of the Design Process and talking through how the team implemented each step can be an efficient way to ensure this criteria is accomplished while providing structure to the interview.

Additionally, it is important to reference how each step of the Design Process was used and repeated throughout the season so far. Rather than just mentioning each step, describing the implementation shows a much more in-depth understanding of the Design Process.

Criteria 2: Game Strategies

Team can fully explain their entire game strategy including game analysis.

In describing the current strategy used by a team, it is important to describe how the team decided upon the strategy in the first place. Rather than simply describing what the robot does during a match, describing why the strategy was decided upon compared to other potential strategies will earn more points on the interview rubric.

Additionally, tying this criteria into the relevant steps of the Engineering Design Process can be a thorough method to illustrate understanding of the Design Process, as well as placing emphasis on how and why the strategic decision was made.

Criteria 3: Robot Design

Team can fully explain the evolution of their robot to the current design.

In addition to describing the current robot design and how it works, it is important to describe how the robot has reached its current state. Explaining previous design cycles and why they were discarded is essential to earn maximum points on the interview rubric, in addition to showcasing how what was learned from these design cycles was used in the development of the current product.

Highlighting the use of Decision Matrices and other methods of tracking overall project workflow can be a good method towards earning more points in this step, showcasing more references to the overall Design Process.

Criteria 4: Robot Build

Team can fully explain their robot construction. Ownership of the robot build is evident.

For this criteria, it is important to describe why the design was chosen, in addition to thoroughly describing the robot as a whole. Given the description of the criteria, a smooth transition from Criteria 3 to this criteria can help earn full points for both steps while still maintaining the pacing of the interview.

Criteria 5: Robot Programming

Team can fully explain the evolution of their programming.

Similar to Criteria 3, it is important to highlight the evolution of the program throughout the season in addition to descriptions of how the program works. A high scoring team will showcase that the program was developed alongside the robot using the Engineering Design Process, rather than specifically developed last-minute without much thought.

Describing how programming development was tracked using timelines and set goals, similar to what is used in the Engineering Notebook, will go a long way towards improving rubric scores for this criteria.

Criteria 6: Team and Project Management

Team can explain how team progress was tracked against an overall project timeline, team can explain management of material and personnel resources.

Though this criteria should have been touched upon in previous steps of the interview, it is important to describe process management used by the team throughout the season. Placing emphasis on how Gantt Charts or other similar timelines were used to keep robot and programming progress on track is essential to earn maximum points on the rubric for this criteria.

Additionally, referencing how various roles and projects were split among the team, as well as any specific time constraints beyond set deadlines, should be brought up to meet the second half of the criteria. Management of materials through tracking available parts and use of parts on various designs or prototypes is another beneficial process to explain.

Criteria 7: Teamwork, Communication, Professionalism

Most or all team members contribute to explanations of the design process, game strategy, and other work done by the team.

This criteria can be accomplished without much specific explanation by having each member present their role on the team, or a step of the Design Process that they may have had particular affinity for. Describing the role of each team member as they begin to present a segment of the interview is also beneficial towards being absolutely clear regarding team involvement.

Additionally, practicing the interview prior to competition can help to ensure each team member knows when to speak their part of the interview, ensuring that all team members are able to answer their segment or question without difficulty or influence.

Criteria 8: Respect, Courtesy, Positivity

Team consistently interacts respectfully, courteously, and positively in their interview.

The most effective method of ensuring this criteria has been met throughout the entire interview is to practice prior to competition. Practice can help to make sure that each team member knows when it is their turn to speak, as well as to ensure that each team member has a fair portion of the interview.

📚
RECF website
Engineering Design Process
Engineering Notebook