Good pay. Good benefits. Some really good people.
Extremely poor technical upskilling.
Poor management communication.
Management backing only a few of their ICs, especially those who are self-promoting (some with very little idea of what they are doing technically).
Learn the difference between speaking and communicating.
Pay attention to your ICs.
Have a general idea of what your ICs do day-to-day, and have a general idea of their skill level.
Actually do your job responsibilities, rather than delegating them to your ICs.
Take team building seriously.
The interview was conversational and focused on both technical knowledge and problem-solving approach. The interviewer was friendly, asked insightful questions, and gave space to explain my thought process clearly. I liked it.
The interviewer was very friendly. I had prepared a lot of Linux troubleshooting knowledge, but was not asked any questions about it at all. So, I totally screwed up. The coding interview was easy. It consisted of CSV data processing questions and
The interview process involved 5 rounds of coding phone interviews, plus an onsite interview. I failed the last phone interview. They checked for a mix of coding, OOD, and system design. I'll have a look at Cracking the Coding Interview.
The interview was conversational and focused on both technical knowledge and problem-solving approach. The interviewer was friendly, asked insightful questions, and gave space to explain my thought process clearly. I liked it.
The interviewer was very friendly. I had prepared a lot of Linux troubleshooting knowledge, but was not asked any questions about it at all. So, I totally screwed up. The coding interview was easy. It consisted of CSV data processing questions and
The interview process involved 5 rounds of coding phone interviews, plus an onsite interview. I failed the last phone interview. They checked for a mix of coding, OOD, and system design. I'll have a look at Cracking the Coding Interview.