Live data from Hacker News

Quitting a New Job

yolken.net

191–200 of 246 posts

Re: Quitting a New Job

#191
post #128

I'm about a month into a new FAANG job, and I hate it so far. I can't decide if it's better to quit sooner as to not waste the companies time (and avoid suffering more), or if I should give it some more time. My team's work seems super boring, I'm not interested in the tech we use, the setup process has been a shit-show, and I'm feeling zero motivation. I've mostly worked for startup to mid sized companies in the pas…

Personally I would just work the minimum amount and do open source or other side projects (indie hacking) with the rest of the time. Then leave after 12-18 months.

Problem is when I have a job I dislike, I loose all motivation outside of work too. So even if I slack off I'll still be miserable.

Re: Quitting a New Job

#192
post #168
post #164

Earlier quoted context omitted.

Probably a lot. Unless you're getting paid enough to put up with it:) That being said, I think a lot people that aren't singularly money-focused overestimate how much money will outweigh other factors in their job.

I was super motivated by the money when I was doing leetcode prep, and then when negotiating and playing offers against each other. And that makes sense, the work I was doing had a direct correlation to the total compensation I ended up signing for. But now that those fat pay checks are coming in, they provide zero motivation, it's just a slightly bigger number in my bank account.

Do you have goals outside of work that the additional money will help you accomplish?

Re: Quitting a New Job

#193

This statement is just sad "After a few weekends of furiously-paced Leetcoding".

Reply that I posted to another comment: Why? If a person can learn bunch of algorithms and apply them to custom problems they probably can do quite a bit with computers. And it shows that they probably can learn new stuff rapidly as well. I don't get why so many developers hate Leetcode. I love it personally, I think it's great. And also, I think people are just lazy and don't want to learn new stuff so they whine in…

Yeah people are "lazy" in that they don't want to spend precious few free hours of their weeks grinding out a gimmicky skill-set that is at best tangential to the actual work they would be doing.

I understand there is no simple solution to how to hire software engineers, but you should be able to recognize why a lot of us don't like the current status quo of interviewing (even if you thrive in it).

Re: Quitting a New Job

#194
post #66

I also did this, worked at a startup for 3 months and left for FAANG. Everyone was surprised, and my manager wasn’t super happy, but on the whole my coworkers understood and tbh it was the best decision of my life. Definitely do not regret it in any way.

They'd be quick to lay you off when times get tough. I'm sure you wouldn't be super happy if that occurred.

Re: Quitting a New Job

#195
post #128

I'm about a month into a new FAANG job, and I hate it so far. I can't decide if it's better to quit sooner as to not waste the companies time (and avoid suffering more), or if I should give it some more time. My team's work seems super boring, I'm not interested in the tech we use, the setup process has been a shit-show, and I'm feeling zero motivation. I've mostly worked for startup to mid sized companies in the pas…

Is it Amazon? Sounds like Amazon.

Re: Quitting a New Job

#196

> the upper rungs of Stripe’s engineering individual contributor (IC) ladder put a lot of emphasis on cross-team coordination and other, managerial-like activities that I didn’t enjoy and felt I wasn’t very good at. That's just the reality of senior IC engineering positions. At some point, there's a limit to the amount that you can contribute by sheerly by your own work - to have a bigger impact, you'll need to need…

Does anyone else find it kind of funny that a lot of companies' "Individual Contributor" roles so many times involve contributions of others once they get past a certain point? Doesn't that mean it's no longer an "Individual Contributor" position?

The IC/manager distinction is a useful false dichotomy, not an absolute rule.

Re: Quitting a New Job

#197
post #139

I'll put my experiences down as a cautionary tale. I've had 3 relatively short stints in tech jobs, but none where I left responsibilities on the table, like leaving in the middle of a project, or promising some work only to bail. Notice was always given, and I made the best effort to transition by completing all work before the end date. My reasons for leaving each are a bit more serious than a lifestyle downgrade,…

> The only thing that seems to count is your tenure, so don't fuck it up. You might not even get to the leetcode step if you do. This is flat wrong. Are you only applying to Fortune 500s or something?

How do you prove to the next company that you won't leave? You really can't. You can easily prove you've been working on leetcode problems. If they don't want to hire people with short stays, you can't really fix that. If they don't want to hire people who haven't practiced leetcode, you can fix that. So to an employer, does it really matter if you are good at leetcode if they feel you won't stay around long? So the tenure takes precedence.

Some companies won't care, but finding those is just about as easy as finding a company that's a good fit before you've worked there.

Re: Quitting a New Job

#199

Completely different type of work, but I once quit a new job at a factory after two days. First day, I arrive early to fill out the paperwork and watch the HR job safety video. Video finishes and I wait for the HR person to return. After a few minutes, I go look for her, but can't find her so I go back to the video room. Eventually someone else (upset) comes in and tells me that I'm supposed to be working rather than…

holy, what industry?

Re: Quitting a New Job

#200
post #197

Earlier quoted context omitted.

> The only thing that seems to count is your tenure, so don't fuck it up. You might not even get to the leetcode step if you do. This is flat wrong. Are you only applying to Fortune 500s or something?

How do you prove to the next company that you won't leave? You really can't. You can easily prove you've been working on leetcode problems. If they don't want to hire people with short stays, you can't really fix that. If they don't want to hire people who haven't practiced leetcode, you can fix that. So to an employer, does it really matter if you are good at leetcode if they feel you won't stay around long? So the…

[deleted]
Post reply on HN