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.
Synthesized from 4 candidate 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.
Three rounds total. First was a recruiter screen, pretty standard, no surprises. Second was a technical round with a senior engineer, two LeetCode-style problems, one graph traversal and one dynamic programming question. I felt confident on the graph problem since I'd worked through similar ones recently, but the DP question caught me off guard because the optimal solution required a space optimization I didn't see until they hinted at it. Third round was a system design where I had to design a data pipeline for processing health metrics at scale. That one I actually enjoyed since it's close to work I've done. The part that made me sweat was when the interviewer pushed hard on fault tolerance and exactly-once delivery semantics. I had a solid answer but not a perfect one. Overall the interviewers were sharp but fair, and the process felt well-organized.
Questions asked: Technical screen: "Given a list of patient vitals with timestamps, find the longest streak where heart rate stayed within a healthy range." Follow-up was to optimize for memory. Second problem was a variant of word break using DP. System design: "Design a pipeline to ingest and process wearable device data from millions of users in near real-time, with support for late-arriving data." They specifically asked about idempotency, partitioning strategy, and how you'd handle schema evolution over time. Behavioral questions woven in throughout: "Tell me about a time you had to push back on a product decision" and "Describe a system you designed that didn't scale the way you expected." One interviewer asked a quick estimation question: how many data points per day would Verily's Study Watch generate across a 10,000-person trial.
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 | |
|---|---|
| Detecting ECG Tachycardia Runs | |
| Hurdles In Data Projects | |
| Client Solution Pushback | |
| 2nd Highest Salary | |
| Prime to N | |
| Cumulative Distribution | |
| P-value to a Layman | |
| Retailer Data Warehouse | |
| Total Spent on Products | |
| Size of Joins | |
| Bagging vs Boosting | |
| Last Transaction | |
| The Brackets Problem | |
| Valid Anagram | |
| Always Excited Users | |
| Sort Strings | |
| String Mapping | |
| Brain Cancer Treatment Outcomes | |
| Sum to Zero | |
| Flatten JSON | |
| Find Duplicate Numbers in a List | |
| Success Measurement | |
| Priority Queue Using Linked List | |
| Cumulative Reset | |
| Rider Discount | |
| Customer Success vs. Free Trial | |
| Digit Accumulator | |
| Time Difference | |
| Search Linked List |
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.