Satt said:
I am in school for Electrical Engineering right now and I have never actually seen the job in action. I was wondering if anyone that is an Engineer could enlighten me about what a day in the life is like. Also, if you don't mind, let me know what kind of Engineer you are and what branch of this work is the easiest one to get a job in. Many thanks in advance.
Jason :fart:
I work in the Embedded Software area:
Right after college I went to work for General Dynamics, and I did Unit testing ob benches, where you step through code and plug in high and low numbers and out of range values and such. I also did reviews of designs and code, and test results in a group review. This gets people to review and look for errors and gets one used to it is the process not an attack on the person to review their work. I also wrote code for various programs.
I left GD and went to contracting at Chrysler where I wrote the Operating system for their new daignostic tool called the DRBIII (* Diagnostic Recorder Box 3rd edition *). I also wrote other software there as well. What surprised me was that when I asked others to review my design, they were surprised, and did so, which helped, but was still a surprise. The group operated under the premise that you do your best and then go try it out and the change it if it did not work. I was able to work the vehicles and the diagnostic equipment in garages and on benches. It was fun and educational.
I left there for GM and a direct position. I took a large amount of bundled code and integrated it with another large amount of bundled code. (* I took the common Transmission software, and then modified the interfaces for the changes and integrated it with the Passenger V6 Engine Code *). Here with me and a few others, we instituted design reviews and code reviews, that were documented and saved for future reviews when problems were found later. This was done to see if they could have been found and why they were were missed. I also would take the software and run it on a bench and from there to a vehicle.
I know am a System Engineer responsible for a whole ECM - Engine Control Module - and others now code and test and do the detail design work, while I sit in on reviews and mange the timing and content for the deliverables of the program.
As to what Arni said about taking what others have done and building this is true for the most part, but you can get a patent in this field as well.

The only thing I would suggest is to go into communications and not the auto industry unless you really are a car guy, as the auto industry is not as stable as it used to be, and people doing more and more with less resources, but I still enjoy the field myself.