Earlier quoted context omitted.
I don't think it is. I got approached by consulting companies and recruiters to work on embedded development for Intel, including on-site work in Santa Clara, CA and travel to Asia. The hourly rate was 60 and days in Asia were 250 each plus accommodations. I've never done a trip to Asia were I was working less than 10 hours per day.
Amazon software development interns (undergrad) in SF get $65/hr + a housing stipend. 60/hr seems far too low
New Intel CEO rehiring retired CPU architects
521–530 of 547 posts
Re: New Intel CEO rehiring retired CPU architects
#522Earlier quoted context omitted.
People get paid what they ask for. No one is underpaid or overpaid. Simply ask for more in salary and benefits. When they ask why, state all the reasons why the increase is warranted. If they deny the request, look for another job that pays the higher amount.
You're assuming that markets are perfect.
Re: New Intel CEO rehiring retired CPU architects
#523Earlier quoted context omitted.
I think talented people will not take it unless they're between a rock and a hard place. Sadly what this does is it attracts only the most junior or unqualified hires who (are great if you got time/budget but if not) will need to be trained by the few seniors left holding the place together. I'm not surprised Intel does this and the telecommunications side I have seen from them in Europe was rotten to the core. I hav…
Yeah, don't understand the story. He got poached from intel, or by intel? Where was he let go from? You need to.. maybe edit the story a bit.
Re: New Intel CEO rehiring retired CPU architects
#524Earlier quoted context omitted.
I just give them the salary I want to make (which is easy because what's on my paycheck + stock opts is a good enough value) so either they go for it or they will decline. It's a good way to see if they mean it or not So yeah sorry, not moving for a lower value
Would that strategy perhaps be excluding a higher salary with those willing to pay more than your maximum ask? (genuine question, no sarcasm)
Probably the simplest strategy would be to always ask for the amount you curently make, plus 30% or 50%. And keep interviewing once in a while even if you are okay with your current job. If you asked for less than you could get, the next jump will fix it.
Then don't increase your expenses, save the extra money, retire early.
Re: New Intel CEO rehiring retired CPU architects
#525Earlier quoted context omitted.
Some people don't care so much about the money. I'm barely over the six figure mark in the bay area. I could probably make a lot more money somewhere else, but I wouldn't get to do anything nearly as interesting as my current work.
I don't think is about not caring about the money... it seems to me that the salary is just the manifestation of the value the company places in the individual, and thus a company that pays 1/3 of the industry average shows very little care for their engineers, at least in my book
My experience confirms this. The least paid jobs I had were also the most stressful.
Re: New Intel CEO rehiring retired CPU architects
#526Earlier quoted context omitted.
Who do you think you are screwing by cutting off your opportunities at the root? :) As the other reply pointed out, you are cutting yourself (a) out of the conversation (b) out of finding out what your actual range is. Here's a dirty secret for you - very often the recruiters don't share the range because the range is broad, they may fill the role with a mid-level or a super-senior at 2x the comp. If they tell you th…
> Who do you think you are screwing by cutting off your opportunities at the root? :) Which would that be, if you have multiple offers, where they name the first number, and then you offer them the opportunity to bid higher against each other?
Re: New Intel CEO rehiring retired CPU architects
#527Earlier quoted context omitted.
Remember, if you pay median, 1/2 the engineers are making more at other companies.
also remember that median always exists so it will always be a case that there is 1/2 under and 1/2 over.If all companies paying median raise that by 20% what is a current median?
Re: New Intel CEO rehiring retired CPU architects
#528Earlier quoted context omitted.
I am 100% in the same boat. Had a recruiter reach out to me who wanted me to leave my more than comfortable six figure SV job to do cutting edge contract work in machine learning as a lead engineer for about $50/hour. I was so amused I actually spent the time listening to their pitch and eventually told them that anything less than $200/hour wouldn't even cover my current pay + benefits. Let me know if you can do bet…
It's one of the (dirty?) pleasures in the work-life, isn't it? I still treasure getting to the stage in my life when I could afford to stop saying what my salary expectation was outside of "fair in relation to the market and my experience". Recruiter H/R: "We need to hear your salary requirements to move forward with this position". me: "I would like to hear your offer". Recruiter / HR: "We won't be able to consider…
Re: New Intel CEO rehiring retired CPU architects
#529Earlier quoted context omitted.
> My secondhand understanding was that Intel was losing top talent due to pressure to pay closer to median industry compensation. Top engineers recognized they were underpaid and left the company. This is what happens when you're run by bean counters who don't understand your core business or industry.
In the same/similar vein it never ceases to amaze me how employers don't provide their employees with the best tools possible (within reason) to do their jobs. A company will give a developer a low/mid-range laptop/desktop pinching every penny they can then turn around any pay them a huge salary... Like do they not understand that running into RAM/CPU limits makes the developer less effective? I've had jobs where I'v…
Same for the current COVID situation. Providing every engineer with minimum dual monitor and a proper desk is only going to provide you with output gains for very little investment.
Re: New Intel CEO rehiring retired CPU architects
#530Earlier quoted context omitted.
Who do you think you are screwing by cutting off your opportunities at the root? :) As the other reply pointed out, you are cutting yourself (a) out of the conversation (b) out of finding out what your actual range is. Here's a dirty secret for you - very often the recruiters don't share the range because the range is broad, they may fill the role with a mid-level or a super-senior at 2x the comp. If they tell you th…
> because the range is broad You make it sound like if they don't tell you what the range is, they are somehow doing you a favor. No, if they don't tell you the range it's not because they're nice or whatever, but because they're trying to get you to sign on for the lowest amount possible. If you hear the range is larger than what you were expecting, you're gonna try to hit that upper bound. Both positions are unders…
I think that's an unhelpful point of view in any but most commoditized-labor situation.
The more rare and hard to find your combination of skills and experience, the longer the recruiter has spent looking for you, and the more motivated they are to get you the best offer possible to get you in the door. It's not in their or your interest to lose you to save a few tens of thousands of dollars.
>> You make it sound like if they don't tell you what the range is, they are somehow doing you a favor. No, if they don't tell you the range it's not because they're nice or whatever, but because they're trying to get you to sign on for the lowest amount possible.
Again that kind of only works in the most commoditized situations (eg: "hire anyone with 6 months experience with React" or whatever.) The more specialized the recruiting search, the broader the range becomes: for example, "we need someone who knows technology X and Y, has been in industry A and has shown attributes B and C" they recognize they may end up hire a more junior or a more senior person and expect different things from them. So the role may pay 250 or it may pay 500 based on who you are. If you're in the 250-level experience range, it's meaningless for you to hear that it can go up to 500.