If I was reviewing only the big companies, Intel might have gotten a five-star rating. You work with top-notch people when you work at Intel. You learn a lot, and you'll be doing cutting-edge products. You'll also work with other big players in the industry.
Intel also tries to maintain your work-life balance, although that deviates at times.
Their way of working with other companies and customer care is the best I've seen. If Intel has set its mind to something, it'll make it happen, and it'll have your back. I mention this here because this translates to pretty good job security.
One of the perks I like is that in the USA, they have a 2-month sabbatical you earn every 7 years.
Intel has all the problems that all big companies have, starting at a fundamentally non-humane, soul-killing root (where civilization also starts). There's lots of brown-nosing that will suck the life out of you if you're not that type. Things happen slowly or not at all. There's an overwhelming feeling of the loss of sense of purpose. Decisions don't seem to make sense. IT support will waste a lot of your time and won't fix your problems. There will be way too many meetings, too many locks and rules, and lots of all kinds of time and money waste. You'll wonder if you're crazy, or if everyone around you is.
To put it briefly: just read a few Dilbert comic strips, and you'll get the picture (I imagine by now you know Dilbert is, unfortunately, the reality in big companies).
Push back on the greed for profit coming from the investors.
Remove the difference between green and blue badges (in places where it makes sense).
Ditch the 18-month work / 6-month break rule for contractors.
Intel's HR contacted me for an initial phone screen. This initial screen was with two engineers who were on the team for which I would be interviewing. The questions were technical, but nothing too heavy. Shortly thereafter, I was contacted to come
It was a phone coding challenge—no IDE or development platform was available. It was an unscheduled interview where the interviewer called me out of the blue one day. I had to describe code to my interviewer because there was no online platform for
Phone call interview about the basics of: * Algorithm * Computer Architecture * Operating Systems Mostly on: * Bit manipulation * Memory management * Process scheduling * Threads * Mutex * Semaphores * Locking mechanisms * IO
Intel's HR contacted me for an initial phone screen. This initial screen was with two engineers who were on the team for which I would be interviewing. The questions were technical, but nothing too heavy. Shortly thereafter, I was contacted to come
It was a phone coding challenge—no IDE or development platform was available. It was an unscheduled interview where the interviewer called me out of the blue one day. I had to describe code to my interviewer because there was no online platform for
Phone call interview about the basics of: * Algorithm * Computer Architecture * Operating Systems Mostly on: * Bit manipulation * Memory management * Process scheduling * Threads * Mutex * Semaphores * Locking mechanisms * IO