Our story

Built by students, season after season

We are a student-run FIRST Tech Challenge team designing, building, and programming a new competition robot every season. Our work runs from CAD and machining through autonomous software and scouting analytics, and it carries into the classrooms and community events where we introduce younger students to engineering. Every season we set out to build something that holds up under pressure and to bring more people with us while we do it.

  • 4 Seasons competed
  • 12 Awards won
  • 45 + Members and alumni
  • 2 Championship appearances

Mission

Why we do this

[Placeholder] Replace this with the team's own mission, in the team's own words. Say what Bubblotics is trying to do, who it is trying to reach, and what would count as a good season beyond the scoreboard. Two or three paragraphs.

[Placeholder] A second paragraph on what members actually get out of it: the skills, the mentorship, where alumni have gone. Judges read this section, and so do parents deciding whether to sign a permission form.

How we work

Three things we hold to

Build it twice

[PLACEHOLDER] A first prototype exists to be wrong. We would rather find a failure in the shop in November than on the field in March.

Everyone touches the robot

[PLACEHOLDER] No member spends a season without a wrench or a keyboard in their hands. Business students machine parts, and builders write outreach copy.

Leave it better

[PLACEHOLDER] Every season we hand down documentation, tooling, and mentorship so the next group starts further ahead than we did.

Timeline

How we got here

Rookie year [PLACEHOLDER: 20XX]. What follows is the short version.

  1. [PLACEHOLDER: 20XX]

    The team forms

    [PLACEHOLDER: Who started it, why, and what the first season looked like. Two or three sentences is plenty.]

  2. [PLACEHOLDER: 20XX]

    First qualifier

    [PLACEHOLDER: The first competition. What went wrong is usually the better story.]

  3. [PLACEHOLDER: 20XX]

    Provincials

    [PLACEHOLDER: How the team advanced and what changed about how it worked.]

  4. [PLACEHOLDER: 20XX]

    Where we are now

    [PLACEHOLDER: The current season, current size, and what the team is aiming at.]

Structure

Four subteams, one robot

Work is split so nothing waits on one person, and everyone still knows how the whole machine goes together.

01

Mechanical

Designs the robot in Onshape, then machines, prints, and assembles it. Owns drivetrain, intake, scoring mechanisms, and every iteration in between.

02

Programming

Writes the autonomous routines and driver controls, tunes odometry and vision, and maintains the tooling the team relies on during matches.

03

Business and Outreach

Runs sponsorship, the engineering portfolio, and the community events that put robotics in front of students who have not seen it before.

04

Strategy and Scouting

Tracks every match at every event, turns it into data the drive team can use, and builds the alliance selection picklist.

The team

Faces behind the robot

[Placeholder] Drop photos into src/assets/gallery/ and they appear here automatically.
[Placeholder]
[Placeholder]
[Placeholder]
[Placeholder]
[Placeholder]

Join or support

Want in?

Students, mentors, and sponsors are all welcome. Tell us which one you are and we will get back to you.

Contact us Sponsor the team