Slashdot Mirror

← Back to Stories (view on slashdot.org)

Ask Slashdot: Why Did You Quit Your Last Job?

Posted by msmash on from the inside-your-mind dept.

An anonymous reader writes: Plain and simple: What motivated or pushed you to leave your last job? Did you have any colleague or friend or family who had left their job for a similar reason?

10 of 540 comments (clear)

  1. Immigration by AmiMoJo · · Score: 5, Interesting

    Couldn't get a visa for my wife, so took my skills and tax contributions and left.

    A bad immigration policy not only deprives the country of the immigrants it needs, it drives the natives out too.

    --
    const int one = 65536; (Silvermoon, Texture.cs)
    SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    1. Re:Immigration by AmiMoJo · · Score: 4, Interesting

      Indeed, the UK is one of the worst in the world for family visas.

      Several years ago the government made a most unwise promise to reduce immigration to the "tens of thousands" (net). At the moment it's about +230,000 net which is actually down quite a bit from a peak of around +330,000 due to Brexit.

      There are about 85,000 family reunions a year. The rest is skilled workers, foreign students who keep the university system going and fees for British students down, and EU workers exercising their freedom of movement rights.

      The government could have stopped about 60% of immigration any time it liked (40% is EU freedom of movement), but obviously didn't because it would be economic suicide. So the squeeze is being put on families, particularly British people with foreign spouses and children. They don't have commercial interests backing them, and they don't have money to pay the ever increasing fees or fight decisions in court.

      This will probably only get worse after Brexit, as the demand for falling immigration increases. Some Brexiteers like Rees-Mogg promised that it would get easier, but they were lying. The worst part is that most people don't realize. Literally every single person, 100% no exceptions, that I told I was getting married followed up with something like "oh, and then she is coming here?" Most people assume that if you are married and a British citizen you have a right to unite your family here, but in reality it's extremely difficult and the Home Office will resist in every way possible.

      When people talk about having a guest worker system that doesn't allow families to come they are being delusional. No skilled worker who isn't fresh out of university and free from all attachments is going to want to move to another country by themselves and abandon their spouse and children. If you want skilled labour you have to accept the family of skilled labour. Most countries are fine with this, except for the ones in the grip of populism and anti-immigrant scaremongering/scapegoating.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
  2. Laid off after corporate merger/acquisition by gti_guy · · Score: 4, Interesting

    Twice. Also laid off once after 3rd round of lay offs due to mismanagement. 30+ years in IT

  3. well ... by cascadingstylesheet · · Score: 3, Interesting

    ... the precipitating event was that a manager I used to work under called me up, and asked me if I'd consider going where she was now. I said yes and am super glad that I did.

    I was receptive to that because of a number of factors. But the root factor to all those factors was (in my opinion) a Marketing department that couldn't stop making decisions based on "ooh, shiny!"

    Parenthetically, I either have a knack or great luck at leaving places before the ship sinks.

  4. Burnout, Re-orgs, and Death. Oh My! by Karnak23 · · Score: 5, Interesting

    Combination of burnout and no longer doing what I enjoy.

    The burnout came during a really rough, 3-year development cycle. We spent three months planning with the principal team. They approved the plans and let us run in one direction for a year before dropping a bombshell on ALL the partner teams. We had to drop what we were doing and start over with a completely new (and woefully incomplete) API, tool chain, and environment. Roughest two years I've spent in software ever.

    Had a former manager swoop in and rescue a number of us. Spent three years learning new stuff and enjoying my work and team. Then a big re-org came. Moved to something I'm not really enjoying and I can feel the "don't give a shit" attitude building up.

    Top it off with a death in the family and it's time to go.

    Fortunately, a great stock and housing market will allow me and my partner to enjoy some time off. Hopefully a year or two of doing what I want to do and exploring topics I want to learn will help clarify things. I'll find my passion for the work again or find another thing to fire my passion.

  5. Health care isn't about doing a good job by puck01 · · Score: 4, Interesting

    I wasn't allowed to perform at a level I was comfortable with. I'm a physician.

    Too many people often with training that is not the same as mine (MBA vs MD or nurse admin vs MD) trying to tell me how I should to my job. Being forced to use EHRs that are just good enough for the hospital admins to okay but are nowhere close to what physicians need to perform well. There is only so much time in a day. Not completing all the task you'd like the way you feel they should be after 12-14 hours of work with no lunch or rest is very disheartening on many levels. Experiencing this nearly every day has a way of killing your spirit. After 10+ years I said no more. I had worked at an acedemic cetner and later a community non-profit.

    I work in medical informatics now so I am able to solve some of the EMR problems plaguing physicians today. I only practice medicine on weekends - the hospital admins and insurance company representatives are off. Practicing medicine this way is much more enjoyable.

    1. Re:Health care isn't about doing a good job by FearTheDonut · · Score: 3, Interesting

      I used to work writing EMR software. I won't name names, but if you have been in the medical field for a long time, you would know this system. I have a Masters in Software Engineering, but also a BSN. My sole purpose for making the switch was because I wanted an EMR system that everyone could not just use, but also positively impact fellow professionals.

      We once wrote a prototype EMR system that BLEW THE SOCKS off of med professional who saw it. It was fricking amazing. EVERYONE loved this thing, saying things, "This is exactly what we need!". However, we eventually demoed it hospital administrators who not just said "Meh..." they said it would mean they'd have to retrain everyone so, no, they'd keep the old shitty system." I left within 3 months.

    2. Re:Health care isn't about doing a good job by puck01 · · Score: 3, Interesting

      That sounds about right. There are a lot of problems with health care today. One that is really unappreciated is how bad hospital admins are and enabling their highly trained workers to do their job. Its a joke. The US system has purposefully shifted power to them over the last 15-20 years. Its not surprising now that physician satisfaction is very low and their suicide rate is now among the highest of all professions. That's what happens when lessor trained people tell well-intentioned highly trained people how to do their job.

      When I was at the non-profit, I took on a number of admin task related to EMRs. While I did enjoy what improvements I could enable, it was always an uphill battle. They never want to support anything that would require any effort beyond a day or two of developer time. They minimize physician needs based on the grumpy bad players or those that bring in a lot of revenue - not the well intended majority.

  6. Negative environment, poor pay by tnok85 · · Score: 4, Interesting

    I worked as the System Administrator/Software Developer for a smaller company (~35 employees). I architected and built out a multi-channel eCommerce solution that synced their ancient database (inventory, pricing, etc) to a modern SQL database that could be tied into Amazon, eBay, their own webstore (which I also built). Automatic repricing to stay competitive based on our inventory costs, custom pricing for custom sizes, bin packing problems, plenty of complex stuff.

    Very very negative environment. Frequent company wide meetings where we were referred to as replaceable and disposable. Cost of living raises once every 24 months if we were lucky. Any time money came up, the company owner would go into a rant about how much each employee costs to employee.

    Pay wasn't keeping up nearly enough with my increased responsibilities (even though my software was responsible for several million per year *profit*).

    They haven't replaced me (have tried a few times, have a few friends who work there) and none of them worked out. Amazingly my software is still running after a couple years. The first major API change to any of the eCommerce channels will break it pretty bad.

    Now I'm a Software Architect (with a heavy dose of DevOps) for a multi-billion dollar company making nearly 300% of what I did there.

    tl;dr - Worked well beyond my job responsibilities, made the company a lot of money, they wouldn't pay me, so I left for a company that would pay me.

  7. I had a heart attack by halivar · · Score: 4, Interesting

    I worked at a job that has seasonal crunch-times, followed by a season of long, long hours to support the released product. Think 60-80 hours a week. When I first started, the season of long hours was technically a code freeze; we only checked in critical bug fixes, and code pushes were arranged long ahead of schedule. Emergency code pushes were vetted by the chief architect. All in all, most of that time was spent killing time, waiting, and watching.

    One season, everything changed. My boss (dev manager) left to go work for a competitor, and was replaced by someone from Sales. At that moment, the dev team became a boiler room. He over-promised his bosses, and expected us to deliver. Scrum become a bullshit "sign off on this estimate or else." If you tried to be conservative in your estimate, the meeting would drag on while he badgered you about why your estimate was so low ("I just don't see..." was his favorite phrase). Eventually you agreed just to put the meeting out of its misery; and you would be held to that estimate. So the crunch-time became almost unbearable. At the same time, my daughter was born. The combination of these things sent by blood pressure through the roof. My doctor warned me that I was extremely hypertensive (170/100) and that drastic action was needed. I took pills, changed my diet, I did everything but change my job.

    You see, my coworkers (the ones that were all quitting around this time) used to joke and call me a "company man." I had never quit a job. Ever. I had only held two jobs before, and lost them both due to problems at the company (the first got hit by the dot-bomb, the second sold email software to ISP's [you can draw your own conclusions]).

    The company owners were great; they really loved the employees, and they tried to make it the best they could. Unfortunately, they were blind to the problems with middle-management. The past year, to alleviate the work stress, they changed company policy on long hours. Basically, the new understanding was that, since we had remote capability and were on-call, it was no longer necessary for us to sit around 60-80 hours for a whole season doing nothing. For other divisions, this meant 40 hour work weeks. My manager's takeaway, however, was that the 60-80 hours could not be filled with actual work. Velocity was expected to increase by 50%-100%.

    Soon after that first season ended, we had a week vacation and then geared up for another crunch period (yay! Only 40 hours, now!). One week shy of my daughter's first birthday, I woke up in the middle of a Friday night with my chest thumping. But it couldn't be a heart-attack; after all, I'm a hypochondriac, and it has never been a heart attack before. So I scheduled a same-day appointment that Saturday morning with my GP. Turns out I had had a total blockage of my lower-left ventricle for over 12 hours. Three stents, and lucky not to have permanent cardiac tissue damage. Luckier still not to be dead; my brand new cardiologist informed me that I was only hours from a catastrophic and unrecoverable cardiac event. I would not have survived the evening.

    My cardiologist and GP agreed on this point: it was not diet, or exercise, or any other external factor that caused my heart attack; it was 100% stress. It should not have happened, especially at my age. They said I had to cut out the stress immediately.

    So, being the company man that I am, I gave the company another season of long hours. But this time I did it right. I didn't let my boss get to me, I didn't volunteer for useless and unrewarding tasks, and all in all stopped being the jump-up-and-go guy I had been before. My manager informed me two weeks before my review that I was going to get poor marks for work throughput. I had not received a bad in 18 years, and I was not going to get one now. I put out my resume, and got hired by the first place I submitted it to (keyword search "work-life balance"). I handed in my resignation the day before my review.

    Work will always be work, but it doesn't have to be terrible (and shouldn't be).

    tl;dr: Don't wait until your job kills you to leave.