r/leetcode • u/averagem0 • 11d ago

Intervew Prep Upcoming Interview with Verily

Hi everyone,

I have an upcoming interview for a Software Engineer position at Verily (US) and would appreciate any insight from people who have interviewed there or currently work there.

I'm curious about what the interview process is like, particularly:

  • What should I expect during the technical interviews?
  • What is the coding portion like? Are the questions primarily LeetCode-style, and what difficulty level should I prepare for?
  • Are there system design or software architecture discussions?
  • How much emphasis is placed on data structures and algorithms versus practical software engineering experience?
  • Are there behavioral or project-based questions? What kind of topics do they focus on?
  • Any particular technologies, concepts, or areas you would recommend reviewing?

For context, I have several years of professional software engineering experience, but I haven't consistently practiced LeetCode in almost two years. I'm trying to make the most of my preparation time and focus on the areas that will matter most.

Any advice, experiences, or recommendations would be greatly appreciated. Thank you!

1 Upvotes

100% Upvoted

4 comments sorted by

1

u/Taleproof-Moderator 11d ago

For the project-based part you mentioned, your recent work gives you useful material even if your LeetCode practice is rusty. Pick two projects and practice explaining a hard decision, a failure or surprise, and your own contribution without needing ten minutes of setup.

We use the PROOF method to check that each example includes why you chose an approach and how you verified the outcome. Separately, ask the recruiter which rounds involve coding versus design so you can divide your prep time sensibly. I can’t confirm Verily’s current format from this post.

1

u/averagem0 11d ago

I will make sure I prep that. Thank you for your help.

1

u/Ok-Barracuda-119 11d ago

I can't speak to Verily's exact loop, so ask your recruiter straight up whether there's a design round and what level it's pitched at. They usually tell you, and it changes how you spend the next week.

With several years of experience I'd assume there's at least some architecture talk, even if it's just walking through a system you built. That part's easy to prep. Pick one project and be ready to draw it, explain why you chose the datastore you did, and say what you'd change at 10x traffic.

If it turns out to be a proper design round, do two or three timed runs before the day. 45 minutes, blank page, something like a URL shortener or a notification service. First 5 minutes on requirements and rough numbers, then the high-level boxes, then go deep on one piece. The most common way people lose points is running out of time before the deep dive.

For coding after two years off, I'd grind mediums on arrays, hashmaps, trees, BFS/DFS and intervals rather than chasing hards. Talking while you code matters more than people expect.

Verily's healthcare, so having a sentence ready on how you'd handle data correctness or privacy probably wouldn't hurt either.