Every role is an engineering role

View Our Team Season Video

— Who builds it

Meet Our Team

Natalie

Hank

Autonomy & OpMode

Process & Notebook

Keeps the engineering notebook current through each design cycle. Records decisions, rejected approaches, and the reasoning behind each pivot.

Owns chassis geometry, motor selection, and gearbox trade-offs. Writes iteration notes after every major test run.

Maps every sensor, motor controller, and power circuit. Maintains the wiring diagram that gets updated each revision cycle.

Authors autonomous routines and teleop logic. Each OpMode version is tagged against the mechanical build state it was tested on.

Natalie

Hank

Autonomy & OpMode

Process & Notebook

Keeps the engineering notebook current through each design cycle. Records decisions, rejected approaches, and the reasoning behind each pivot.

Owns chassis geometry, motor selection, and gearbox trade-offs. Writes iteration notes after every major test run.

Maps every sensor, motor controller, and power circuit. Maintains the wiring diagram that gets updated each revision cycle.

Authors autonomous routines and teleop logic. Each OpMode version is tagged against the mechanical build state it was tested on.

Each design review session brings in practicing engineers from local industry partners. They review our CAD, stress our load assumptions, and ask questions we haven't thought to ask ourselves.

Feedback is logged in the engineering notebook against the specific subsystem version reviewed. When we change something because of a review, we say so—and link back to the session notes.

Outreach events—elementary school demos, library workshops, and district STEM nights—are logged with the same rigor as build sessions: date, audience, what we showed, and what questions came back.

Documented alongside the build

There's a role with your name on it

Whether you write code, sketch mechanisms, or want to keep the notebook honest—reach out and tell us where you'd fit.