I had a first call with a recruiter that was more like a conversation. She asked about my previous projects and my interest in the position and the company.

This was followed by two technical phone interviews using Collabedit to code a couple of problems. Both interviewers were very nice. However, the first interviewer was really quiet, which was not very helpful in a coding interview. The second interviewer was the total opposite, creating a quite nice collaborative interview environment.

Overall, it was a nice experience. I am not particularly a fan of coding interviews, but the problems were not that hard, and it was not a bad experience.

A couple of days after the second interview, the recruiter contacted me with nice feedback, but said that I was not a match. I got the impression from both the feedback and the recruiting process that the position was for a graduate and not for an experienced engineer. So, I guess I agreed that there was no match, and it was nice that the recruiter contacted me soon without making me wait.

There were two problems to solve:

A) Write a job scheduler. Input: a list of jobs with dependencies. Output: a list of jobs to be executed according to dependencies.

B) Count calendar days. Input: a list of ranges [start, end]. A range represents days, e.g., [1, 4] means days from 1 to day 4. Output: the total days included in the list of ranges.

The answer involved:

1. Sorting the list.
2. Merging overlapping ranges.
3. Counting/summing the days of the resulting non-overlapping ranges.