Me postulé en línea. El proceso tomó 2 semanas. Acudí a una entrevista en Bridgewater Associates en nov 2018
Entrevista promedio
Solicitud
Me postulé a través de una facultad o universidad. El proceso tomó 3 días. Acudí a una entrevista en Bridgewater Associates
Entrevista
Before the interview, there was a 3 hour coding test and 3 hour personality test. The coding test was pretty easy. The personality test was just time-consuming.
The night before the interview, there was supposed to be a dinner, but the location where it was held did not exist. The dinner ended up being in a nearby location, but it took me fifteen minutes to find it, and I arrived five minutes earlier than all the other candidates. The dinner's organizer flatly refused to admit that he sent us the wrong location.
For some reason, the dinner ended up being held in the waiting area of the restaurant the whole time and was attended by the next day's interviewers themselves. One of the interviewers obsessed over personality assessments.
The actual interview was fairly simple. One design question and a bunch of questions about why my current lab works the way it does and why it has a particular name.
Preguntas de entrevista [1]
Pregunta 1
Why do you think [current workplace] is named the way it is named?
I submitted my application for the Technology Associate position through Bridgewater's website and after about a week I received a coding challenge. The coding challenge was about a directed weighted graph and how it applies to Bridgewater. The problem was easy and I received a notice that they wanted to move forward about 2 days after I submitted my solution. Next came 2 phone interviews. The first was focused on seeing who I am and why I applied to Bridgewater. The second was technical and focused on the solution I sent. The technical call was a disappointment because the engineer I talked to obviously did not read my code before the call. We spent 45 minutes talking about how this problem was important to Bridgewater, nothing technical. After this call I received an email that they wanted to move to on-site.
I setup dates and figured out when would be best to visit. Then randomly about 4 days later I received an email that they did not want to continue the interview process because all of their TA position were filled for the year. After spending hours taking coding challenges, phone calls, personality tests, and multiple interviews, I was rejected because HR couldn't figure out they had enough candidates already.
Nice people, but really annoyed.
Me postulé en línea. Acudí a una entrevista en Bridgewater Associates (Berkeley, CA) en sept 2017
Entrevista
The technical interview was a generic technical interview in which the interviewer started off by talking about the projects that I have done. Then we talked about the coding challenge that was sent to me a week earlier. Finally, I was questioned on data structures and algorithms fundamentals.
Me postulé a través de un reclutador. Acudí a una entrevista en Bridgewater Associates en nov 2016
Entrevista
The campus recruiters hosted a dinner for interested students referred from past interns. From there, there were several online questionnaires and personality questions, alongside a technical and personality interview through the phone. Then, there was an onsite interview.
Preguntas de entrevista [1]
Pregunta 1
You and an opponent both have a copy of a set of N unique cards, each with a certain set of attributes. The attributes of a card uniquely distinguishes it from the other (N-1) cards. Your opponent chooses a particular card. You're allowed to ask your opponent yes-no questions about the type of attributes the chosen card has. What's the best strategy to minimize the number of questions you need to ask to determine the card?
