J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez Rubicon Project (Playa Vista, CA) en août 2016
Entretien
First round: Skype interview with hiring manager
Second round: Complete a 3-4 hr coding challenge
Third round: Onsite with 5 different people. One of the interviews was reviewing your coding challenge code with the interviewer. The rest were algorithm/language specific questions on the whiteboard. The recruiter then talks to you afterwards for are 15 minutes.
Do not be nervous, the interviewers are all very nice and help you through if you get stuck. They also provided snacks and gave a tour of the office during the interview. It was a very pleasant experience and my nervousness went away when the interview started.
J'ai postulé en ligne. Le processus a pris 6 semaines. J'ai passé un entretien chez Rubicon Project (Bozeman, MT) en juin 2019
Entretien
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.
Questions d'entretien [1]
Question 1
*paraphrased* I am skeptical about a library's function that I'm importing. How do you prove it behaves as expected?
J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez Rubicon Project (Playa Vista, CA) en oct. 2017
Entretien
Received an email from recruiter within hours of applying to the position, was called next day to schedule a video interview with Manager by that week. Received a positive response after the video interview within next 2 days and was scheduled for an on-site interview with 5 technology team members of different roles (including the Manager). Each one-to-one interview was around ~45 mins and comprised of technical discussion/white-boarding. Prior to interview, recruiting HR there had me he get me acquainted with the office space and general mood / office culture, it has agile/open seating (which actually suits me pretty well). In short pretty fast and efficient Interview process. Received a verbal confirmation of offer in 2 days and offer letter within a week.
Meilleures entreprises pour « Rémunération et avantages » près de chez vous