View Single Post
  #4   Spotlight this post!  
Unread 26-03-2008, 10:18
JesseK's Avatar
JesseK JesseK is offline
Expert Flybot Crasher
FRC #1885 (ILITE)
Team Role: Mentor
 
Join Date: Mar 2007
Rookie Year: 2005
Location: Reston, VA
Posts: 3,625
JesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond repute
Re: Career in Systems Engineering.

I'll give you some anecdotal evidence based on my perspective of a Systems Engineer. You don't need a piece of paper that says you know what you're doing to be a SysE. Actually, those pieces of paper in the real world for that particular discipline mean next to nothing. Alex is correct that experience in this field greatly outweighs the education. We have people where I work who's title includes SysE somewhere in it but they never went to school for it. It's something they picked up since they had expertise in a variety of different systems we integrate together for our contracts.

Those particular guys have phases of extreme stress and then phases of boredom. The stress comes the fiscal quarter right before we roll out a product we have a contract for, and the boredom comes just after that. Well, I guess I should say it's "relative" stress and "relative" boredom.

My particular career has considered SysE, but I also still have options to specialize in something. Who knows where I'm going though; I'm only 25 and still have the majority of my career ahead of me.
__________________

Drive Coach, 1885 (2007-present)
CAD Library Updated 5/1/16 - 2016 Curie/Carver Industrial Design Winner
GitHub
Reply With Quote