How many hours per week do you work?
-
for me i work 54 hours a week and maybe more, it depend if there is an issue that require time to solve or everything is OK
-
@IT-ADMIN said:
@coliver said:
@DustinB3403 said:
Anywhere from 40-55 hours a week depending on how busy things are, currently things have been pretty slow. So we've been taking more time for ourselves.
I just started a new job (on week 3 right now) so my hours are fairly limited probably 35-40 a week. I think that will change as I get more responsibilities here.
is it so easy for you to find a new job ?? this is great
Easy? Kind of... I wasn't really looking when I applied and when I was offered an interview I was surprised.... even more so when they offered me the job.
-
you guys really have more opportunities in US, which helps you getting strong experience
-
for us it takes 100 times before you can even thinking of resignation, it is really hard to find a new job
-
@IT-ADMIN said:
for us it takes 100 times before you can even thinking of resignation, it is really hard to find a new job
It depends on the region, area and density of available and qualified personal.. There were times which I spent 6-14 months looking before I was fortunate enough to land something. It is easier to find a job when you have one,.. that I know.
I wasn't looking really when I started talking the MQ back in December but spent some time talking back and forth with her. And when a chance came up at the end of March, I took it. Working with MQ and NTG has been great.
As for hours, I don't really keep up with it,.. Today I was in before 8 and will likely be around till nearly 8 tonight. Though there will be a period I am doing other things,.. I just enjoy being around here and the good people I work with.
-
I only have to put in 40 (to get benefits)... I rarely go over 45. But I get paid overtime, so they don't expect me to do crazy extra hours. And my schedule is somewhat flexible, I do 4x 9 hour days, then a half day Friday (or any other day of the week if I need to do something).
-
So what do you all think of the Swedish idea of only working 6 hours a day, 5 days a week. You work less hours, but the idea is you work more intensely (so no browsing MangoLassi at work, for example), so you still get as much done, but in less time.
-
I work 60+ hours a week every week. I am currently in a "I am all you get" role for anything that runs on electricity. Both myself and the company I work for acknowledge this is a risk and we are trying to fix it; however, it is a slow process.
Note: I do NOT wear this as a badge of honor.
-
It is hard to say. I used to be over 100 hours a week. Then dropped to 80. Was doing well in 2010 - 2013 with keeping that reasonable, then back up again in 2014. This year I dropped to 40 until recently. Now I'm far more Swedish. It is hard to determine how many hours I work because of the kind of work that I do, but not that many hours anymore.
-
@Carnival-Boy said:
So what do you all think of the Swedish idea of only working 6 hours a day, 5 days a week. You work less hours, but the idea is you work more intensely (so no browsing MangoLassi at work, for example), so you still get as much done, but in less time.
I'm ready for the US to adopt this policy... at least for IT. I could easily trim 10 hrs of "dicking around" time a week.
-
One thing that is a big deal is whether your job is one of productivity or one of availability. If your job is engineering or decision making making you a productivity worker, then going to 20-30 hours a week is found to be ideal for getting the best work out of you.
If, on the other hand, you are an availability worker like a system admin, helpdesk tech or similar then cutting hours reduces your value to the company by making you less available.
So it really depends. When I was at CitiGroup they offset this by having me be always on call as a system admin but only in the office for 20 hours a week. There are ways to make availability workers valuable without making them "work" too much, but you have to be more creative than just reducing hours.
-
@scottalanmiller said:
One thing that is a big deal is whether your job is one of productivity or one of availability. If your job is engineering or decision making making you a productivity worker, then going to 20-30 hours a week is found to be ideal for getting the best work out of you.
If, on the other hand, you are an availability worker like a system admin, helpdesk tech or similar then cutting hours reduces your value to the company by making you less available.
So it really depends. When I was at CitiGroup they offset this by having me be always on call as a system admin but only in the office for 20 hours a week. There are ways to make availability workers valuable without making them "work" too much, but you have to be more creative than just reducing hours.
How do I get this????!! I am in the office 40-50 hours and then on-call for the other 150 or so hours
-
@donaldlandru said:
How do I get this????!! I am in the office 40-50 hours and then on-call for the other 150 or so hours
Um... work for a more enlightened company that takes its IT more seriously?
-
I generally put in 40-45 billable hours a week. Billable hours = hours I get paid for.
I also put in 5-10 hours of time doing things to improve my skills for various pieces of our business. This is not paid for directly.
-
40, I work 40 hours and then have a hard cut off. I came from a company that used to push me 45-55 every week to get their money's worth. I am much happier overall now than I was before, and makes me more likely to pick up skills at home and learn again vs coming home drained and wanting to unplug from all tech.
-
@s.hackleman This is where I am at too. I was the on call guy... and boy did I get the calls... My new employer is great and being just one of the minions low on the totem pole, I don't have to worry about too much like that.
-
I used to bust my butt and do tons of OT - when I stopped and everything kept working....
37.5h/wk, occasionally an extra hour here or there, but it's rare.
-
4 10's, and then I have my own business so I work in the evening until about 9-10 and then usually doing stuff for that on Friday as well.
Plus, I feel like a moron reading stuff on here so I'm always trying to learn things.
-
@johnhooks Try, not! Do, or do not. There is no try! (sorry... I couldn't resist)... But seriously, I learn more by doing, so when somebody says hey I want to do $project -- If I have the resources in my system at home to set it up myself, then I do so.
-
@dafyre said:
@johnhooks Try, not! Do, or do not. There is no try! (sorry... I couldn't resist)... But seriously, I learn more by doing, so when somebody says hey I want to do $project -- If I have the resources in my system at home to set it up myself, then I do so.
Lol, I'm the same way. I have a hard time learning if I don't do it myself. Watching other people do it helps (much better than reading) but doing it is always the best for me. I just never feel like I'm not behind on stuff (if that makes sense).
I wish I was paid based on the number of VMs I've created and destroyed in doing projects.
