Great pay. Flexible hours. Potentially interesting projects (depending on team). You will learn a lot.
Extreme bureaucracy, people constantly quitting, aggressive deadlines (usually at the expense of quality software development), poor internal tools, operational burdens/tech debt.
It's not anything near as bad as the infamous NYT article, but it is pretty bad for a lot of other reasons.
There's no way to fix the problems at this point, even if there was a strong desire to.
There was an OA, a phone round with the recruiter, and then a loop with the panel. This included medium and hard LeetCode problems, followed by system design.
The first round was a two-question online assessment. The second round was a virtual onsite with four rounds. Each round, the interviewer spent about 30 minutes covering leadership principle questions and left about 30 minutes for technical coding
The interview process is too lengthy. It includes an online assessment that lasts for 4 hours, followed by a panel round consisting of three back-to-back interviews: one for LeetCode, one for system design, and one behavioral interview. My interview
There was an OA, a phone round with the recruiter, and then a loop with the panel. This included medium and hard LeetCode problems, followed by system design.
The first round was a two-question online assessment. The second round was a virtual onsite with four rounds. Each round, the interviewer spent about 30 minutes covering leadership principle questions and left about 30 minutes for technical coding
The interview process is too lengthy. It includes an online assessment that lasts for 4 hours, followed by a panel round consisting of three back-to-back interviews: one for LeetCode, one for system design, and one behavioral interview. My interview