So it’s a question of Breadth vs. Depth.
If you go to work for a small startup, chances are, you will just be an “engineer” who gets to do a bit of everything! The scope is small enough that just one or a few humans can do all the aspects of design and manufacture. This could be something you could look into as you form your future career path.
However, on BIG engineering projects (think, the space shuttle, an airliner, a cruise ship), no human being has the capacity to single-handedly design and implement everything. You have to split it into a team project, and most of the team members will inevitably have to pick specializations.
As you go off to college, consider some of the lesser-known specializations. Technical Systems Management at UIUC is one I’m aware of, as is the Cyber Physical Systems Minor AKA “mechatronics” at Iowa State. These programs emphasize breadth-first approaches where cross-functional skills are taught, rather than a “depth-first” dive into the details of one particular aspect of engineering.
University engineering teams like Baja SAE, Formula SAE, Solar Car, and many others will provide a FIRST-like experience. Especially if you’re starting up one of these clubs from scratch, you’ll likely find yourself in that “little bit of everything” role.
As you pick your major, minor, and courses… build up the story of why you are doing what you are doing. Tell that story with how you craft your resume, and how you pitch yourself to employers. Don’t shy away from the idea that you like being involved in a bit of everything, and also emphasize how you know how to work with many teams of people at once. This will disqualify you from some of the more “depth-first” oriented jobs, but make you very attractive to a person who needs a true “Systems Engineer” who can wear many hats in a single day. In turn, this should help down-select your job offers to ones that are most interesting.
On the other hand… keep in mind a lot of companies, especially right out of college, prefer you be able to illustrate one or more specializations you have - they want to know what makes you unique from your peers.
Also, keep in mind, you’ll hopefully have a solid 50+ years ahead of you to keep repeating that FIRST experience you had, again and again. That’s another 10+ cycles of what you just went through. Each cycle, you shouldn’t be doing the same things again and again. Think of each cycle as an opportunity to pick a new specialization, dig as deep as you can in four to six years, do some productive work, then know you’ll be moving on to something else right about the time you’ve hit the level of expertise you desire.
What you’ll want to be cognizant of is at what point to hand off a task to another person. This is just a general “working in a team” skill that FIRST hopefully teaches, but will be essential. In every engineering role, you’ll always have something you have to let someone else do.
You’ve definitely already experienced this - for example, in FIRST, students don’t design the PCB inside the RIO - someone else does that for you, and tells you how it works, and you just have to use it. Same will be for any team, large or small, you work with in the future.
ALL that being said… Yes, CS does pay the bills the best. At least by starting salary.
Hence the reason why this EE with a sorta-CS job knows CAD.