Verily Software Engineer interview typically runs 3-6 rounds: recruiter screen, technical screen, coding rounds, onsite, and team fit. The process often takes several weeks to months and is coding-heavy with little hand-holding.
$125K
Avg. Base Comp
$230K
Avg. Total Comp
4-7
Typical Rounds
3-8 weeks
Process Length
We've seen a consistent pattern at Verily: the interviewers care far more about how you reason through an unfamiliar problem than about polished storytelling or a flashy background. Multiple candidates said the process felt coding-first and even impersonal, with little interest in prior experience or stack specifics. That means the signal is not whether you can recite a framework or domain buzzwords; it’s whether you can stay precise when the prompt is underspecified, build the right assumptions, and keep your solution clean under pressure.
A recurring theme is that Verily likes problems that start simple and then layer on complexity. Candidates reported everything from insertion sort and basic OOP-style implementation to processor simulation, trees, backtracking, stacks, strings, arrays, and even a hard-style composite problem. The non-obvious trap is that several people were caught off guard by the amount of ambiguity and the limited hand-holding. We’ve seen that candidates who do best here are the ones who clarify the problem early and narrate tradeoffs clearly, because the interviewers often seem to be watching for disciplined thinking more than speed alone.
Another pattern worth noting is the tone: several candidates described interviewers as proctors rather than collaborators, and one even mentioned repeated questions across rounds. That makes consistency matter. If your answers drift or you rely on the interviewer to rescue you, it tends to show quickly. Verily appears to reward candidates who can keep their implementation tight, ask the right questions, and remain composed when the process feels a little uneven or less polished than expected.
Synthetized from 4 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Verily process.
The part that caught me off guard was the coding section, mostly because it was not explained very clearly up front. I ended up going through multiple rounds over several weeks, starting with a hiring manager interview and then moving into several team rounds. The technical interviews were all about 45 minutes each, and I scheduled them close together so I could get them done in one stretch. The questions were pretty standard software engineering ones, but they were medium difficulty and definitely not the kind where everything is spelled out for you like on LeetCode. I had to ask clarifying questions before jumping into an answer, otherwise it would have been easy to waste time solving the wrong version of the problem. One of the coding questions I remember was insertion sort, and there were also some repeated questions across rounds, which made the process feel a little less polished than I expected.
Overall, I’d describe the interview as fair but a bit messy in execution. The technical bar was reasonable, but the limited information and the unexpected coding portion meant you had to stay alert and communicate well. I hadn’t really prepared for that style of interview beforehand, so that was the main lesson for me. If I were doing it again, I’d practice talking through assumptions out loud and making sure I clarify the problem before writing anything. I didn’t get an offer in the end, but I do think someone who is comfortable with medium-level coding questions and a less structured interview flow would have a good shot.
Prep tip from this candidate
Practice medium-difficulty coding questions in a format where the prompt is intentionally underspecified, and get comfortable asking clarifying questions before you start solving. Also be ready for a coding round that may be introduced less clearly than you expect, since that was the most surprising part of the process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Verily
Return keys with weighted probabilities
| Question | |
|---|---|
| 2nd Highest Salary | |
| Prime to N | |
| P-value to a Layman | |
| Cumulative Distribution | |
| Hurdles In Data Projects | |
| Last Transaction | |
| Size of Joins | |
| The Brackets Problem | |
| Valid Anagram | |
| Always Excited Users | |
| String Mapping | |
| Brain Cancer Treatment Outcomes | |
| Total Spent on Products | |
| Sum to Zero | |
| Find Duplicate Numbers in a List | |
| Flatten JSON | |
| Cumulative Reset | |
| Search Linked List | |
| Time Difference | |
| String Palindromes | |
| Prime Numbers Identification | |
| Common Prefix | |
| Greatest Common Denominator | |
| Subscription Retention | |
| Type I and II Errors | |
| Possible Triangles | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Moving Window | |
| Combinational Dice Rolls |
Synthesized from candidate reports. Individual experiences may vary.
The process often starts with a recruiter reaching out and scheduling a short phone screen. This call is usually general and lightweight, with basic questions about your background and fit, and in some cases candidates reported going straight into technical screening with no recruiter conversation at all.
This is a coding-first interview focused on fundamentals rather than LeetCode-heavy memorization. Candidates reported live coding in Python or Java, with medium-to-hard problems that may build on themselves, and interviewers expect you to clarify assumptions and talk through your approach.
Candidates who pass the screen are moved into several more technical rounds, often with team members or developers. These interviews can include hands-on coding exercises, algorithmic problems involving trees, backtracking, stacks, arrays, strings, dynamic programming, and occasional system design questions, with some rounds feeling more bare-bones and less collaborative.
The onsite-style stage is typically a sequence of four back-to-back 45-minute technical interviews. Interviewees described it as a demanding coding-heavy day with little room for behavioral discussion, and one experience also included a final team fit call after the technical rounds.
After the technical rounds, some candidates go through a team matching or final fit conversation. This step appears to focus on whether there is a good match with a specific team, but candidates noted that a positive team match does not necessarily guarantee an offer.