None that I can think of
Highly political and toxic environment with a lot of backstabbing and finger-pointing. Cronyism is widespread. Managers have a lot of power without any checks and balances. 360 feedback is a scam, as managers use it to manage folks with negative feedback out. ICs are essentially at the mercy of their manager.
Over time, the best leaders have left, and now you are left with incompetent managers who have zero EQ, questionable integrity, fragile egos, and are focused on empire-building. They see engineers as resources, aka slaves that can be easily replaced. This is especially true in the Kirkland office and in the cloud infrastructure development org. The management here is truly messed up, such that someone who is demoted for failure to deliver will again be given the same responsibilities. And this is not because the person has shown improvement, but because his replacement also messed up.
Joining the cloud infrastructure development org as a Software Engineer would mean that you are working on the ServiceNow platform and won't have much flexibility to innovate or try something new. The managers there have no development background and are scared of trying anything new that carries some amount of risk. They would rather be safe and let the platform team deal with all challenges. As an IC, you are not going to learn anything new that would help you grow unless your goal is to become a certified ServiceNow developer.
If you really want to improve the culture so that you can attract and retain top IC talent, then you need to get rid of the managers who are responsible for creating the toxic and political environment.
I was contacted by a recruiter about four weeks after submitting my resume. Typically, the process involves rounds of phone interviews followed by an onsite interview. The onsite interview lasted five hours and included five people, with most quest
Coding round Behavior round A typical software engineer interview assesses coding, algorithms, data structures, system design, problem-solving, debugging, communication, and cultural fit through technical challenges, behavioral questions, and discuss
2 DSA rounds, 1 system design round, 1 managerial round, and 1 HR round. Few questions related to my project and I was given a problem to solve: Merge n number of sorted arrays into a single array with O(k*logn) time complexity.
I was contacted by a recruiter about four weeks after submitting my resume. Typically, the process involves rounds of phone interviews followed by an onsite interview. The onsite interview lasted five hours and included five people, with most quest
Coding round Behavior round A typical software engineer interview assesses coding, algorithms, data structures, system design, problem-solving, debugging, communication, and cultural fit through technical challenges, behavioral questions, and discuss
2 DSA rounds, 1 system design round, 1 managerial round, and 1 HR round. Few questions related to my project and I was given a problem to solve: Merge n number of sorted arrays into a single array with O(k*logn) time complexity.