A lot of great people work here, and compared to all the other companies, the benefits and compensation are above average.
Actions speak louder than words. My experience as a lower-grade employee (3, 5, 6, 7) has shown me that I've felt undervalued. When I first joined, I felt the complete opposite, but there has been a negative trend starting before I joined. Lowering 401k contributions, removing GPTW freebies, removing quarterlies, dismal focal/insight budgets, ACT (layoffs), frequent hiring freezes, BU-specific bonuses (CCG/DCG), frequent reorgs, and exorbitant exec compensation have all contributed to this trend. It is no longer a company I am proud to work for; it is now just a paycheck.
For a company of Intel's size, the compensation for software engineers is so far off that it is a demotivating distraction.
Don't give out huge allotments of RSUs to fix the compensation for only 25% of employees unless you truly believe that they are the only critical talent.
Things are so messed up now. With these critical retention bonuses, you now have lower grades making more than higher grades. Also, new hires are getting these RSUs as well.
So, you now have Grade 5 RCGs making the same as an experienced Grade 7. How is this fair?
I guess if you want to motivate experienced engineers to leave, this is one way to do it.
Two phone interviews followed by being flown in for a day's worth of interviews on campus. People were dressed extremely casually and seemed pretty laid back. Most questions were relevant to the materials on my resume, but some were very odd and slig
It really depends on the team you interview with. Generally, we hire folks as contractors, and then if they work out, we try to bring them on as full-time. A phone interview is used to screen, and then an in-person interview follows if things go we
Each interviewer brings in his test of the day, which includes an IQ test and programming questions. This was okay. I missed one question regarding Mutexes. I aced all IQ-type questions and system architectural questions. I have never been turned d
Two phone interviews followed by being flown in for a day's worth of interviews on campus. People were dressed extremely casually and seemed pretty laid back. Most questions were relevant to the materials on my resume, but some were very odd and slig
It really depends on the team you interview with. Generally, we hire folks as contractors, and then if they work out, we try to bring them on as full-time. A phone interview is used to screen, and then an in-person interview follows if things go we
Each interviewer brings in his test of the day, which includes an IQ test and programming questions. This was okay. I missed one question regarding Mutexes. I aced all IQ-type questions and system architectural questions. I have never been turned d