Schedules and workload are very demanding; it's always a struggle to maintain work/home balance.
We need understanding spouses who will put up with either always being on VPN or working late at the office.
Email is crushing; the sheer volume is crazy.
Most of the year, you are blacked out from selling or buying any shares in the company. The stock always takes irrational wild gyrations during blackout periods, and you can't take advantage of it. But that's the downside of having truly honest and informative company meetings.
Obsession with cost control gets silly sometimes.
More realistic schedules: either get more resources or scale back projects.
Need more thermal chambers. Every engineering team (desktop graphics/mobile graphics/MCP/etc.) needs thermal chambers, and haggling during crunch time doesn't always work.
Need more lab space: buy, build, or rent more.
Choose between "growing a business unit" or "shooting for 40% margin". You can't get high margin without economy of scale, and you don't get economy of scale unless the business unit is well out of the "growing" phase.
People on the critical path all the time are burning out; need to grow bench depth in engineering.
Skip the annual "family day" event and give everyone a mandatory day off. Literally take down the server farm and shut off the power to the campus to force everyone to take time off.
Chips coming back days prior to the Christmas shutdown cause lots of collateral damage in family life.
It was good. They asked some technical questions about C++ and low-level systems. Then we went over OOP (Object-Oriented Programming) concepts. He was genuinely nice and interested to hear about my experience.
I was contacted by a recruiter after applying. Then, all correspondence seemed like boilerplate scheduling emails; I don't think the recruiter/scheduler spent any time crafting custom responses. I did an initial informational/technical screening, fo
The interview process consisted of two tech screens, followed by a panel. Interview questions were standard design problems, targeting both Verilog coding ability and problem-solving skills. Interviewers looked more at thought process than specific s
It was good. They asked some technical questions about C++ and low-level systems. Then we went over OOP (Object-Oriented Programming) concepts. He was genuinely nice and interested to hear about my experience.
I was contacted by a recruiter after applying. Then, all correspondence seemed like boilerplate scheduling emails; I don't think the recruiter/scheduler spent any time crafting custom responses. I did an initial informational/technical screening, fo
The interview process consisted of two tech screens, followed by a panel. Interview questions were standard design problems, targeting both Verilog coding ability and problem-solving skills. Interviewers looked more at thought process than specific s