The interviewing process is comprised of three steps (so far). Since I'm writing this prior to hearing back on the feedback/next step, thus I selected the "No offer" option.
1. 1 day after online application: I received an email to schedule an over-the-phone screening with the recruiter. I can't say with certainty, but I believe the screening's purpose was to weed out the resume liars and for you to elaborate on the projects/languages you have listed.
2. 17 days after finishing step #1: I received a follow-on email for scheduling a Google Hangout interview. To prepare for this, I recommend demoing codepad.io and acquaint yourself with the site by reading the quick guide and toggle dark mode. Speak, then code. I did not finish with polished products -- be sure to communicate your logic along the way.
3. < 3 hour after step #2: The recruiter was asking my availability for the on-site interview. This was in the office, and where you first get to meet your coworkers (read a "First Impressions are Everything" article). I was provided with lunch/beverages and was given the opportunity to eat by each member, but there was no scheduled lunch break. It was a personal choice to eat prior. This step involved an interview with 5 members (45 minutes each) both in person and over Google Hangout using the white board or coderpad.io. This was my favorite step, because they paint a picture and you have to devise a solution. Don't go in with the strict mindset of: I must make my first attempt the optimal solution as fast as possible or else I failed; just rubber duck it if you come across something and it will evolve naturally. Mind your corners and visualize the code before writing.
Overall, I had a pleasant experience talking to/working with the Rubicon Project team.
I am glad the company (Software Development Engineers at least) works via Mac and Linux.
