Successful But Long Hours
Successful But Long Hours
An industry-leading company that responds to customer demands quickly.
I am on a successful project, so customer demands can result in long hours because of the number of customers using our product.
Since the company is so customer-focused, we tend to be reactive rather than proactive.
Try to build up successful teams while also cutting the less successful. Don't use blanket policies that can hurt some parts of your company. Understand better the teams you are managing and make decisions for each group based on the business needs of each group.
Was this helpful?
Broadcom Interview Experiences
Principal Software Engineer
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
Principal Software Engineer
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
Principal Software Engineer
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.
Principal Software Engineer
Santa Clara, California, United StatesFebruary 1, 2012First, 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
Principal Software Engineer
Santa Clara, California, United StatesJuly 1, 2009To 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
Principal Software Engineer
United StatesJanuary 17, 2022C: - 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.
