text: whats it like for electrical engineers at work? im an ee major, and i have no idea of the types of work enviroments i might be in...  what the general format is, how much of a pain in the ass (compared to learning calculus 3 for example) ... most of all i want to know what kinds of daily things i will do..  and what methods are used...  will i be on a computer all day?  etc etc...  whatever info u got.  thanks you can find all kinds of work environments.  simulating things on a computer all day.  testing things in a lab all day.  conceptual design or detailed design.  solving problems at the customer's site (alaska in winter or socal at the ocean in summer).  solving problems in your own company's mfg line.  helping to sell your products to other companies. helping define standards that will be used industry-wide.  testifying in court cases.  analyzing patent applications.  supervise other engineers.  try as many as you can to find out which ones you'd really like to do for a long time...  some of the cool things you'll do:  see something you drew up get built. get something you designed to work the way you thought it should. get something you designed to work the way the boss thought it should. get something you designed to work the way the customer thought it should.  (yes, they are all different!) get something that your team designed to work the way the customer thought it should and now they are going to pay your company for it. point to something and tell your friends that you helped design it. have something you designed get used by someone else and you know it helped them, even if they never heard of you. have other engineers start asking you questions because they know you're the expert -- and you really are. come up with a real cool solution that makes the customer's mouth drop open (because they know "it can't be done") during a design review presentation. document something well enough that the production people don't call you.  not so cool things:  get laid off along with the rest of your coworkers -- usually just after buying a new car or house. spend a long time at the customer's site during your least favorite season to be there. put in 60 (80? 100?) hours and end up more behind than when you started the week. have your boss take credit for your work. have your boss's boss take credit for your work. have someone you've never heard of in your corporation from another city take credit for your work. have the customer ask your boss wtf when they see your design review presentation. spend weeks answering production questions while you're trying to get started on your new project.  just remember, they pay you because it's not always fun -- that's why it's called work!  also, remember that engineers don't actually build things -- they create documents that let others build things.  our outputs are the documents, so you want those to reflect your skills, abilities, and professionalism.  yes, the products have to work, but they will always be built to the documents you create.  sometimes it takes a while to "get religion" in this area, but the first time you're 2000 miles from home, using other engineers' documentation, and you aren't leaving until the customer is happy, will be the last time you put less information, instead of more information, in a document.  you'll curse their lack of documentation and resolve that you won't do that with yours (ever again).  if you're really unlucky, one of those poor documents will be yours from 6 months before, so you'll have to reconstruct what you were trying to do while the customer and your boss wonder why since you created it in the first place!  definitely something to try to avoid if you want to have engineering as a long career.