Paragon FTCFTC 11311 / 2026–27 season

01 / The people

Built by
a team.

Paragon's 2026–27 roster spans mechanical, software, electrical, project coordination, and outreach. Many members contribute to more than one part of the work.

Working together

Different roles. Shared goals.

The team's role plan connects engineering work with planning, safety, events, and communication.

A / Coordinate

Keep the work moving

Project management, meeting records, event planning, and the website keep the season organized.

B / Engineer

Build across systems

Mechanical, software, and electrical groups plan the robot as one connected system.

C / Share

Bring others in

Outreach and demonstrations make room for more people to try robotics firsthand.

2026–27 role plan

Meet the contributors.

First names below come from the team's current role table. Roles overlap and may change as the season develops.

01 / Coordination

Management & outreach

Darren, Sophia, and Jack cover project management, events, fundraising, and the website.

02 / Hardware

Mechanical

Darren, Jack, Aden, Ethan W., Ethan L., and Iris work across drivetrain, mechanisms, assembly, and fabrication.

03 / Code

Software

Eric, Dustin, Jinglin, Iris, and Sophia cover autonomous, teleop, controls, and computer vision.

04 / Systems

Electrical

Dustin, Jinglin, Aden, Eric, and Ethan W. take on integration, sensors, reliability, and ESD.

05 / Operations

Lab & safety

Aden, Ethan L., Iris, and Eric help with safety, equipment, maintenance, and asset tracking.

06 / Competition

Drive team

Jack, Darren, Sophia, and Ethan L. are listed for driving; Dustin and Eric are listed for drive coaching.

Paragon team members discussing ideas during a summer planning session
Planning together / summer 2026

The working loop

Talk. Make. Test.

The season plan moves from game analysis and prototypes into fabrication, programming, robot assembly, and driver practice. Team discussions help turn those tracks into a shared build.

  1. 01

    Plan

    Compare strategy ideas and decide what to try first.

  2. 02

    Prototype

    Build mechanisms and software in small, testable steps.

  3. 03

    Iterate

    Use testing and driver practice to guide the next change.