Fast pace, collaboration with other teams, great employee discounts, paid time off during Thanksgiving and between Xmas and New Year (because a lot of holidays are work days here).
Almost constantly on call, not much of a work time and off time difference. It really depends on your assignment, politics, and rivalry between teams.
Too much secrecy between teams and projects makes work very inefficient.
Having less rivalry and competition may actually encourage better collaboration between teams and prevent disasters like antenna gate and calendar day time-saving switchover.
A recruiter approached me for the role of Deep Learning FW Engineer. I was told by the recruiter that the team wanted to have a conversation about my background and the role they had. (It was never intended to be a telephonic screening.) But, it i
Overall smooth. Had 3 interviews: one behavioral and 2 technical. Heavy system design and debugging. Interviewers were nice, standard interview format with an introduction and then mostly technical questions. Some OOP concepts needed as well.
It was a pretty standard big tech interview process. At a high level, it had the following steps: * Recruiter call * Hiring Manager screen * Technical phone screen * Onsite
A recruiter approached me for the role of Deep Learning FW Engineer. I was told by the recruiter that the team wanted to have a conversation about my background and the role they had. (It was never intended to be a telephonic screening.) But, it i
Overall smooth. Had 3 interviews: one behavioral and 2 technical. Heavy system design and debugging. Interviewers were nice, standard interview format with an introduction and then mostly technical questions. Some OOP concepts needed as well.
It was a pretty standard big tech interview process. At a high level, it had the following steps: * Recruiter call * Hiring Manager screen * Technical phone screen * Onsite