Oh, that’s interesting, because I am 16 and exploring college majors based on the type of career I think I might go for, and I have been speculating becoming an actuary since I am strong in my mathematical ability and love dealing with and using statistics in my everyday life and plan on taking AP Statistics next year (senior) after AP Calculus this year.
I heard somehwere that you have to work long hours as an actuary, but I guess they were wrong.
What major did you take to become one? And how’s the job in general?
The most is a hundred, and that typically involved some system problem, so it was me and some co-workers sitting by an intercom talking to programmers intermittently for two days in a row. Not grueling, but still sucky. Once we were behind on a client and I did an entire week of double shifts to catch up their account. Really wasn’t so bad.
At Dominos, 60 hour weeks were the norm for managers. Your shift was typically 10 hours (4 p.m. to close/clean-up) and you always got called in on one of your days off for some disaster. Much more of a hassle at the time.
Domestic Operations - Flood Fighting and I was the only media contact for the first four days. Not something I would want to do on a regular basis.
That, or on training, Infantry Phase 1 - week in the field, week out to recover (classroom). To quote my Sgt, “We can’t beat you anymore, can’t starve you anymore, so the best way to stress you out is to deprive you of sleep and work you.”
[QUOTE=R3d Anonymous]
I heard somewhere that you have to work long hours as an actuary, but I guess they were wrong.
[/quote]
You certainly have to work long hours studying to qualify as an actuary. The job itself, in my experience, doesn’t require excessive hours, though it can in certain situations e.g. valuation actuaries at year end.
I did an undergraduate degree in actuarial studies straight out of school, and then studied part-time for my professional exams once I was working full-time.
I’ve been working full-time for nearly 30 years now and I’ve found it interesting and enjoyable. It’s challenging to qualify; very well paid once you do qualify; has skills that are easily transferable around the world; has options for both technical and managerial roles; and a very low unemployment rate.
As an exempt engineer in Silicon Valley in the mid-1970’s I would often work 40+ hours on a weekend trip, if measured portal-to-portal, and still be expected for the usual 40+ weekday hours(*), all for the base 40-hour salary. There were many engineers in that position. I didn’t mind – I had no social life and was working for the thrill of it!
So that would be 80+ hours, since contractors and non-exempt employees bill portal-to-portal for trips. But my paid hours never exceeded 40. OTOH, if unpaid hours count, time spent on my work-like hobbies should count and I’d get a very high number.
(* - A consolation was that no one complained when I sauntered in just before lunch. More than once I was woken up at home by a phone call: “Don’t bother coming to work today. Just head to the airport, ASAP.” Once I drove to the airport, unpaid, to be ready to fly quickly if field developments required my presence and, after phone calls, I returned home.)
Thinking about this now, the unpaid work surprises; does this happen these days? Engineers with families resented it greatly, but jobs were hard to come by. As I said, it didn’t bother me – I was young enough to find it thrilling! :smack:
I agree. The granularity of the poll is much too coarse. OP, were you too lazy to break it down by minutes?
I once had a job that required me to remain at work until all the work was finished. I remember one particular week when I worked around the clock without going home more than a few times. I’m guessing 130 hours. And no overtime pay.
Does being able to sleep not count? I routinely work 30+ hour call shifts where I can sleep, but am woken up several times per hour to answer pages or admit patients from the ER. Can I not count that at 30 hours then?
It’s been a long time so I don’t remember the precise number of hours but my worst week was a desperate flight around the country to save a dying project.
It started out with a problem occurring on a Friday night, spending 24 hours working at the office with the team for a solution and then a team of us splitting up and flying from site to site to apply the fix. It was a nightmare of flights, holding tightly to my laptop between flights and buying clothes along the way as none of us had time to go home and pack. Network speeds at the time were insufficient to run the fix remotely and we had no onsite technical support, just admins whose instructions for backups had to be amended several times to add lines like “remove the plastic from the backup tape before inserting it in the drive”
By Thursday I had visited 30 sites in 7 cities and all of my sleep had taken place on planes or in the back seats of taxis. One person on the team had been designated to skip the traveling and keep the corporate travel department on track with getting us where we needed to be. She slept under her desk in the office until we were all on our way home. It was a nightmarish week but we were all well rewarded for the effort, particularly since it was determined to be a fault the customer introduced to the system so we were able to bill them for each and every hour. I’m pretty sure the account manager added an emergency multiplier to the rate and they paid it. I’m fairly certain that he billed them 168 hrs for that week for each of us, but I think I actually logged a couple hours per day off.
Bonus for that project that year was more than all my other projects combined.
Wouldn’t the poll be more useful if it used hour ranges.
Anyway, I’m self-employed, which means I couldn’t give you more than a range anyway. It’s not like anyone is clocking all of those hours to determine overtime compensation. During tax season, I have plenty of weeks that are basically 12 hrs/day x7 days/week, so at least 84 is pretty common during the tax season. (In fact, this week might be one of them). I went ahead and answered 100 hours, though. It’s a pretty good estimate of what was probably the max.
However, I should point out that I count my hours differently from many people. If I work 8 am to 6 pm, then stop for two hours for dinner and continue on from 8 pm to midnight, I’m counting that as 14 hours. I know that many people would call it a 16-hr day.
Several years ago, I moved the company datacenter from one location to another. The move began at 6:00 PM Friday evening, took 24 hours of non-stop work, and was preceded by a very busy work week (mostly prepping for the move). I think the total hours from Monday to Saturday was +/- 80, with the last 36 hours being uninterrupted by any kind of break.
As a consultant, it wasn’t uncommon to do something like work 5 consecutive 10-12 hour days, and then put in half-days over the weekend.
Or something like MTWT: 13-15 hour days, then maybe a 8 hour day on Friday, and then work a few hours on Saturday and Sunday, and then do it over again on Monday.
So 70+ hour weeks weren’t really uncommon when a project was hot, or coming down to the wire.
What sucked the most is that due to the fact that our moron managing directors wouldn’t let us bill for computer run time, we’d often put in a 13 hour day, by coming in at 8, spending an hour setting up the e-discovery or forensics software, and then spending the next 7 hours twiddling our thumbs waiting on the computers to get done, and then spending from 4 pm to 9 pm actually working on the results. So we’d put in a 13 hour day, but only be able to bill our clients for 6 hours of it.
During Sandy it was 16hrs on & 8hrs off (“eating, sleeping and commuting are part of your 8”)… 7 days a week… until told otherwise.
“Yes, I Know you don’t have power. No, my family doesn’t have power either. I’m here so we can try to All get our power back on and as quickly as possible.”
I did 126 hours - 18X7 for one ridiculous week to get some stuff done and make a point.
My job now involves some crazy hours, but things are very flexible, I can work from home and a a good portion of my hours are just “on duty”. The last few days have been pretty crappy though, with multiple calls at night and a few hours of work on Saturday and Sunday and a 4:00am start today. Hell, it’s a living.
I worked in the front office for a minor league baseball team several years ago and the average day when the team was in town was 9 a.m. to midnight. If the team was on a ten game home stand you worked 10 straight 15 hour days. Towards the end of the season a day off was 9 to 5.
I normally started the day by cleaning the seating area and rest rooms then moved on to prepping the clubhouse for the arriving players ( they normally showed up for a 7 p.m. game by 2) then starting getting the concession stands ready for the game. Worked the game which normally ended around 10 then locked up the stadium, counted the cash for the nightly deposit then left which was around midnight.
I laugh when I hear people say that they would kill to work in pro sports, only if they knew the serious amount of hours you have to put into the job for the insane low pay.
Oh yeah you will get the 5 a.m. call to drive to stadium to pull the tarp over the infield.
It’s been almost 20 yrs, but when I was working for E*Trade in it’s early start up days we worked an awful lot of hours. I can’t remember the exact number but I’m sure some weeks it was over 100.
One location I worked was a rotational assignment so I worked 28 days in country and then flew home for 26 days off. The official work day was 5am to 6pm Mon through Sat, and 5am to noon on Sun. My “weekend” was Sunday afternoon and evening. Since there was plenty of work to do and few distractions, most everyone would eat dinner and then return to the office ( which was close to the accommodation block ) and work several more hours before heading back to your room. Added up, a typical work week was usually 90 to 100 hours.
