A Google software engineer who previously worked at Twitch compares the two companies' interview processes and work cultures
Briefly

A Google software engineer who previously worked at Twitch compares the two companies' interview processes and work cultures
"Nair found the interview process at both companies to be "fairly similar," he said, with strong emphasis on problem-solving, coding skills, and system design. "Each company evaluated candidates for both technical expertise and cultural fit," Nair said, through four to five technical interviews and then a cultural-fit assessment. However, he found Google's technical interview process to be the hardest out of the Big Tech companies he's interviewed at."
""It really tested my core understanding of computer science fundamentals and applying creative solutions to different problems," he said. He added that Google's interview process also involved an additional process designed to match each candidate to a team that fit with the candidate's skills and interests. This differed from his experience with the other companies, which he said typically have candidates interview directly with the hiring team."
Goutam Nair, 29, has been a software engineer at Google's Mountain View headquarters since May 2022. Prior to Google, Nair spent over three years as a software engineer focused on machine learning at Twitch in San Francisco and completed a two-and-a-half-month software engineering internship in 2018 at another Magnificent 7 company. Both Google and Twitch interview processes emphasize problem-solving, coding, and system design and typically include four to five technical interviews followed by a cultural-fit assessment. Google's technical interviews are notably harder, testing core computer science fundamentals and creative solutions. Google uses an additional step to match candidates to teams, while Twitch emphasizes moving fast, adapting quickly, and a bottom-up, fast-paced culture with a contrasting, more welcoming and methodical onboarding at Google.
Read at Business Insider
Unable to calculate read time
[
|
]