Real, anonymous reports from people who interviewed for Software Engineer at Verily, newest first and distilled into what to expect across the loop.
I got contacted by a recruiter and moved straight into a 45-minute phone screen. The coding there felt pretty straightforward—very OOP-flavored—and I finished in about 15–20 minutes, then spent the rest of the time just chatting with the interviewer. The recruiter response felt fast and the process ramped up immediately.
The early parts of the process felt oddly indifferent to me as a person and my background. I started with a 45-minute technical screening where the interviewer didn’t really ask about my prior experience at all. The vibe was that the process was there to test coding rather than understand what I’d done before.
The interview process typically begins with a short recruiter call, often focused on logistics rather than technical skills, followed by a 45-minute technical screening that emphasizes coding abilities over prior experience.
Candidates can expect multiple back-to-back coding interviews during the onsite, generally lasting 45 minutes each, with a focus on algorithmic problem-solving and coding under time constraints, often resembling LeetCode-style questions.
The coding challenges are reported to be of high difficulty, often requiring extensive preparation, and candidates may feel significant pressure to perform well under tight time limits, which can lead to a stressful experience.
After the technical rounds, there is typically a team matching step that assesses cultural fit, though feedback during this stage can be vague and the communication about next steps may be unclear.
Candidates frequently report a lack of meaningful feedback post-interview, leading to feelings of uncertainty and frustration, as the process can feel open-ended without a clear conclusion.
The overall experience can vary significantly, with some candidates noting logistical issues and prolonged timelines that contribute to a negative impression of the hiring process, despite the technical rigor.
