I have been preparing and giving interviews for almost 2 yrs now. I have interviewed with almost all the hardware companies that I can think of and also many startups. I haven't got a single offer. Obviously I'm missing something which is why I'm getting so many rejects but I really need help in improving. Life at my team is like going through hell. I really want to change but I'm failing at each and every step. I'm asking for some serious help if you guys know of a forum where people can help preparing for a design engineer position, is there some Meetup or group where people help each to crack an hardware interview?
Are you able to clear phone screens?
YOE?
1. What exactly are you doing currently (role)? 2. Are you applying for relevant roles and getting called likewise? 3. As pogs posted, YOE? 4. What are your expectations?
I'm doing DFT. I want to move to logic design and those are the jobs that I'm applying for. I have 4 yrs of experience in DFT but 0 in logic design side. I want to move from DFT to logic design and micro architecture asap.
It's hard to convince a company to hire you into a role you have no experience in. I recommend reaching out to managers within Intel that have roles you want. Gain some experience within Intel first then apply externally. Even a short term assignment within Intel will improve your chance to get noticed by recruiters.
I have been trying that for quite some time now. Even within intel, they are looking for experienced candidates
I would recommend the same. Maybe yoyu can try a role which is part design part something you know. That way you will be a kind of safe bet for the new boss
Have you tried taking online courses with hands on projects? That might help you gain skills in design or verification
Alright, I'll give it to you. Its kinda hard to move to a logic design role. When I tried to move into a new company and move out of my back end role, they would not take me seriously. They look at your experience and immediately think you might know something tangential at the least, but when they do call you in they'll venture into a traditional hardware interview. I knew it'll be hard to convince people outside, so I looked inside Intel. I used edaplayground to code, picked up sunburst design papers and started going through them one by one. When I started interviewing inside Intel this practice made a big difference, you run into some weird scenarios when you actually code, that changes how you perceive a problem and solve it instead of just prepping and reading it "n" times. I'm not sure what you're failing at but you should be honest with yourself and accumulate a list of weakness, right them down, target them, smash them out. This worked for me, I'm in a logic design role and I work on UVM development as well
PM me