Slashdot Mirror


Amazon Work-Life Balance Defender: Prior Employer Nearly Killed Me and My Team

theodp writes: New York Times Public Editor Margaret Sullivan questions whether her paper's portrayal of Amazon's brutal workplace was on target, citing a long, passionate response in disagreement from Nick Ciubotariu, a head of infrastructure development at Amazon. Interestingly, Ciubotariu — whose take on Amazon's work-life balance ("I've never worked a single weekend when I didn't want to") was used as Exhibit A by CEO Jeff Bezos to refute the NYT's report — wrote last December of regretting his role as an enabler of his team's "Death March" at a former employer (perhaps Microsoft, judging by Ciubotariu's LinkedIn profile and his essay's HiPo and Vegas references). "I asked if there were any questions," wrote Ciubotariu of a team meeting. "Nadia, one of my Engineers, had one: 'Nick, when will this finally end?' As I looked around the room, I saw 9 completely broken human beings. We had been working over 100 hours a week for the past 2 months. Two of my Engineers had tears on their faces. I did my best to keep from completely breaking down myself. With my voice choking, I looked at everyone, and said: 'This ends right now'." Ciubotariu added, "I hope they can forgive me for being an enabler of their death march, however unwilling, and that I ultimately didn't do enough to stop it. As a 'reward' for all this, I calibrated #1 overall in my organization, and received yet another HiPo nomination and induction, at the cost of a shattered family life, my health, and a broken team. I don't think I ever felt worse in my entire career. If I could give it all back, I would, in an instant, no questions asked. Physically and mentally, I took about a year to heal."

21 of 211 comments (clear)

  1. "I wanted to work this weekend" by SlithyMagister · · Score: 5, Insightful

    I really did

    FTFS:
    "I've never worked a single weekend when I didn't want to"

    Employee: "I wanted to work this weekend. I really did"
    Interviewer: "Oh, that's good. Why did you want to work this weekend?"
    Employee: "Cuz they'd fire my ass otherwise, doofus!"

    'nuff said. Sure, some management type work weekends to "set an example" but otherwise I don't buy it.

    I was a mid-level IT dept manager for a major newspaper. I was never specifically asked to work overtime, but I often did so because it was my responsibility to ensure production readiness. So yeah, I chose to work, but to say I "wanted to" would be stretching it.
    Peace,...

    1. Re:"I wanted to work this weekend" by Beeftopia · · Score: 4, Interesting

      Times I've wanted to work on the weekend:

      1) When I'm doing work on the side and want to get it done. I'll work on the weekend.

      2) When I'm being paid well and able to telecommute, and there's a task that needs to be done - I'll work on the weekend. Heck, in that situation, I've worked late nights too. The working environment couldn't get more comfortable, with my own kitchen and bathroom and climate control. And when my brain shuts down late at night, I'm a few feet from the bed.

      When I'm on-site... and I'm eating from the vending machine, trying to avoid using the low-privacy, cesspool toilets, and it's too cold or too hot, and I can't take a few minutes off and relax on the couch or outside in peace - yeah, I have no interest in staying there longer than my 8 hours. I don't care how interesting the work is. I've done it of course, both late night and weekends, but under duress like the parent poster noted.

    2. Re:"I wanted to work this weekend" by rainmaestro · · Score: 5, Insightful

      This. The standard worker smarter vs work harder dilemma.

      I did the whole groove thing when I was in my twenties and just starting out. As I gained experience, it became obvious that the groove is far from ideal. I produce better code when I take frequent short breaks. Get up, stretch, take a quick walk, give your brain time to process everything you've been doing. Then you're in the right mindset to see what's what. So I don't work late, especially on Fridays. If I'm in the middle of a tricky bit and 5:00 hits, I'm gone. By the time Monday rolls around, I know how to proceed because the problem has been rolling around my subconscious for 2.5 days.

      I see a few coworkers who work long hours in the groove, and they always seem to be rewriting four hours of work for the third time because they get into the groove, churn it out and a day later realize it isn't gonna work long-term. Meanwhile, if they'd just stopped an hour in and pinged one of their colleagues for a 5-minute sanity check they'd have realized it sooner and saved their evening.

  2. Re:Logical by Anonymous Coward · · Score: 5, Insightful

    Your company regularly makes everyone work 100 hours a week, and you wonder why they're having problems hiring developers?? It's a fucking miracle the rest of your team hasn't left yet to go work for a less shitty company!

  3. Dear Nick by eulernet · · Score: 4, Insightful

    Dear Nick,

    I'm very happy to learn that you, the Head of Infrastructure Development at Amazon, have good working conditions at Amazon, but your opinion is absolutely irrelevant, since people being pressured at Amazon are not developers, but people doing physical work.

    It's easy to defend your job when you have a comfortable position, but it's also very disrespectful towards people who do *real* manual work, who are forced to follow a fast pace and who are also badly paid.

    I had countless death marches in my previous jobs (in videogames), and I know very well how it destroys people (and it took me more than one year to recover).
    But death marches cannot compare to physical repetitive fast-pacing tasks.
    The body suffers but also questions arise, because the mind is completely available.

    As a software engineer, my minds is always busy, so I don't have doubts when I work.
    If I had a manual work, I would have plenty of time to wonder why I do a job that I dislike.

    I have experienced the Stockholm syndrome https://en.wikipedia.org/wiki/... in a few jobs, where I believed it was my duty to sacrifice myself for the company, so I understand people wanting to show that they can perform better than others.
    It's totally normal !

    But please, Nick, don't compare your job to the mindless harassing jobs in Amazon.

    1. Re:Dear Nick by Beeftopia · · Score: 5, Insightful

      The overseer whipping the slaves: "Damn, that one time, my arm got so tired, I didn't know if I could keep going. But I persevered." :)

  4. What ridiculous logic by jtownatpunk.net · · Score: 4, Insightful

    Just because there are worse places to work doesn't make Amazon a good place to work.

  5. Let me get this straight by Tough+Love · · Score: 5, Insightful

    Manager passionately disagrees with complaints of managers abusing staff, did I get that right?

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  6. Re:Logical by FlyHelicopters · · Score: 4, Insightful

    You just can't find developers at any price./quote

    Don't be silly, of course you can... you're just not offering enough.

    Six figures sounds like a lot, but it isn't anymore. I make about $300k these days and I work 40 hours a week (I work more some weeks during crunch, but I also get 8 weeks of vacation to compensate, and I take it). It would cost $500k a year to get me to move (more if you're in CA), but if you needed my skills, I think I'd be worth it.

    Are you offering $500K? What do you need?

  7. Re:Logical by YrWrstNtmr · · Score: 4, Insightful

    The rest of us have had to work "hundreds" as my boss calls them, which are 16 hours a day on weekdays and 10 hours a day on weekends, for over two years. Also, we haven't allowed any vacation time other than around Christmas in nearly three years.

    Change this first. Then you might get some actual employees.

  8. We're dealing with an imbalance of power here by Applehu+Akbar · · Score: 4, Interesting

    Here's an interesting case for unionization in tech:
    https://michaelochurch.wordpre...
    Discuss.

    1. Re:We're dealing with an imbalance of power here by Applehu+Akbar · · Score: 4, Insightful

      This is my fiftieth year in tech, and whenever the word "union" has come up in the field, workers have reacted to horror stories from Detroit, Chicago and DC, where the imbalance of power was clearly in the opposite direction: graft and featherbedding destroying grand old industries, driving the smoldering remnants of our national productivity away to Asia. What we were not being cognizant of was that there was an earlier time - in the mining camps of the Gilded Age, in meatpacking plants crammed with immigrants fresh from eastern Europe and willing to do anything to survive, in steel mills where nobody cared about working conditions - where the imbalance of power went the other way. That was when the union movement got started.

      I'm fortunate to have spent most of my career in times and places where developers had the upper hand over companies in negotiations. You got mistreated at one place, there was always a better job around the corner, and everyone knew it. If the stories coming out about conditions at Amazon and other tech companies are true, today's young people don't have that luxury, and may have no choice but to organize.

  9. Re:No sympaty for slef-inflicted problems by Pro923 · · Score: 4, Interesting

    I agree with you, I do... But as a guy who has worked in tech for 20+ years now, there have been so many times where I realize that people can be so smart, yet so stupid at the same time. Specifically, tech people - suckers... So many time I've looked around the room for someone else to share a look of "what the fuck?" with me, but most of the time, no one dares. When they offer people "free pizza" to work past 8:00, I look around for people to say, "Yeah, thanks, but I'll go home now and buy my own $6.99 pizza thanks" - but no one does, and they work, and they eat the pizza like it's some incredible gift.

    If everyone were like me, we'd probably get paid more than the sales guys, work less hours and have a hell of a lot more respect. The problem is that your average engineer is a moron. Since most are morons, we're all morons. If I'm the one guy that tells them to "shove the pizza up their ass cause I'm goin home on time", I'll get replaced with a fresh Chinese kid faster than you can say kung pao chicken.

    I can say I'm a broken person now... I'm definitely not what I was 15 years ago when I was a smart mofo and ready to take on the world. THe tech industry has brought me to the ground - in so many ways. You can't win... We're all just cogs in a wheel... The industry has been turned into more of a manual labor type of gig, and it sucks.

  10. Re:No sympaty for slef-inflicted problems by PopeRatzo · · Score: 4, Informative

    Y'all just need to grow a pair and remember that employment is a business contract between equals.

    No, it's not. In late-stage capitalism, employment is more like a monopsony. In fact, most of Amazon's business model is based on monopsony.

    Corporate consolidation has created these megacorps, grown to unimaginable size. When an employer reaches a certain size, it can drive down wages and working conditions.

    It doesn't have to be only one buyer to be a monopsonistic market.

    --
    You are welcome on my lawn.
  11. Re:Logical by Anonymous Coward · · Score: 5, Insightful

    you are having trouble because word on the street is that you work 100 hours. Everyone knows, no one applies.

  12. Re:Logical by Anonymous Coward · · Score: 5, Insightful

    Hmm, but that is why you are having problems. You think it is easy to hide the fact that you are all overworked and you can tidy up the place to hide evidence that you live at your work, but people aren't stupid. They know the culture. Just like employers can look up information about candidates on the Internet, the same way candidates can look up working conditions. And Amazon isn't a place many people would like to work.

    In my province there is also an IT company that makes custom made software. They also have a 'flexible' team of programmers, which just means that the programmers have to be flexible in their working hours. They still have to do the usual 8 till 5, even when there is no work. But when there is work, the flexibility kicks in. They have to work lots of hours, they have to work in the weekend. Having a child that needs attention isn't showing flexibility and loyalty to the company. You can still phone someone like your neighbor to pick up your child from the child care center. That's their culture.

    But lately they have been complaining that they can't find new programmers and this with so many unemployed people. And they offer so many benefits like a laptop, a smart phone and a company car and the chance to work in a wonderful team.
     
    Well of course you can't find people willing to work under these conditions. Only very few people are willing to have a life like this. If you love your family, you can not have a live like this. It is even better to just remain unemployed for some time until you find the right job, than having to endure this flexible team spirit that is fueled by many team building events. It almost sounds like religious indoctrination and I'm well aware that some people are vulnerable to this kind of indoctrination. But many people are not and do not even want to try to work at that company because they know about the working conditions.

    Yet that doesn't stop the local news paper to have a monthly full page infomercial about that company where they can still try to attract new candidates. It probably costs them quite some money to have this full page advert that looks like a news article. But why not just change the working conditions. The company grew too fast in its history but they handled it wrong. Instead of hiring enough people, and slowing down growth when you can't find them, they just demand unhealthy working ethics from their programmers.

  13. Re:Logical by NormalVisual · · Score: 5, Insightful

    That isn't why we're having trouble. We, of course, don't mention that.

    You don't have to - word gets around. If your coders are being expected to regularly put in 2.5 times the "normal" hours per week, the company should be expected to be paying them at least 2.5 times what the going rate is. Offer that deal, and you might see more interest from competent people.

    --
    Please stand clear of the doors, por favor mantenganse alejado de las puertas
  14. Re:Logical by Anonymous Coward · · Score: 5, Insightful

    You apparently work in a hell-hole. I take off around a month a year, and have been doing so for almost a decade with no ill effect. You need to find a job that treats you (explicitly and implicitly) as a human being.

  15. Re:No sympaty for slef-inflicted problems by Dutch+Gun · · Score: 4, Insightful

    It's really, really hard to do that when you're a young person on your first job, and are just thankful that you're being given a shot to gain some valuable real-world experience. It's also very easy to say that when you've got fifteen or more years of experience, lots of high profile projects under your belt, and can get a job just about anywhere you like with relative ease.

    So, when you talk about "equals", you have to consider that some "equals" have much more bargaining power than others. I'm not disagreeing with your sentiment, but I'd suggest that it falls on senior developers to take on some leadership in these sorts of fights against bad managerial practices.

    Personally, I still don't get the short-term thinking of forcing insane work hours on programmers or other skilled workers. For myself, I've noticed that my quality of work and productivity per hour drop dramatically when I've worked long hours. Even when I'm working on my own now as an independent developer, I try to limit my hours per day and per week for fear of making bad decisions or writing bad code. It comes back to bite you in the end.

    Moreover, forcing long hours on people simply burns them out, meaning you're going to lose your best and hardest-working people in the end. Or at the very least, they'll need a long time to recover, negating any short-term gains. I've seen an entire game development team simply disintegrate at the end of a project after a long, extended death march. The company foolishly sacrificed an entire team for the sake of one project, and the end results weren't even that spectacular. People tend to slog it out to the end, because they want to see their own work through to the finished project, but afterwards, they realize that they never want to be subjected to that again, and find other jobs, many even leaving the industry.

    Death marches are nearly always a result of management failure. Either management failed with initial estimates and unrealistic scope, or by failing to make necessary revisions or cuts earlier in the project, when things started falling behind (in other words, making hard decisions). Or worst, they're a callous way to try to squeeze more from less as a matter of economics - pretty much the most idiotic type of short-term thinking imaginable.

    --
    Irony: Agile development has too much intertia to be abandoned now.
  16. Re: Logical by Anonymous Coward · · Score: 5, Insightful

    Wow. This is what's wrong with the American work ethic.

    Everyone is afraid to take their vacation time out of fear of being let go because they're not seen as " important " or " critical ".

    Tip: You work for a very shitty company if you're so damned critical you can't even take your own vacation time off. Tell them to hire more employees and quit relying on one person. You can bet your ass the CEO and the rest of the executive branch takes their time off. . . .

    Trust me when I say you're not the super-hero you think you are. You'll burn out or die from a heart attack or stroke and they'll replace you within two weeks. From overseas if necessary. Then they'll work that one into the ground. Wash, rinse and repeat as necessary.

    Remember, the brightest star burns out the fastest. . . .

  17. Re:Logical by JoeMerchant · · Score: 4, Insightful

    I don't think the relationship should be linear - 2.5x the work for 2.5x the hours...

    If you count waking hours, a typical (3 weeks vacation M-F 9-5) job expects 49 *40 / (52 * 7 * 16 ) = 1960 / 5824 = right at 33% of your life. As they take away my free time, I have to hire (and manage) people to do things for me that I would normally do for myself - this drives up costs by as much as 3-4x in many instances, and can become incalculable when it means hiring people to watch my children grow up for me.

    I think a fair overtime formula would be paying you 4x your standard hourly rate by the time you reach 80 hours a week, something like P = P * (H / 40)^2 when H > 40 - by the time they've taken all your waking hours, pay would be at 9x standard. Is getting the project out on-time critically important to the financial future of the company? If it really is, the team that "gives their all" should be getting more than "attaboys" in return.

    If it's a short-term crisis where 4 or 40 extra hours worked at a critical juncture can be "paid back" in comp-time within a week or two, that makes total sense in an "overtime exempt" relationship. If the crisis is dragging for months and all you're getting is a gold star on your annual review, put in a few extra hours a week to shop for a better working relationship.