the video version
The same lesson as a narrated video. Watch it on YouTube
A team is a small company#
An FRC team is far more than a few people with wrenches. Successful teams organize into sub-teams, each owning part of the work. You do not need to be an engineer to contribute — there's a role for almost any interest.
Technical sub-teams#
Mechanical / Build#
Designs and fabricates the physical robot: the drivetrain (how it moves), the manipulators (intakes, arms, shooters, climbers), and the structure. Members learn to use tools like drills, band saws, lathes, mills, 3D printers, and CNC routers, and to work with aluminum extrusion, gears, belts, and bearings.
CAD / Design#
Models the robot in 3D CAD (commonly Onshape, which is free and cloud-based for FRC teams, or Fusion/SolidWorks) before anything is cut. Good CAD prevents costly build mistakes and lets the team plan packaging, weight, and motion.
Electrical / Wiring#
Wires the control system: the roboRIO (the robot's brain), a Power Distribution Hub (PDH) or Panel (PDP), motor controllers (e.g., Talon FX inside the Kraken X60/Falcon 500, or SPARK MAX/Flex driving NEO motors), the radio, breakers, the 12V battery, and sensors. Clean, reliable wiring is a hallmark of strong teams.
Programming / Software#
Writes the robot code using WPILib (the official library, supporting Java, C++, and Python) in a VS Code-based environment, plus the FRC Driver Station software. Programmers handle drivetrain control, autonomous routines, sensor integration, and increasingly vision (cameras like Limelight or PhotonVision).
Non-technical sub-teams#
Business / Operations#
Manages the budget, fundraising and sponsorships, registration logistics, and travel. Teams often raise tens of thousands of dollars per season — this work is essential.
Outreach / Impact#
Runs community events, mentors younger FLL/FTC teams, and documents the team's impact. This sub-team drives the FIRST Impact Award submission, the highest honor in FRC.
Media / Marketing#
Handles branding, social media, photography/video, the team website, and the technical binder/presentation used for judging.
Competition-day roles#
Drive team#
The only people allowed to operate the robot during a match, typically:
- Driver — controls robot movement.
- Operator — runs the mechanisms (intake, shooter, climber).
- Human Player — feeds game pieces from the field stations.
- Drive Coach — calls strategy and communicates with alliance partners.
- Technician — preps the robot in the pit and on the field.
Scouting#
A data-driven role: scouts watch every match and record each robot's performance, then analysts use that data to advise alliance selection and match strategy. Scouting can decide whether your alliance wins the event.
Pit crew#
Repairs and maintains the robot between matches in the pit, the team's workspace at an event.
How to choose#
Try several sub-teams early. Many great members start in one area (say, electrical) and discover a passion in another (say, scouting analytics or outreach). The point is to find where you add the most value and have the most fun.
Learn more#
- FRC Technical Resources: https://www.firstinspires.org/resources/library/frc/technical-resources
- WPILib documentation (programming): https://docs.wpilib.org
the part worth keeping
Key takeaways
- FRC teams run like small companies with technical sub-teams (mechanical/build, CAD, electrical, programming) and non-technical ones (business, outreach/impact, media).
- Competition day adds specialized roles: the drive team (driver, operator, human player, coach, technician), scouting, and pit crew.
- You don't need to be an engineer to contribute — there's a valuable role for nearly every interest, and trying several early helps you find your fit.
Getting Started with FRCCulture, Teams, and Roleslesson 2 of 3
Keep going
Take the quiz+10 XP with an accountMore in Culture, Teams, and Roles
where this came from
Sources and corrections
This lesson is AI-assisted: drafted from primary sources, then reviewed and edited by hand. Errors still get through. When one is reported we fix it and write down what changed, in public, in the corrections log.
sources and further reading
- firstinspires.orgFRC Technical Resources
- docs.wpilib.orgWPILib Documentation
clipped to this lesson
Articles that go further on this
The lesson gets you through the topic. These go wider on it, and they read in one sitting.
- 4 min readFRC Drive Team Guide: Roles and How to WinA clear, accurate guide to FRC drive team roles - drivers, coach, human player, and technician - plus practical tips for winning more matches./blogread it
- 7 min readHow to Structure an FRC Team: Subteams, Roles, and LeadershipA practical guide to organizing an FRC team: the common subteams, student leadership, mentor roles, meeting cadence, rookie onboarding, and sustainability./blogread it
- 20 min readREV Robotics for FRC: NEO Motors, Spark MAX/Flex, PDH & MAXSwerveA practical guide to the REV Robotics FRC ecosystem: NEO, NEO Vortex and NEO 550 motors, Spark MAX and Spark Flex controllers, the PDH, and MAXSwerve./blogread it
answer sheet
Lesson quiz
All 3 right completes the lesson. Miss one and only that question comes back, anything you already answered correctly stays banked.
0 of 3 answered
01On a typical FRC team, which sub-team is primarily responsible for designing and fabricating the robot's drivetrain, manipulators, and structure?
02Which sub-team is mainly responsible for wiring the control system, power distribution, and connecting sensors and motor controllers on an FRC robot?
03During a match, which drive-team member's main job is to run the robot's mechanisms (such as an intake, shooter, or climber) rather than its driving movement?
Answer every question to submit.
All 28 lessons in Getting Started with FRCopenclose
01 / what-first-and-frc-are
02 / the-season-and-the-game
03 / culture-teams-and-roles
04 / getting-started-your-first-steps
05 / worked-examples-mini-projects
- Not read yet:Project 1 — Make a NEO Spin with the REV Hardware Client
- Not read yet:Project 2 — Deploy a Real Arcade-Drive Program
- Not read yet:Project 3 — Refactor into a Command-Based Drive Subsystem
- Not read yet:Project 4 — Build a Fuel Launcher for REBUILT
- Not read yet:Project 5 — A One-Button Autonomous Routine
06 / common-mistakes-troubleshooting
- Not read yet:The Connection Chain: When the Driver Station Won't Connect
- Not read yet:Brownouts: Why the Robot Goes Limp Mid-Match
- Not read yet:CAN Bus Gremlins: Missing and Conflicting Devices
- Not read yet:Software Gotchas: Inverted Drives, Scheduler Stalls, and Reading the RioLog
- Not read yet:Inspection-Day Failures: Bumpers, Size, and Weight
07 / advanced-techniques-case-studies
- Not read yet:Closed-Loop Control: PID + Feedforward for a Consistent Shot
- Not read yet:Swerve Drive: Omnidirectional Movement with YAGSL
- Not read yet:AprilTag Vision: Knowing Where You Are with PhotonVision
- Not read yet:Data-Driven Strategy: Scouting, EPA/OPR, and Alliance Selection
- Not read yet:Choosing Your Hardware Ecosystem: REV vs CTRE