Acudí a una entrevista en Bridgewater Associates en nov 2018
Experiencia positiva
Entrevista promedio
Solicitud
Me postulé a través de una facultad o universidad. El proceso tomó 2 días. Acudí a una entrevista en Bridgewater Associates
Entrevista
I applied after attending an on-campus information session. They have a strong culture of openness and honesty, and there you get somewhat of a cult vibe from the recruiters. They were all very friendly and down-to-earth, and were also surprisingly fratty, to the point of referring to each other by callsign-esque nicknames. The interview itself was with two employees at once, and featured an audio recorder so they could review my performance after the fact. We dove straight into the case, and I had the chance to ask them questions afterwards. I performed poorly on the case (it was not a good fit, and I had lost my voice and had to speak in a whisper, pretty awkward) and did not get a second round. I believe second rounds were held the very next day, and offers were given out within several days.
Preguntas de entrevista [1]
Pregunta 1
The case was an open-ended invitation to identify a problem with elevators and design a software-based solution. The interviewers were aggressive about asking why I chose the topic I did, what I wanted to do with it, etc. They wanted to make sure I could have strong opinions and back them up. I think the process was supposed to mimic a three-way brainstorming session, with me coming up with ideas and them trying to pick them apart. It all felt quite fair.
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?
