Lots of cool projects on which to work with top-tier customers and competitive compensation plans, composed of base salary, stock (RSUs), annual bonus, and ESPP.
The vacation policy is awful. There is no accrued entitled vacation. Instead, employees can take time off when their schedule allows, with manager approval.
But the schedules of highly utilized employees never have open time (and who would feel secure if they weren't utilized?). How can you predict your schedule in order to plan vacations months in advance? The system is extremely biased based upon one's manager's philosophy of employee downtime.
Also, although there are classes offered on advancement and an advancement roadmap, I've been in the exact same position for several years, even though my reviews have always been excellent.
I know you guys know the vacation policy is terrible, even though you had the nerve to promote it as better than the previous accrual-based system.
This is because none of the copious surveys have asked about it since its inception, nor has it ever been brought up again.
Also, I realize bloated director salaries are the norm today, but Broadcom seems to be one of the more extreme examples. Directors continue to get 10-50 million dollar bonuses, even though the company's performance has been anything but stellar.
Why don't you put some questions about this on the next survey?
First, a simple phone screen, with no much technical stuff. Then, an on-site interview, with maybe around 4-5 people. All questions will be technical, and most questions will relate to your resume. After that, you should hear the result in 2-3 wee
To start, a recruiter scheduled a telephonic interview with a hiring manager who was himself a Sr. Principal Engineer. The interview lasted for an hour. The interview was difficult, and it appeared the interviewer asked questions primarily based on
C: - Data structures - Embedded basics - State machines Questions on previous positions to understand knowledge depth. Challenging issues solved in previous jobs. Systems design questions. RTOS problems. Architectural system design questions.
First, a simple phone screen, with no much technical stuff. Then, an on-site interview, with maybe around 4-5 people. All questions will be technical, and most questions will relate to your resume. After that, you should hear the result in 2-3 wee
To start, a recruiter scheduled a telephonic interview with a hiring manager who was himself a Sr. Principal Engineer. The interview lasted for an hour. The interview was difficult, and it appeared the interviewer asked questions primarily based on
C: - Data structures - Embedded basics - State machines Questions on previous positions to understand knowledge depth. Challenging issues solved in previous jobs. Systems design questions. RTOS problems. Architectural system design questions.