First, I was contacted by a college recruiter on LinkedIn and we set up a phone interview.

The call lasted about 15 minutes. We discussed my background, interests, and the Google interview process.

Next, the recruiter forwarded my preferred technical interview times to a recruiting coordinator to set up a technical interview.

The technical interview started with the interviewer briefly discussing what they do for Google and asking a couple of questions about projects on my resume. Then we jumped into the technical questions.

I won't give the exact questions, but instead a general idea of what was asked.

1. The first question involved returning true or false for some condition regarding two input intervals. This could be approached in a simple one-line return statement (by approaching it as when is the input going to return false) or a less optimal solution of finding all of the cases where true is returned. I wasn't thinking clearly and took the less optimal route. I realized that wasn't the best way after the interview.

2. The second question was basically an expansion of the first question. Given two inputs, a list of intervals and another interval, the function from part one could be used to do something with the list of intervals. I ran out of time to code it for the final edge case to be completely functional, but told the interviewer what had to be done to make it work for all cases.

The questions were not really difficult or unexpected, but making silly mistakes led to a less optimal or not entirely functional solution.

The recruiter called back within the specified timeframe with very general feedback from the interviewer. There was nothing specifically saying what went well or not well. The recruiter told me that, at the time, they would not be continuing with my application.

Given two intervals, return true or false for some condition.

Given a list of intervals and another interval, do something based on the previous condition from question 1.