Good stock option, which is totally luck and good timing based, to survive till that time.
Broadcom is completely dependent on legacy employees, who hold all project dependencies. No one can survive without their wish, as there are no project documents, and it's hard to grasp everything solely through source code.
The main strategy is to hire new "goats to slaughter" during layoffs. Hire new resources, don't give them space to survive, and then lay off the candidates before their stock matures (yearly). Then, hire new resources again. This is just to secure legacy employees' jobs and stability.
Management treats software professionals like slaves and expects them to work like robots.
Managers are totally dummy, non-technical, and unprofessional. They are not even able to realize the politics of legacy engineers. Here, managers just blindly follow instructions coming from the USA and lack any individual strength.
HR is totally worthless; they aim only to make employees' day-to-day lives hell. For example, they push software professionals to work from the office even during the COVID crisis (where around 50-60 employees are infected with corona in the office weekly). There is no WFH policy; it's just to fool external candidates.
Yes, there are good stock options, but they are just a carrot hanging on a pole in front of a goat, a part of a greedy algorithm to impress new hires, which they will never get.
These are not my individual thoughts. Just think 100 times before joining Broadcom, because once you are trapped in this situation, it is really tough to come out and find another similar-level job.
Just hire a technical manager who can take care of the dirty politics by legacy engineers.
Started by getting to know each other, followed by two technical questions. The questions considered data structure understanding; each solution should be implemented. I had two interviews there. In each, there were two interviewers (at least one was
Internally referred. Went through two phone interviews: * One with the hiring manager. * One with a team member. For the onsite interview, I met with 6 people. We mostly talked about the experience listed on my resume. Several simple and basic C pr
A quick call with clarification about university projects and a few behavioral questions, such as: * What is the project you are most proud of? * How would you start with the project you will be dealing with during your internship? etc.
Started by getting to know each other, followed by two technical questions. The questions considered data structure understanding; each solution should be implemented. I had two interviews there. In each, there were two interviewers (at least one was
Internally referred. Went through two phone interviews: * One with the hiring manager. * One with a team member. For the onsite interview, I met with 6 people. We mostly talked about the experience listed on my resume. Several simple and basic C pr
A quick call with clarification about university projects and a few behavioral questions, such as: * What is the project you are most proud of? * How would you start with the project you will be dealing with during your internship? etc.