The interview process was straightforward and well-outlined by the recruiter.

It begins with an initial screening with the recruiter to determine if you are a good fit. If they believe you are, your recruiter will extend an opportunity to do a Karat interview.

This is a LeetCode-style virtual interview outsourced to a third party (Karat) rather than performed by Indeed itself. Working in Karat's text editor, you'll be asked to solve progressively harder problems within a short time window (50 minutes). Aim to solve three problems, but at a minimum, you should solve two completely (I only solved two).

After this, Karat will provide Indeed with a video of the interview as well as their recommendation. A perk of this approach is that if you feel you didn't perform well on your first attempt, you can opt to take it again.

Finally, if Indeed is happy with those results, they will ask you to perform a virtual onsite. This consists of 4-5 back-to-back interviews with various members of different teams (usually 2-3 interviewers per call).

My Super Day included:

• Two Indeed-led whiteboard sessions
• One 'ProgEx'
• One resume deep dive

The whiteboard sessions were not very difficult, and the interviewer provided ample direction to help you find the best answer. The ProgEx was a longer session (I believe 105 minutes) and asked you to build a work-related program. You are expected to finish this and pass all test cases. Honestly, I ran out of time and don't think mine even compiled. That said, focus on writing good, clean, and thorough code; even if it doesn't compile, they will evaluate your performance.

Finally, the resume review was a standard behavioral interview, designed to uncover good project/leadership experience. Be sure to go into detail here about what you have specifically done to build software in teams.

The progex question asked you to devise a program that would perform a fuzzy search of job posts. Fuzzy search means finding the top 10 job postings with the most matching keywords.

The input will provide you with x job postings to load and cache, and y job searches to perform. Your program should then output the best job postings for each search to the screen.

At the end, you are asked some follow-up questions about runtime and how you would improve this moving forward.