The Mechanical Sub-team handles all the robot hardware and is the most hands-on with the robot. They are responsible for constructing all the parts used on the robot and assembling them. The sub-team also handles all the wiring of the electronics on the robot and sets up any pneumatic systems. In addition to the first-time assembly of the robot, the mechanical sub-team also works on repairing things that are broken. More experienced members of the sub-team will work with CAD in finalizing the design of the robot.  

The Programming Sub-team is the sub-team that handles all the robot software and also gets to be fairly hands-on with the robot. The sub-team is responsible for coding all the functionality of the robot. Ultimately, the code will come down to two parts; making easy-to-use controls for the drive team and writing effective autonomous code for the first 15 seconds of the match.  

The programs linked below are some of the main programs used by programing. Github is used to sync the code between devices, WIPlib is what the actual code is done on, and finally Team 6329's Advantagekit to track the field and graph the robots actions.

The Logistics Sub-team is in charge of every other aspect of the team. The Logistics Sub-team is roughly composed of two halves – Internal Operations (IO) and Public Relations (PR). Internal Operations is responsible for working on the Business Plan, coordinating team bonding activities, preparing team spirit materials (including merch), and maintaining the team’s branding standards. Public Relations is responsible for running the team’s social media channels, maintaining the team's website, tracking and coordinating team outreach, and setting up formal events. Both IO and PR work together on the team's award submissions (various essays, animations, and presentations), as well as on maintaining strong relationships with the team’s sponsors.  

Team 818: The Steel Armadillos is run by a student leadership system, composed of the team captains and sub-team leads.