Verily Software Engineer candidates describe a coding-heavy process: a recruiter or phone screen, timed LeetCode-style rounds, a multi-interview onsite, and sometimes a slow team-matching stage.
$152K
Avg. Base Comp
$196K
Avg. Total Comp
3-6 rounds
Typical Rounds
Not reported
Process Length
Candidates describe the Verily Software Engineer process as coding-first, with a lot of time spent on algorithms and little on past experience. Several report a recruiter contact or phone screen, then a 45-minute coding interview, then an onsite or "super day" of four or more technical interviews. One candidate reports five coding rounds plus a team-fit conversation at the onsite stage.
The reported problems are mostly medium-difficulty: linked lists, DFS, a problem similar to Container With Most Water, strings and arrays, and dynamic programming. One candidate also heard that later rounds leaned on trees, backtracking and stacks. A few say the prompts were deliberately vague, so asking clarifying questions and talking through assumptions mattered. Others describe a Python task that simulated a processor, a Java class built from scratch, and a LeetCode-hard style screen with only about 35 usable minutes.
One candidate reports a different mix: a graph problem, a DP problem and a system design question about ingesting wearable-device data. The design discussion covered idempotency, partitioning, schema evolution and fault tolerance. Behavioral questions are less commonly reported, but that candidate mentions pushing back on a product decision and describing a system that did not scale as expected.
The reported outcomes are what applicants should plan around. Every report here ended without an offer. Several describe slow or vague communication after the interviews, and some say the rejection came after positive interview feedback. Ask the recruiter to confirm the round format and the expected decision timeline up front.
Synthesized from 12 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.
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 | |
| Last Transaction | |
| Size of Joins | |
| Total Spent on Products | |
| Cumulative Distribution | |
| P-value to a Layman | |
| Retailer Data Warehouse | |
| Bagging vs Boosting | |
| Google Maps Improvement | |
| Cumulative Reset | |
| Always Excited Users | |
| Type I and II Errors | |
| The Brackets Problem | |
| Justify a Neural Network | |
| Subscription Retention | |
| Valid Anagram | |
| Ranking Metrics | |
| String Mapping | |
| Sort Strings | |
| Brain Cancer Treatment Outcomes | |
| Sum to Zero | |
| Flatten JSON | |
| Find Duplicate Numbers in a List | |
| Swap Variables | |
| Success Measurement |
Synthesized from candidate reports. Individual experiences may vary.
Candidates typically report a recruiter email or call first, sometimes a 30-minute general conversation. One candidate reports going straight into a 45-minute technical screen with no recruiter call and no questions about their experience. Confirm the format with recruiting early.
Candidates report a live coding interview of about 45 minutes. Reports include a Python OOP-style problem, a linked-list problem, and a LeetCode-hard style problem with about 35 usable minutes after introductions. One candidate described an interviewer who mostly watched silently rather than collaborating.
Candidates report onsite or super-day loops of four or five coding interviews, usually about 45 minutes each, with a final team-fit call or conversation. Topics reported include dynamic programming, strings, arrays, DFS and a Container With Most Water-style problem. One candidate heard that trees, backtracking and stacks also come up. A few report vague prompts, so clarifying questions may help.
Some candidates report general system design questions. One reports designing a near-real-time wearable data pipeline, with follow-ups on idempotency, partitioning and schema evolution. Behavioral prompts reported include pushing back on a product decision and describing a system that did not scale as expected. These appear less consistently than coding rounds.
Several candidates report a team-matching or team-fit stage and then a rejection, sometimes days or weeks after positive feedback. One describes months of follow-ups before a late rejection. Applicants may want to ask recruiters for a concrete decision date.
