Since I didn't have anything original to say today, I'll go with Eva's suggestion and tell you all what I do for work. I'm an electrical engineer, and I design electronic controls. There. I'm sure that clears it all up.
I really am not sure how to describe what it is an engineer does. Even within the field of electrical engineering, there is an astounding number of different things you can do. EE's can work with large things like the power grid, power plants, space shuttles, and airplanes. They can work on nanotechnologies that are small enough to swim in the human bloodstream or application specific integrated circuits (ASICs) that are smaller than your fingernail. I work on none of those. I'm somewhere in the middle designing circuit boards that go into consumer goods. One example of a circuit board is that green thing in your computer with a bunch of square black, silver, yellow, and blue things on it. Inside your computer there are actually several circuit boards. What I do on any given day varies widely. Here is my typical day.
- Get into work around 8:00. Start computer boot-up process.
- Prepare my oatmeal breakfast while computer boots.
- Check e-mail.
- Respond to urgent e-mails.
- Send out e-mails to other people.
- Call some other people.
- Go to the lab and make sure you "squeak" so they get your work done.
- Go to lunch.
- Return from lunch.
- Nap.
- Check e-mail.
- Write some more e-mails.
- Make some more calls.
- Attend some meetings.
- Snack
- Check e-mail.
- Shut down computer
- Leave work.
Seriously, some days it feels like that's about all I get done. I do actually do some "real" work every once in awhile. I'm in the "execution" (otherwise known as delivery) part of the company, so that means I
don't do a lot of inventing, but I do a little bit of design work, I re-use a lot of stuff in my designs, and we are the "experts" in how to make a circuit board dirt cheap while still trying to walk that fine line between cost and quality (robust design) and jamming 40 pounds of potatoes (otherwise known as features) into my 20 pound circuit board, so to speak. No two days are ever the same, so it's hard to describe. Maybe as a compromise I will describe the last two days I worked (Friday and Monday).
Friday
- Get to work around 8:15
- Start computer boot-up process.
- Prepare oatmeal for breakfast while computer boots.
- Check e-mail.
- Go to 2.5 hour long weekly project summary meeting where we discuss progress of the projects, issues, give status updates, etc. There are about ten people in the room and people on the phone from India, Brazil, Mexico, and the U.S. I don't work on all of the projects, so while they're discussing projects I don't care about, I.....
- Update a parts list for an upcoming prototype build and send it to our contract manufacturer.
- Upload the parts list changes into our document management/storage system.
- Update a couple other documents in the aforementioned system in preparation for the project review happening that afternoon (don't want to look bad when the managers review it!).
- Review some test results, put my analysis in the test request, and resubmit it to the lab so the test request can be closed.
- Respond to some e-mails.
- Instant message with people from work about various tasks, tests, etc.
- Give my input on projects I am working on - resources needed, issues that need to be addressed, items we need to watch closely, ideas on possible root causes of strange behavior from the circuit boards or systems we are responsible for, etc.
- Start my weekly update e-mail but don't have time to finish it during the meeting.
- Finally, the marathon meeting ends. Go from the conference room back to my desk.
- Do some more e-mails and maybe check my voicemail.
- Instant message with a co-worker to find out the plan for lunch.
- Have a discussion about where to go for lunch and reluctantly agree to Long John Silvers
- Lunch
- Return from lunch - I am double-booked with meetings starting at 1:00 PM. I tell my project leader I won't be at the project review (I'm sure she can handle it without my help). Decide to go to the Six Sigma training meeting from 1:00-3:00.
- Review someone else's data for the first 1.5 hours of the meeting, give ideas, suggestions, ask questions, etc.
- For the last half hour of the training, I present my project and begin collecting ideas, questions, etc. on how to approach the test planning I'm working on.
- Return to my desk.
- Finish my weekly summary e-mail I started in the morning.
- Check e-mail.
- Sort through e-mails - deleting, saving attachments, reviewing documents, sending reminders to people on stuff I need them to do, etc.
- Respond to instant messages.
- Respond to urgent e-mails.
- Leave a phone message for the lab manager about a test request that is not getting completed in a timely manner (in my opinion anyway).
- Upload more documentation to the document storage system.
- Review simple circuit board drawing and send e-mail stating concern with design and drawing and how the concern can be fixed.
- Try to get my mind organized - make a to-do list for the things that didn't get done this week that need to be done next week, etc.
- Realize how late it is and that it's a sign of how lame my personal life is that I'm there so late on a Friday.
- Enter time into time tracking system.
- Check personal e-mail and take a quick gander at facebook.
- Shut down computer
- Leave work.
Monday
- Get to work around 8:15
- Boot up computer
- Prepare oatmeal breakfast while computer is booting
- Check e-mail
- Respond to urgent e-mail
- Decide I'm going to "crank through" doing documentation and project updates on a cost improvement project that has been lingering for months.
- Print out parts list drawings, mark them up, and give them to the documents guy so he can get that started.
- Call into conference call on the UL approval status of many different projects. Make a suggestion on how to more efficiently test one control to get IEC approval.
- Make sure schematic for the cost project has everything changed that needs to be changed, make sure the title block is correct and that nothing "weird" happened to the CAD project (sometimes weird stuff happens).
- Create official revision B schematic for engineering notice release.
- Work on generating documents for parts list changes so that the parts lists can be uploaded into procurement's tracking system.
- Have inner debate about most efficient way to accomplish this task and choose course of action.
- Get engrossed in this task, and then realize how late the hour is getting.
- Instant message lunch buddy to see what the lunch plan is - he is delayed in a meeting, so I decide to go home and eat leftovers.
- Return from lunch and continue with parts list work where I left off.
- Finish parts list file generation.
- Upload completed files to the parts and bill of materials system.
- Call vendor representative and leave a message about when I'm available this week to meet with him.
- Make sure ECAD files are all hunky-dory and load them to the network drive where the CAD guy can access them.
- Walk over to the CAD guy's desk and ask him to generate his part of the revision B documentation.
- Upload parts list files to document storage system.
- Get revision B documentation from CAD guy and review it. Give him the "green light" to send all Rev B ECAD documents to the document guy for official file system storage upload and engineering notice preparation.
- Have discussion with cube mates about the Super Bowl.
- Check e-mail - got a lot of them while I was working on this other stuff!
- Start sorting through e-mail.
- Call into conference call to discuss project status and schedule.
- After conference call, read through and respond to some more e-mail.
- Realize it's 5:00 and I need to be out of there to make it to racquetball on time.
- Enter time into time tracking system.
- Check personal e-mail, looks for comments on my blog, and check facebook quickly. Not much going on with any of them.
- Shut down computer.
- Leave work.
You might be sensing some themes: Oatmeal for breakfast, lots of e-mail and instant messaging, project management, meetings, documentation, and asking other people to do stuff for me and reminding them when they don't. :-) On paper it sounds kind of boring and tedious, and there is some of that. It's hard to describe the fun stuff like the challenge involved with doing my work though. If you made it to the end here, I'm surprised. A gold star goes to you for your reading fortitude! That's all I got folks. On the rare day I even get to go into the lab and do some testing, or I might actually get to
*gasp* design something!