From 11:00PM PDT on Friday, July 1 until 5:00AM PDT on Saturday, July 2, the Shmoop engineering elves will be making tweaks and improvements to the site. That means Shmoop will be unavailable for use during that time. Thanks for your patience!
We have changed our privacy policy. In addition, we use cookies on our website for various purposes. By continuing on our website, you consent to our use of cookies. You can learn about our practices by reading our privacy policy.
© 2016 Shmoop University, Inc. All rights reserved.


The stress, while not horrendous, is still rather high. The deadlines are tight, the money placed behind an Engineer's project is astronomical, and the fact that someone is going through your garbage every now and then to be sure you're loyal to your employer can all add up. Government oversight committees are notorious for wanting quick results and do not deal well with disappointment.

This isn't even to mention the fact that the things a Defense Engineer develops will likely lead to people dying. It may be a lone terrorist or it could be an entire village that harbors the enemy with "acceptable collateral damage," but chances are pretty good that someone somewhere will bite the big one because of an Engineer's work.