It's a data-driven company, paving the way to be recruited without bias and business decisions taken without bias.
It's a data-driven company, and there are misinterpretations of data.
It's a good place with teammates citing your small helps, and a bad place with people around you giving data some spin.
Asking to code review counts will reduce documented discussion. Reducing ticket counts is not what you may be looking for in every team.
Long initial assessment, then long video interview. Both about 3 hours each, both pretty difficult. Process was overall pretty quick as it was just two stages, it was a lot of technical questions and a lot of questions about leadership principles.
Interview Process: * HR Screening * Coding Interview * Two onsite rounds with team members * Final round with the manager I was referred to go from an SDE II to SDE I, and then asked to interview for SRE. Since I felt I was being downgraded, I refu
Loop Interview Round 1 - 30 minutes LP followed by a LeetCode problem (Trees related) Round 2 - 2 coding questions: * One was similar to LRU cache. * The other was a matrix traversal in 8 directions (graph depth-first search). Round 3 - Behavioral
Long initial assessment, then long video interview. Both about 3 hours each, both pretty difficult. Process was overall pretty quick as it was just two stages, it was a lot of technical questions and a lot of questions about leadership principles.
Interview Process: * HR Screening * Coding Interview * Two onsite rounds with team members * Final round with the manager I was referred to go from an SDE II to SDE I, and then asked to interview for SRE. Since I felt I was being downgraded, I refu
Loop Interview Round 1 - 30 minutes LP followed by a LeetCode problem (Trees related) Round 2 - 2 coding questions: * One was similar to LRU cache. * The other was a matrix traversal in 8 directions (graph depth-first search). Round 3 - Behavioral