Live data from Hacker News

Quitting a New Job

yolken.net

21–30 of 246 posts

Re: Quitting a New Job

#22
I haven't had success switching teams at all. I had a few that wanted to still interview me. I had a vp say he won't let me switch. The only time I ever switched teams, I had that decision made for me, worked out fortunately.

Having another internal team still want to do a technical interview was ridiculous to hear though.

Re: Quitting a New Job

#23
post #6

Earlier quoted context omitted.

This is the risk with at-will employment in CA. The employer could very well decide after two days of you working there that they wanted to let you go -- there's no part of the contract keeping either side from ending things early. I don't think it's unethical to leave after a short amount of time given the employer has no equivalent expectation.

I agree with this. However, I will say unless there is something major wrong with you or major at the company, you are now going to be fired very quickly. The company also doesn’t want that reputation. I work in finance and certain hedge funds have a reputation for cutting people quickly they don’t like. It attracts people that are ok with that and most stay away. That all said - you got to look out for you and your…

now or not going to be fired quickly?

Re: Quitting a New Job

#24
post #7

Earlier quoted context omitted.

Not only that, but I'm getting the feeling a developer's best option these days for maximizing pay increases is to spend their free time on Leetcode. Which in my opinion is a problem from an industry perspective.

> Which in my opinion is a problem from an industry perspective. 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 n…

Because learning a bunch of algorithms doesn’t translate well into day to day programming capability. This is exactly why those dumb whiteboard problems aren’t good for interviews; you’re not measuring what makes someone successful on a day to day basis.

Re: Quitting a New Job

#25
post #8
post #6

Earlier quoted context omitted.

This is the risk with at-will employment in CA. The employer could very well decide after two days of you working there that they wanted to let you go -- there's no part of the contract keeping either side from ending things early. I don't think it's unethical to leave after a short amount of time given the employer has no equivalent expectation.

Would you have a different expectation if the employment agreement specified severance compensation for the employee, or if the law required severance?

If the law required severance the law is also pretty likely to make requirements of the employee as well so things will still be equal - when I say pretty likely I mean in every case I have ever seen.

Re: Quitting a New Job

#27
> 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 influence/improve/impact others

Re: Quitting a New Job

#28
post #6
post #2

I realize that HN is very employee-centric, but "exploring new opportunities but don’t quit until something better is lined up" is rather harmful to the team you're working with. If someone's just started, they're generally a net-negative, so the individual is both drawing pay and sucking resources. This is almost 'quitting in-place'. If we expect startups and companies to act ethically (in terms of pay, benefits, op…

This is the risk with at-will employment in CA. The employer could very well decide after two days of you working there that they wanted to let you go -- there's no part of the contract keeping either side from ending things early. I don't think it's unethical to leave after a short amount of time given the employer has no equivalent expectation.

[deleted]

Re: Quitting a New Job

#29
I've done this before. Got an offer while I was still interviewing with a few other companies. Accepted the offer then a few weeks later another, significantly better, offer came through.

I have absolutely no qualms about it, and I don't put the tiny stint on my resume. My work and expertise speaks for itself. It's sad that job hunting has become rife with Machiavellian machinations in the past three decades, but this is the world we live in. Acting otherwise is self-sabotaging.

Long gone are the days where we'd become "company men" loyal to CEOs and corporate pillars. We'd get to retire in our late 50s with pretty wives, a few kids, and decent savings. Job hopping is the most reliable way to get a raise. If you don't job hop, you might be on the chopping block come the next layoff wave.

This is all on top of the fact that engineers are woefully underpaid. I have finance friends that make literal millions in yearly bonuses. This is virtually unheard of in software, even though we provide orders of magnitude more value.

It is what it is.

Re: Quitting a New Job

#30

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 instead. I don't think whining will help them.

Post reply on HN