Used to be more like Google. Andy used to be more forthcoming. Some teams are shielded better than others.
Verily’s projects are consistently understaffed, and stress levels reflect that.
Verily calls itself a startup when it suits them (minimal resources, cutting benefits, work/life balance problems) and plays up the message that they come from Google when it suits them (any external messaging).
Requests for transparency from leadership are met with answers that downplay the issues or outright say that there are no problems.
Dissatisfaction and attrition from rank-and-file employees.
The new COO seems like a good change, but it may be too little too late after years of C-levels telling us that the problems we see and experience daily don’t actually exist.
Executives and middle managers focus on denouncing leakers while ignoring the underlying problems within the company.
Would not recommend as a place to work for those concerned with DEI.
Too much reliance on promoting “the mission.” The mission should be used to motivate people, not be used as justification to guilt people when they question cost-cutting.
Promotions are very political.
Verily used to be Google, but it isn’t anymore. As of today, the benefits are strictly worse.
Figure out tangible things for why people would look at Verily versus Google and choose to work at Verily, and then promote those. It can’t just be for the mission.
Transparency has been reduced because people are leaking things to the press. This unfortunately has further sowed distrust in leadership. Don’t give up on being honest with your employees.
Recruiter Screen – 20–30 min, background, motivation, compensation. Technical Screen – 45–60 min, coding + DS&A over Google Meet. On-Site Loop – 4–6 rounds (coding, system design, domain knowledge, behavioral). Virtual or in-person. Hiring Committ
Google Meets coding exercise with 2 developers. I was asked 1 coding question after initially meeting with the recruiter. The next step would have been a 4-hour in-person interview.
A recruiter contacted me for a 30-minute phone call. The recruiter was kind and liked my enthusiasm for integrating software with life sciences. I was later scheduled for a phone interview. During the interview, I was completely lost.
Recruiter Screen – 20–30 min, background, motivation, compensation. Technical Screen – 45–60 min, coding + DS&A over Google Meet. On-Site Loop – 4–6 rounds (coding, system design, domain knowledge, behavioral). Virtual or in-person. Hiring Committ
Google Meets coding exercise with 2 developers. I was asked 1 coding question after initially meeting with the recruiter. The next step would have been a 4-hour in-person interview.
A recruiter contacted me for a 30-minute phone call. The recruiter was kind and liked my enthusiasm for integrating software with life sciences. I was later scheduled for a phone interview. During the interview, I was completely lost.