Great coworkers, tooling, and the ability to work at scale.
Working at scale and a defensive programming philosophy can lead to slower velocity until you really get the hang of the system.
I had a virtual onsite interview for L4. One week after the interview, I was told that I had been approved for L3. A few days later, I was informed that the decision had changed and my status was HOLD, with extra interviews scheduled. These extra i
I applied online via a link provided by my university. After applying online, several weeks went by before I heard back. They asked me for my available times for a phone interview. The phone interview was scheduled for a week later, and they gave s
I applied for a Google SWE position and went through a recruiter call first. The recruiter was very friendly and clear about the process. My phone screen had two coding questions: * One on arrays (two sum variant) * Another on dynamic programming (u
I had a virtual onsite interview for L4. One week after the interview, I was told that I had been approved for L3. A few days later, I was informed that the decision had changed and my status was HOLD, with extra interviews scheduled. These extra i
I applied online via a link provided by my university. After applying online, several weeks went by before I heard back. They asked me for my available times for a phone interview. The phone interview was scheduled for a week later, and they gave s
I applied for a Google SWE position and went through a recruiter call first. The recruiter was very friendly and clear about the process. My phone screen had two coding questions: * One on arrays (two sum variant) * Another on dynamic programming (u