Why Subteams?

Autonomous drones are complex systems that span mechanical engineering, electronics, real-time software, computer vision, and simulation. No single person can master all of it — subteams let members specialize while still collaborating toward a single flying vehicle.

Each subteam owns a core area of the drone, working in parallel so progress can happen quickly across the whole stack. Members get focused experience in the domain they care about most.

⚙️
⚙️ Mechanical
🔌
🔌 Embedded Systems
👁️
👁️ Perception
🌐
🌐 Simulations

Q & A

Do I have to pick just one subteam?

Not necessarily. Many members focus on one subteam at first to build depth, then branch into other areas once they're comfortable. We encourage specialization early and cross-pollination later.

Can I switch subteams?

Yes — talk with the subteam leads and we'll help you transition without disrupting ongoing work. People switch when their interests evolve or they want a new challenge.

How experienced do I need to be?

No prior drone or robotics experience is required. We'll point you toward learning resources and pair you with more experienced members. Curiosity and consistency matter far more than what you already know.

What majors are welcome?

All majors! We need mechanical engineers, computer scientists, electrical engineers, and anyone who's excited about autonomous systems. If you're not sure where you fit, come to a meeting and we'll figure it out together.

How Do I Join?

Getting involved is straightforward — here's the usual flow:

1. Complete the SlugWorks Canvas & join our Discord

Most of our work happens in SlugWorks (BE-49). Complete the safety training Canvas module and do a walkthrough to gain workspace access. Join our Discord to stay up to date on meetings and announcements.

TO BE FINISHED LATER — add Canvas and Discord links

2. Visit a few subteam meetings

Check out subteam meeting times listed on each subteam page. If the times don't work for your schedule, reach out to the leads — we reschedule at the start of every quarter to fit everyone.

3. Commit to a subteam

Once you've explored, pick a primary subteam and start taking on tasks — CAD modeling, firmware, vision code, simulation scripts, whatever fits that group's current needs.

Not sure where to start? Ask any subteam lead or message us through the contact info on the home page.