I'd love to see a wide sampling of StackOverflow users as I feel that you all tend to represent developers with higher than average passion for your craft. Thanks!

+1  A: 

40-45 at work, another 5-10 on my own projects at home.

Although I am just an intern and I don't get paid overtime. I do software development because I like it, but if I'm not into the project (like now), I won't give extra. At my last dev job, I worked 50+ hours a week without overtime because I loved the project.

Thomas Owens
+1  A: 

55-60 on a busy (normal) week. 10-15 of those might be working from home though.

Geoffrey Chetwood

40-45 hours at work , 10-20 on my own fun at home.

pete blair

45-50 hours at work, some more at home but not with a predictable pattern - can be either on extra work or on my own projects.

Simon Steele
That's hours excluding a lunch hour by the way, which I don't often take :)
Simon Steele

45-55 per week at the workplace, and typically 1 hour per night at home (wrapping things up, doing tasks that must be done during non-peak hours). During times of crisis or special circumstances, up to 70 at work, and sometimes 18 hours a day (typically only for massive deadlines, and only for the last few days).

I feel like my co-workers and myself balance well the ease of coming and going as you please with the need to get things accomplished in the timeframe that they should be. Leaving early, coming late, and taking long lunches is well offset by willingness to stay late, come in early, and do whatever it takes to get the special cases worked out.

Michael Runyon
Are you able to take extra vacation days off after those 18 hour days?
Troy DeMonbreun

For my employer, about 45 hours a week. For myself, it used to be an additional 15 or so.

Ever since we had our first baby, 2 mos ago, it has been basically zero for myself. I expect it to pick up again in a few months though. I have several projects that I'm itching to start, along with several books I want to read.

+3  A: 

40-5, like most people. I'm lazy, so I try not to do anything stupid that will require me to go much over 40...

Along the lines of "Do No Harm", woud that be "Do No Stupid"?
Troy DeMonbreun
+1  A: 

About 45+ hours a week. Because I work for my own company, I work both from home and a clients office. I seem to have figured out how to make all the programming work related to my business, and most of it billable.

Darryl Hein
+1  A: 

40 hours a week on average at work. I then spend 10-20 hours a week messing around and reading in my spare time. I occasionally use work projects in my personal time efforts, but I don't consider myself to be on the clock.

Daniel Auger
+5  A: 

Almost exactly 40. We don't get overtime, and I don't work for free.

I do work on some stuff at home, but that is for me, and more fun than work.

Adam Lerman
+1  A: 

In the past, working for startups I worked anything from 50 to 85 hours a week. I made it into a rule on this job to work only what I am paid for. Good planing and good project management enable our team never to be pressed in time and never to be late for a dead line. The book "Getting things done" was an eye opener in that regard.

+1  A: 

About 84. But then I work for an early stage startup.

Wow, give this man more stock!
Troy DeMonbreun
+2  A: 

I am expected to put in 35 (union rules) We also get overtime

+1  A: 

37.5 because unless requested to work overtime I don't get paid at all for anything extra. The CEO doesn't want anyone working overtime on a regular basis so we don't.

At home I spend another 10 - 15 hours a week practicing languages that we don't use at work by tooling around with ideas or things like project euler.

Wow, such a directive straight from the CEO. Sounds like they appreciate good balance in their life and wish to respect others'.
Troy DeMonbreun
+2  A: 

40, and I put 5-10 hours into my own interests at home. I have a 1 year old so had to cut back on the excessive work hours.

Brian G
Good call. I'm sure your child will one day reflect and appreciate that sacrifice.
Troy DeMonbreun
+6  A: 

too much!!

if(!self.isAtWork()) {
    goto: WORK;
So, maybe Goto's are harmful afterall. ;-)
Troy DeMonbreun
+1  A: 

Depends. During the technically satisfying times I'll put in 50+ per week without really thinking about, but during the more mundane support-oriented times I'll put in a long 40 with some time at home for satisfying work.

Mike Reedell
There's something to be said about being "in the zone".
Troy DeMonbreun
+2  A: 

36 in the office, my boss kicks us out at 5 makes me so mad.

about 20-30 at home.

Sara Chipps

Preparing for launch the last three weeks, about 100hr/wk. We're very close though and it's all very exciting :D

Eric Willis
Ouch. Tell me you work for NASA and that launch is the space shuttle. ;-) Seriously, though good luck and good profit!
Troy DeMonbreun
It's worth it. I love it :)
Eric Willis
lucky lucky man!
+1  A: 

Yeah, 40-45 right now, a little more when I'm on Technical Support (irate E-Mails from customers). As many of the respondents have indicated, 10-20 more hours on stuff at home (openSolaris with ZFS pool acting as my new NFS server, memory upgrades, network upgrades (yay Gigabit), finally upgrading my main box to F9 from F7 .. and list goes on).

My time may creep up in the future when I start to do more support, but it will also more around to the Somewhat More Inconvenient section of the clock, like the part where I'm normally sleeping.

Being a windows developer, I only upgrade from an F7 to an F9 when I fat-finger on the keyboard. :-)
Troy DeMonbreun
+1  A: 

Being stuck on a fairly interesting project for some time it is something like 50-55 hours on average. That's time sitting in front of the work PC - so it includes certain procrastination. I constantly fight with it ...

Tomas Pajonk
Yeah, I think the more hours one works in a week, the harder the fight against procrastination and distraction.
Troy DeMonbreun
+1  A: 

I'm still in college, so only 15-20 hours a week at work.

+1  A: 

I've put in up to 100/hrs a week, though I average around 50.

And I'm salaried :(

That's the thing about salaries - they tend to favor the employer. It's okay for the employee to work 20 hours more than the required work-week hours, but not 20 hours less than.
Troy DeMonbreun
+3  A: 

Right now I am averaging right around 41 hours a week. When a major project deployment was being done I was averaging 48 hours, peaking at 60 hours.

As for the employer - it is a major company so the "spikes" due to a project being deployed tend to be minimized a lot more than smaller companies.

+23  A: 

I don't go over 40. Balance in life is important.

Sameer Alibhai
I agree. If you have to work overtime, chances are you're doing something wrong (planning, implementation, whatever).
Garo Yeriazarian
I agree, but if the overtime is my fault (i.e. being held to an estimate I made with a reasonable amount of wiggle room) then I put in the time.
I'll go over 40 when I feel that's the right thing to Get The Job Done because that's part of being a professional, but I don't do it regularly -- only in a crisis such as discovery of a critical bug, an immediately looming deadline, etc.
Bryan Oakley
+1  A: 

40-45 at work

+15 or so learning on my own time at home

+5-10 Other projects

George Mauer
+1  A: 

Exactly 40, and I wouldn't stay anywhere that expected more unless I received some kind of royalties or owned part of the company. :)

Boundaries or Benjamins, I guess you could say. :-)
Troy DeMonbreun
+21  A: 

I average around 50 hours per week, but it does vary greatly from week to week.

As a senior manager, the developers who work for me put in at least 5 hours more than they are contracted to each week, many put in an extra 10 or so. And, I wish they didn't. Some of them put in extra time because they are stimulated by their jobs, and I am glad that is the case. However, others put in extra time because they perceive that they have to "keep up appearances". But, they don't need to.

  1. From time-to-time, a few extra hours are needed to meet deadlines or fix serious problems, but if everyone is already working as many hours as possible, then they don't have further free time to "donate" to the company. It is more important to me that developers are flexible than to be found at the office all hours of the day.
  2. Doing a couple of extra hours doesn't greatly impact the amount of productive work that is done. I strongly believe that developers are only highly productive for three or four hours of the day, Joel had a post about being unproductive. But I think it goes beyond this. Someone just can't concentrate on hard tasks for more than a few hours a day (well, I can't!) and writing good code is hard.

In my mind, the perfect developer would never routinely work longer than their contracted hours. If they have free time and enthusiasm then, great, they can work on a personal project and become a better developer as a result. That would be the win-win scenario.

Indeed, the peer pressure from those who work long hours can have more influence on those who'd prefer not to due to basic fears about job security in a day and age where company loyalty (to it's employees) is very low.
Troy DeMonbreun
I couldn't agree more. As a developer, I'm productive for a maximum of around 4 hours.
Have you *told* them they don't need to?
+1 - I agree. I'd rather have the guys on my team be flexible instead of already maxed. That really counts when unexpected deadlines are dropped on your team...
Mat Nadrofsky
+3  A: 

Love this question!

I put in exactly 40 most weeks, which includes 5 hours of lunch :) On weeks when a deadline is coming and im worried about it, I wont hesitate to go 50+, but so far this has rarely happened...

+3  A: 

"If you do what you love, you'll never work a day in your life."

I am not sure I agree hours you work equate to passion, but if you're going to do over 40 per week I suggest the following.

Never clock watch.
Never stop yourself if you are "in the zone" (if you can help it).
Never drink a Diet Monster right before you're wrapping-up and think you are going straight to bed, or you'll dream in an infinite loop.

Personally, I work enough that if I replaced writing code with drinking alcohol my friends and family would put me on that Intervention show. If I don't have an IDE in front of me, I am sketching in pseudo-code on napkins at dinner.

Ian Patrick Hughes
+1  A: 

Some weeks I put in just 40, but most of the time I get in more like 45. In very busy weeks I have put in over 60 -- something my boss frowns on, as he is a stickler for getting what needs to be done in 40 hours.

+2  A: 

38 hours at work and about 15 to 20 hours doing consulting at home.

Timothy Lee Russell
Heck yeah, if you're gonna work overtime, make sure you get paid for it.
Troy DeMonbreun
+3  A: 

192 hours. Yeah, that's eight days a week. That's how much I love programming and the Beatles.

Even Mien
Your work ethic is astounding!
Troy DeMonbreun
+1  A: 

~43 where we have a policy about getting an earned day off each month if one works an average of 42.5 hours a week. Course there are more hours spent in the office as there are breaks and lunch to factor in.

JB King
+1  A: 

I average 32 to 38 hours a week. My company used to call itself Agile, but has executed it so poorly it can only be described as Dilbert Incarnate. I can rarely motivate myself to stay there the full 8 "net hours".

  • "Net Hours" refers to ((Gross Hours) - breaks), as they don't let contractors charge their break time. Thus I end up being there for an extra 5-10% uncharged time.
+1  A: 

My contracted hours are 37.5 and I pretty much keep to that. I have a family that I don't want to neglect.

+1  A: 

Between 50 - 60 hours a week, not including the 2 1/2 hours of travel (42 miles each way). Hey.. that might be an interesting follow up; how far do you travel to work!

+1  A: 

37.5 officially, but 40 or 41 since I accepted a special extra side project.

+1  A: 

40hrs. They don't pay me for any more than that :)

Kevin Tighe
+1  A: 

I usually put in between 40-45. I generally think that having to work more than that is caused by either poor estimation skills of the developer or a manager with a lack of cajones. If I already have tasks on my plate for a certain week that I estimate will take me 32 hours to complete (20% for support), my manager should be able to push back on any additional work (or re-prioritize). Now, if it is something I am really enjoying, that is a different story...

Todd Friedlich
+1  A: 

35-55 of actual work

I've using pomodoro technique to time box my work to 25mins and I'm logging what I do each day

I average 35h-55h for 6 days of actual work with sunday off

this includes

  1. starting at 530am
  2. finishing at 10pm

this excludes

  1. breaks, meals, twitter, stackoverflow, blog reading etc..
  2. 2h commute 5d/week

I've had weeks of 65h's but I burn out and follow it up with an <35h week. It means that I can gain 10h one week but have to pay it back with at least 20h the next week.

My context is

  1. I contract during the day
  2. I work on a startup mornings,evenings and weekends

My goal is to trend my productivity so I can find a sweet spot between the hours I sit at a desk and ammount of work I get done.

Scott Cowan
+1  A: 

42 (hours a week)

+1  A: 

40 h/week. I do not want be a foreigner to my kids.