FormerHangie
En-Route
What's your job like? Not so much what is your job, but what is a typical day like? Are you in an office most of the time, or on the road? Steady hours or variable? Anything you particularly like or dislike? Any cool perks like sports tickets or free travel?
I'll start. Ostensibly, I'm a software developer, but when I last asked what my job description is, I was told "everything else". Today was a good example. I got in around 8:30, and faced a stack of helpdesk tickets, left to me by a former employee who had resigned. I was sorry to see him go, but he was offered a position for a little more money with better growth potential than we could offer him, and I encouraged him to take it. He was doing a lot of reporting, something I'm not that practiced at, so I'm having to force feed myself the reporting tool while i try to fix some of the issues. I spent the early afternoon dealing with some data quality issues, and then had to go over to our warehouse to do an update on a computer that will be running UPS WorldShip, which is used to integrate our internal shipping process with UPS. So, I spent zero time actually developing software today.
I'm an office dweller, I've been there for 18 years and have never had to travel. That's fine with me, business travel isn't usually much fun, particularly if you do an IT function, it mostly means very long days, but it would be nice to get out sometimes, and that hardly ever happens.
What's good about my job? Software development is a creative process, and it's satisfying to see something you create doing thing that are important to the company's success. What's not to like? If you're the kind of person who likes to feel that he's done at the end of the day, you wouldn't do well in this position. I could work 10 hours a day six days a week and still not be caught up. The worst part of my job is trying to keep on schedule, which really is impossible since I have lots of troubleshooting of issues that pop up during the course of any substantial project. I really hate being asked to give a "rough guess" as to how long something will take without being given time to plan the task at hand. That's kind of like asking a builder how much it will cost to build a three bedroom house, he'll want to see the plans first. In our case, we have to write the plan, but many times management wants some idea how big a project is. Fair enough, as long as they don't ask me to stick to the rough guess if the actual plan shows much of a difference.
Perks? Well, I stayed employed during the Great Recession, and that counts for a lot. Our project is an educational one, and we are allowed to take a certain number of courses per year. Unfortunately, most of our product line is aimed at people who have struggled with the traditional education system, and are looking to get an entry level certification in an industry, or to finish their high school program, so it's not of any value to most of us. It's nice to be home every night as well.
I typically arrive around 8:15 and leave at 5:30 or so. Today I was there until 6:45 because I needed to work on something that our shipping department uses, and had to wait Every third week we have a release, which starts at 11 PM and usually ends a little after midnight, and every quarter our servers are patched, which means a few hours on Sunday morning.
What bothers me the most? Every few years I get handed the project from Hell, that requires very long hours with little extra compensation. There was one year where I put in more than 400 hours of overtime and lost vacation, and got all of $2500 (gross) for it. There was one January where I worked the entire 31 days. Yuck. Also, we're a pretty small department trying to cover a business that's open 7A -11P five days and 8A - 7P on Saturday, so sometimes you get called in on what's supposed to be your time. Also, it's tough to keep up with the professional development needs, We're supposed to get one hour a week for self study (we get a subscription to Pluralsight), but it's not enough, and quite often we are too busy to take it. Having to pick up a new tool on the fly isn't much fun either.
I would say my situation is better than most people's.
I'll start. Ostensibly, I'm a software developer, but when I last asked what my job description is, I was told "everything else". Today was a good example. I got in around 8:30, and faced a stack of helpdesk tickets, left to me by a former employee who had resigned. I was sorry to see him go, but he was offered a position for a little more money with better growth potential than we could offer him, and I encouraged him to take it. He was doing a lot of reporting, something I'm not that practiced at, so I'm having to force feed myself the reporting tool while i try to fix some of the issues. I spent the early afternoon dealing with some data quality issues, and then had to go over to our warehouse to do an update on a computer that will be running UPS WorldShip, which is used to integrate our internal shipping process with UPS. So, I spent zero time actually developing software today.
I'm an office dweller, I've been there for 18 years and have never had to travel. That's fine with me, business travel isn't usually much fun, particularly if you do an IT function, it mostly means very long days, but it would be nice to get out sometimes, and that hardly ever happens.
What's good about my job? Software development is a creative process, and it's satisfying to see something you create doing thing that are important to the company's success. What's not to like? If you're the kind of person who likes to feel that he's done at the end of the day, you wouldn't do well in this position. I could work 10 hours a day six days a week and still not be caught up. The worst part of my job is trying to keep on schedule, which really is impossible since I have lots of troubleshooting of issues that pop up during the course of any substantial project. I really hate being asked to give a "rough guess" as to how long something will take without being given time to plan the task at hand. That's kind of like asking a builder how much it will cost to build a three bedroom house, he'll want to see the plans first. In our case, we have to write the plan, but many times management wants some idea how big a project is. Fair enough, as long as they don't ask me to stick to the rough guess if the actual plan shows much of a difference.
Perks? Well, I stayed employed during the Great Recession, and that counts for a lot. Our project is an educational one, and we are allowed to take a certain number of courses per year. Unfortunately, most of our product line is aimed at people who have struggled with the traditional education system, and are looking to get an entry level certification in an industry, or to finish their high school program, so it's not of any value to most of us. It's nice to be home every night as well.
I typically arrive around 8:15 and leave at 5:30 or so. Today I was there until 6:45 because I needed to work on something that our shipping department uses, and had to wait Every third week we have a release, which starts at 11 PM and usually ends a little after midnight, and every quarter our servers are patched, which means a few hours on Sunday morning.
What bothers me the most? Every few years I get handed the project from Hell, that requires very long hours with little extra compensation. There was one year where I put in more than 400 hours of overtime and lost vacation, and got all of $2500 (gross) for it. There was one January where I worked the entire 31 days. Yuck. Also, we're a pretty small department trying to cover a business that's open 7A -11P five days and 8A - 7P on Saturday, so sometimes you get called in on what's supposed to be your time. Also, it's tough to keep up with the professional development needs, We're supposed to get one hour a week for self study (we get a subscription to Pluralsight), but it's not enough, and quite often we are too busy to take it. Having to pick up a new tool on the fly isn't much fun either.
I would say my situation is better than most people's.