Thread regarding Intel Corp. layoffs

Note to engineers who think they're not good enough to leave

Honestly, you may be right. It depends on how much you fought to learn useful real technical skills during your career there. TLDR: if you want to leave for greener pastures, you had better get good with technical fundamentals. None of this powerpoint BS or running pointless workgroups.

I was laid off from Intel after 10+ years in the March 2020 timeframe. Pure politics. It wasn't even my real manager who did it, he was a great guy, but had to jump ship before the layoffs really happened. I was a good technical engineer who was getting Level2 RSU grants during Focal and out-of-cycle raises and RSU grants. So I was thrown into interviewing at various companies and the questions asked revolved around stuff I had always been interested in, but never got the chance to get involved in during my career. I got rejected a good bit. After a lot of studying and luck, I finally managed to land a FAANG level job doing actual hardcore technical work and a 30% bump in total compensation. No lie. I still can't believe I'm getting paid this much to do actual fun technical work rather than BS stuff with wrangling tools, dealing with c-appy documentation, or constantly fighting colleagues to develop my skills.

I still have a lot of good colleagues who are early to mid career who feel like they are stuck at Intel. Various Intel engineering groups have perfected the art of dumping so much menial work on you, that you don't have time (or even need to) learn the nitty gritty technical details. Younger engineers "think" they are learning useful skills applicable across all industry and don't really know otherwise. There's a lot of information hoarding from more senior level engineers and architects in order to keep you dumb and stall your career. The culture is so deep rooted that even JK couldn't fix this mess and left after 2 years. A lot of senior engineers who have been with the company a long time realize that with the years of experience they may have, they really should be better compared to industry, so since they are stuck at Intel, and they will fight to protect what little they know in order to prevent younger engineers from getting better.

The grass really is greener on the other side for most individual technical contributors. Realize you can be better with some hard work and make sure you are developing technically.

by
| 3516 views | | 11 replies (last September 6, 2020) | Reply
Post ID: @OP+16wAltzA

11 replies (most recent on top)

Dear youngsters, study and learn from this thread.

by
| | Reply
Post ID: @iclv+16wAltzA

Yeah, at this point, I’m learning the technical details not because they’ll help me do my job better, but because I need them for interviews. But then again, they could give a different view point on problems even if they don’t get me promoted.

by
| | Reply
Post ID: @3het+16wAltzA

I am not sure there are no opportunities in Intel based on interviewing. Definitely does not seem like much bs going on. These interviews have made me think in ways that I don’t in my daily work. I’m actually happy to follow up on their questions and have been learning more. Like I said, it’s an intense process, but at least I know the relevance of these questions. It seems like a small area that is essential, but works in the background.

If not for this one group, I’d agree with the OP completely.

by
| | Reply
Post ID: @3owe+16wAltzA

OP, a lot of the people who know they cannot get a job anywhere else are the politicians who managed to backstab their way to gr10+ and know they are grossly overpaid for the zero technical work they do. They will never get a job anywhere else because no company will pay that much for someone who is less competent than a good new grad.

by
| | Reply
Post ID: @2yvx+16wAltzA

Intel has too many people. This is a natural outcome and it is by design. It creates competition among engineers so the company benefits. Also, back in the days when it was the king, the management wants the knowledge to be in such small fragments that nobody who goes working for a competitor knew much at all. This dovetails into each manager's need for expanding his/her turf and the structure is set. The good thing was there is plenty of money to pay for all that idle headcount.

One of the down side is those who know very little eventually become managers themselves. It was a good show when Grove was whipping id–ts. It became a comical mess when those id–ts become bosses themselves. They have no expertise and their insecurity led them to hire certain people who always tell them optimistic tales. Now you have a gigantic organization and a lot of soon to be obsolete fabs. Both are very expensive to keep.

by
| | Reply
Post ID: @2kcq+16wAltzA

It is odd to think “I can’t get a job anywhere else” while at the same time being told how awesome intel is. The truth is, intel is not awesome and jobs are out there if you put in the effort.

by
| | Reply
Post ID: @1uaa+16wAltzA

@ghm+16wAltzA
Sounds like you have talent. Go Freelance.

by
| | Reply
Post ID: @1vqx+16wAltzA

Paraphrased: I hoarded info to save my own skin.

Wow, I was hoping people at Intel were better than this, but damn. I don’t think my organization is that bad since people have too much stuff to do to not show younger engineers how to do things, but it’s still crazy that this thought can exist at this company. Saving your own skin is not an excuse to stunt the growth of people coming behind you; people in high places with the mentality of saving their own skin is likely how we’re in this situation to begin with. Thanks for your honesty.

by
| | Reply
Post ID: @ecw+16wAltzA

I can see OPs point about hoarding information. I'm still at Intel, a G7 (designer) who can easily do most of a G9 (architect) work. However, I get the impression the G9 architect is constantly trying to credit vulture my ideas and work when in group settings, in order to maintain she is really in charge. When it comes to reciprocation in terms of sharing information, I always get brushed aside. Someone two grade levels above should not be fighting for recognition from somebody two levels below. If the the majority of info a G9 knows is easily taught to a G7, then the person who is G9 probably should not be a G9.

by
| | Reply
Post ID: @yji+16wAltzA

I have to add a little advice, if you want to learn skills, consulting is the way to go. Taking training and using the tech in your current job will get you only so far. The real experience comes from seeing how different companies work with the technology. In other words, experience counts.

by
| | Reply
Post ID: @sln+16wAltzA

I'd like to respond to the statement about older engineers hoarding information, I'm an older (female) engineer so I can speak to this. In my career, I've seen more layoffs than I care to count. Some companies have what I call a layoff cultire. These companies have regular layoffs and the only way to survive was to do things no one else can do or no one else cares to do/learn.

My first layoff I was given the task to train a far junior team member on my processes and duties (I was at financial institution and I automated most of my work). So, here I was, about to be laid off and I had to turn over the tools I built for myself and then train someone to take my job. This person had none of the skills needed to do this work but because I had built tools that made things easy, I was laid off in favor of someone with a far lower, non-engineer salary. And, being my first job out of college, I was making entry level engineer dollars.

I don't know if this will mean anything to you but we older engineers are not against young engineers. We just want to work too!

by
| | Reply
Post ID: @ghm+16wAltzA

Post a reply

: