Why Nobody Tells You What a 70-Hour Week Actually Does to Your Life
I've seen the salary offers. Six figures, sometimes well into seven figures, dangling in front of people who think they're making a rational choice. I've been on the other side of hiring for these roles too. What the offer letter doesn't show is the erosion that happens over eighteen months. Not the dramatic burnout story you read about on LinkedIn. Just the slow, boring reality of missing your kid's third grade play because there was a server migration that couldn't happen during business hours. Or the Tuesday night you spent debugging a deployment pipeline instead of your actual job, because that's what the salary is paying for. Here's the thing most people miss when they're calculating whether the numbers work. They divide the annual salary by standard full-time hours and get a comfortable hourly rate. They don't factor in the compounding costs. The dinner dates that become takeout because you got home at eight. The gym membership you stop using after month three. The relationship strain that shows up as one more thing you have to mentally manage even when you're technically "off." These aren't abstract. They're line items in your life budget that nobody puts in the offer letter. I once took a contract role that paid significantly above market rate for a forty-hour-week position. The expectation, unspoken but absolute, was closer to sixty-five hours. I lasted eleven months. The specific problem that broke me wasn't the volume of work. It was the context-switching penalty. When you're working that many hours, you're never deep in any single thing for long enough to get into flow state. You're constantly recovering from interruption. I calculated it once and realized I was spending roughly two hours per day just regaining focus after being yanked between tasks. That's fourteen hours a week of my life, gone to overhead. The salary looked good on paper. The effective hourly rate after accounting for that switching tax was barely above what I could make working forty hours at a normal company.
The workaround I ended up using was brutal but effective. I stopped trying to do everything and started negotiating explicit scope boundaries. I said to my manager: here are the three things I will own completely. Everything else goes into a backlog and we prioritize from there every Monday morning. He pushed back for two weeks. Then he agreed because he was drowning too. Productivity actually went up because I could finally do deep work during the hours I had. The lesson I took from that is that the 70-hour schedule only works if you protect your actual working hours from the ambient chaos that fills every empty space. Without that protection, you're not being productive. You're just being busy at an expensive rate.
What the Math Actually Looks Like
Let's talk numbers without the gloss. A $200,000 salary in the United States, after federal taxes, state taxes depending on where you live, FICA, health insurance premiums that rarely shrink no matter how much you pay, 401k matching that you might not even use because you're too tired to think about it — you're looking at roughly $3,800 to $4,200 a month take-home. Divide that by 70 hours a week over 52 weeks, and your real hourly wage lands somewhere between $13 and $14.50 an hour. Not $96 an hour like the sticker price suggests. $13 to $14.50. For work that leaves you with no energy for anything else. I've sat in bars with people making $250,000 at hedge funds and tech companies who couldn't remember the last time they ate a meal without looking at their phone. They weren't miserable in a dramatic way. They were just... flat. There's a difference between unhappy and depleted. Unhappy you can fix. Depleted you can only recover from by stopping, and most people in these roles don't stop until something breaks.
Get the Full Details
When It Actually Makes Sense
There are scenarios where this trade is rational. The first is temporary. You take the role for eighteen to twenty-four months, you maximize your savings, you explicitly plan an exit, and then you leave. I've done this twice myself. Once to pay off graduate school debt, once to build up a runway for a business venture that never materialized but which I felt better about having the financial cushion for. The key word is temporary. The brain adapts to high hours in a way that makes you forget what normal feels like. You need an external deadline to remind you that this is a phase, not a lifestyle. The second scenario is equity-heavy compensation where the numbers only work if you stay long enough for the vesting to matter. If you're getting significant stock options or RSUs, the calculation shifts. You're not selling hours. You're selling time at a discount in exchange for upside that may or may not materialize. I've seen people get vested out of $400,000 in stock and then watch it drop 60% the following year because the company missed earnings. The salary compensated them for the stress. The equity didn't compensate them for the risk. Those are two different problems. The third scenario is early career when learning velocity matters more than work-life balance. If you're going to be working 70 hours anyway, you might as well be working on problems that make you significantly more valuable. I mentored a junior engineer who took a startup role at 26 specifically for this reason. He was shipping code, talking to customers, debugging production incidents, and writing architecture docs within six months. By 28 he was making twice what he would have made staying at a big company doing standard hours. The trade worked for him because he was investing the extra hours in skill acquisition that had a clear payoff. It won't work for everyone. Some jobs just give you more work, not more growth.
The Hidden Bottleneck Nobody Talks About
After working in hiring and management for over a decade, the pattern I've observed consistently is that 70-hour weeks don't produce 70 hours of productive work. They produce about 40 to 45 hours of genuinely high-quality output, spread across a much longer timeframe. The rest is presence theater. Sitting in meetings that could be emails. Re-doing work because you were too exhausted to get it right the first time. Being too drained to make good decisions in the evening, which leads to mistakes that cost two days to fix the following week. I managed a team once where two people consistently worked 60+ hours and produced mediocre results, while three others worked 45 hours and shipped everything ahead of schedule with higher quality. The high-hour group was respected for their "commitment." The high-output group was trusted with the important work. This isn't a rare pattern. It's the default pattern once you remove the cultural pressure to perform busyness. Most companies don't realize they're paying premium salaries for performative hours, not actual output.
How to Know If You Should Take the Deal
Ask three questions before you sign. First: what is the explicit end date or exit strategy? If the answer is vague, walk away. Second: what does the actual day look like for someone in this role right now? Not the job description. Ask to shadow someone or talk to someone who's been there six months. The first month is always better than month six. Third: what happens if you say no to working late on a Thursday? If that question causes visible discomfort in the person answering, that's your answer. I've also learned to track my effective hourly rate for the first three months of any demanding role. Not to complain, but to get data. Write down every hour you work and every dollar you earn. After ninety days, do the division. Sometimes the number surprises you in a way that changes your decision. Other times it confirms the choice was right. Either way, you're making it with your eyes open instead of seduced by a headline salary. The salary is real. The opportunity it creates is real. But the cost is paid in chunks of your life that you can't get back, and most people only notice the size of those chunks when they're already six months deep and too embarrassed to leave. Don't be most people. Do the math honestly, and then do it again after you've actually lived the schedule for a few weeks. The numbers often change when you stop calculating on paper and start calculating in practice.
