Smart colleagues.
Amazing engineering infrastructure in place.
Exponentially increasing bureaucracy to basic tasks, like creating design docs.
Re-orgs come without warning and seemingly without reason. Projects are shut down because some exec didn't like what they saw in a slide deck.
The company is increasingly corporate, focused on profits today instead of long-term plans.
Listen to employees and give products and teams time to bring products to maturity.
On-campus interview: two 45-minute sessions back to back. Very few to no behavioral questions were asked. The interviewers did not ask much about past experience, going straight to the technical portion. There were two programming questions, each i
I went through basic LeetCode-style questions, software engineering topics, and material from "Cracking the Coding Interview." The process involved a phone screen, a remote interview, and an onsite interview. It took a couple of weeks from start to f
From my experience, the Google interview process really tested my core CS fundamentals—especially in DSA and problem-solving. What stood out, however, was how much they valued clear communication and structured thinking. Beyond just writing code, I
On-campus interview: two 45-minute sessions back to back. Very few to no behavioral questions were asked. The interviewers did not ask much about past experience, going straight to the technical portion. There were two programming questions, each i
I went through basic LeetCode-style questions, software engineering topics, and material from "Cracking the Coding Interview." The process involved a phone screen, a remote interview, and an onsite interview. It took a couple of weeks from start to f
From my experience, the Google interview process really tested my core CS fundamentals—especially in DSA and problem-solving. What stood out, however, was how much they valued clear communication and structured thinking. Beyond just writing code, I