So let’s say you just got hired by a company to be their newest software engineer. What can you expect to be doing? People will be very impressed with your new title. And they can guess you work with computers. If fact, they may have already been coming to you to help fix their own “technical stuff.”
Surprisingly many of these companies get started at 9 a.m. You might think it would be earlier. Don’t fear, likely someone came in at 5:30 a.m. An arrival at 9 a.m. is not shabby because you will probably work into the night.
Most offices will supply a kitchen with stocked goodies, both healthy and then not so much. Grab a coffee and a breakfast roll and head to your desk. The first thing to check is your email to see if someone is looking for you or there is an urgent matter. Make sure no fires were set in the middle of the night.
The next good idea is to check your technology news feeds. This business changes rapidly. See what’s going on out there in the world. When something new comes along to make life easier for a user, you want to know something about it.
Then it’s time to get down to business on whatever project you are assigned. As a rookie you will most likely be working on projects that get broken down into smaller working components. You and your teammates may spend two weeks writing code for an environment. The third week you can test the changes, fix bugs then deploy the features.
When this three week stint is done you will sit in meetings to discuss the next project. Your group will see how difficult each element is and then the project manager will prioritize and assign tasks and due dates. Critical areas will need to be covered first.
When each project completes and it is deployment day you may be assigned to let things go to live servers at night when there are few users and disruptions. You may be ending your day at 9:00 p.m. or later.
Sources Cited: http://www.madex.com