91–100 of 365 posts
Earlier quoted context omitted.
There is also a thing called unions.
The tech industry has the best horizontal mobility of any other right now. Why do we need the downside of unions when we can just move company and have only the upsides?
I think you just answered your own question. Unionize while you have leverage to protect yourself for a future where you might not.
Earlier quoted context omitted.
There is no such thing as a "recruitment list" to be removed from, unless you remove all traces of yourself from the internet. Sourcers don't work from a shared list. Also, you might be surprised to hear how often people will say "no" at one point, and later say "yes." Circumstances change. Asking again later works.
> Sourcers don't work from a shared list. Presumably they do have a referral database, though. I can't remember the exact verbiage, and can't be bothered to go digging for the emails, but I know I've received several similar solicits after asking to be removed from their referral pipeline.
Amazon is not the only company to sue over this, Microsoft successfully sued as well[0]. In fact, several large companies have pushed to keep these non-competes in place in Washington State[1]. I don't think it's fair to focus only on Amazon. The reality is that in Washington State, this benefits many large corporations ( while being harmful to employees ) so it is the company's incentive to try and keep the non-comp…
I interviewed with AWS for an analyst/business intelligence engineer role. When asked to write a query to get the total GDP by month per country, I wrote a query along the lines of: select date_trunc('month',datecolumn) as month, country, sum(GDP) over (partition by date_trunc('month', datecolumn), country) FROM the_table order by 1 The interviewer asked me if I was missing something. I said no. "Don't you need an ad…
I'm guessing you didn't get to do this interactively? If I interviewed someone and they seemed knew something I didn't and could prove it by actually running the query/code I would be impressed. At the very least the interviewer should have checked your claim after the interview if they were skeptical. I think it's a real mistake when you don't let candidates write actual code and run it during interviews.
I've also turned down countless Amazon interview offers. In fact, I don't get how I'm still on their recruitment lists after asking several times to be removed. Amazon has arguably the worst culture out of any large tech company, and generally treats its workers like dirt. Given all my friends that worked for them, almost all have quit within 5 years. Given their abysmal warehouse management, it's no surprise they ha…
> Given all my friends that worked for them, almost all have quit within 5 years. 5 years is pretty darn high by tech company standard, as people already mentioned. Partly because of the culture of "you have to jump ship to make more money and promotions", but even the most employee friendly company will barely edge that, just because software engineers have a huge "grass is greener" syndrome.
I've also turned down countless Amazon interview offers. In fact, I don't get how I'm still on their recruitment lists after asking several times to be removed. Amazon has arguably the worst culture out of any large tech company, and generally treats its workers like dirt. Given all my friends that worked for them, almost all have quit within 5 years. Given their abysmal warehouse management, it's no surprise they ha…
I haven't personally experienced Amazon's culture however.
How does refusing to sign a non-compete clause typically play out? I imagine it goes back and forth, and I'm trying to imagine a tactful way to do it that doesn't burn the relationship.
(client): "Here is our standard contract"
(me): "Please remove the 12 months non compete clause"
(client): "How about 6 months non compete?"
(me): "No"
(client): "3 months?"
(me): "Fine, where do I sign?"
I don't mind 3 months non compete. I can take a longer holiday if I desperately need to go straight back. I never have and 6 months is probably ok as well.
It is mostly if I go somewhere else and it for some reasons finished early after a few months, then I am free to go wherever I choose.
Earlier quoted context omitted.
> Given all my friends that worked for them, almost all have quit within 5 years. 5 years is pretty darn high by tech company standard, as people already mentioned. Partly because of the culture of "you have to jump ship to make more money and promotions", but even the most employee friendly company will barely edge that, just because software engineers have a huge "grass is greener" syndrome.
>just because software engineers have a huge "grass is greener" syndrome "Grass is greener" is a strange label to use for the ability of even mediocre developers to get $50K+ raises by switching jobs, while the industry as a whole remains myopic about giving comparable pay increases to existing employees.
Earlier quoted context omitted.
> Sourcers don't work from a shared list. Presumably they do have a referral database, though. I can't remember the exact verbiage, and can't be bothered to go digging for the emails, but I know I've received several similar solicits after asking to be removed from their referral pipeline.
Amazon recruiters don't talk to each other at all. I actually applied for a position from a local ad, and shortly heard from a recruiter. I assumed it was in reference to my application, but it turns out it wasn't and this recruiter had no positions availably locally (only in Seattle). It's a shit-show.
The only thing that scares me is the IP factor if I work on stuff after work. From what I am hearing, if I am not in Cali, I am at risk even if I don't use company time/equipment? Amazon pretty much doubles salaries in areas outside of California, so it's extremely appealing money-wise if you stick around for the vest.
No, this is a common misconception.