Getting an Interview
Getting an Interview
Interviews for Top Jobs at Two Sigma
- Software Engineer (46)
- Quantitative Analyst (6)
- Quantitative Research Analyst (6)
- Data Analyst (5)
- Financial Analyst (3)
- Quantitative Researcher (3)
- Data Analysis (2)
- Software Engineer Internship (2)
- Developer (2)
- Quantitative Research Associate (2)
- Quantitative Research (2)
- Software Developer (2)
- Software Developer Intern (1)
- Software Development Engineer (1)
- Software Engineering Intern (1)
- Quant (1)
- Leadership Role (1)
- Quantitative Developer (1)
- SQL Programmer (1)
- Analyst (1)
- Business Development (1)
- Senior Software Engineer (1)
- Systems Support Engineer (1)
- Asset Management (1)
- Systems Developer (1)
- Systems Engineer (1)
- Research Engineer (1)
- Human Resources (1)
- Human Resources Business Partner (1)
- Procurement Specialist (1)
Helpful (5)No OfferNegative ExperienceAverage Interview
I applied online. The process took 4+ weeks. I interviewed at Two Sigma.
Four hours of people asking questions more relevant to a psychological study than a job interview. Clearly, the eight individuals I was questioned by were trying to see if I was the correct "cultural fit". However, the divergence of questions showed that these eight individuals were not on the same page as to what their company's culture actually was as I found contradictions in their answers to my questions. Unfortunately, this interview process was a waste of half of a day as the organization clearly did not understand what they were looking for. In other words, this was a fishing expedition that only cost me my time. In fact, nearly eight months later, I saw that they were still "looking" to fill this role.
- What do you regret about your life? If you could do something over again, what would you do over? 1 Answer
Helpful (1)No OfferPositive ExperienceAverage Interview
The process took 4+ weeks. I interviewed at Two Sigma.
1st round hr interview 2nd online test 3rd phone interview major on os related high level questions 4th onsite interview For onsite are basically easy data structures and algorithm problem. One related to bug revise and another related to system design. Get to know bit manipulation and iterator would help a lot.
- Iterator bit manipulation Answer Question
- No OfferNeutral ExperienceEasy Interview
I applied online. The process took 2 weeks. I interviewed at Two Sigma (New York, NY) in May 2015.
im in the first round of interview process . 20 mins questions to see what you like and don't like. second round is 2hours coding questions, and the third one it behavior question. Then last one is on-site.
- bit manipulation Answer Question
- No OfferPositive ExperienceDifficult Interview
I applied online. I interviewed at Two Sigma.
There were two phone screens with Two Sigma. The first was a simply introduction with HR. The second phone screen was with a senior scientist at Two Sigma. It took about an hour and it was VERY DIFFICULT! She asked me to explain the projects in resume in very detailed implementation and then asked about 5~7 questions about data science. Each question needs a very detailed explanation with the reason using these approaches. I have to admit it was the hardest interview I have had and I did not do well.
- Given a new dataset, how do you find it provides useful information or not? Answer Question
Helpful (2)No OfferNegative ExperienceDifficult Interview
I applied through an employee referral. I interviewed at Two Sigma in April 2015.
First round, HR screen to see if you're a good fit. Then a phone interview with the manager of the systems department. The interviewer did not know how to conduct an interview and was just awkward. They told me I would hear back very shortly. I found out I did not get the position, because someone else from the company contacted me on Linkedin a month later to ask if I was interested in the same position. The interview was mostly centered around network topology. Either the interviewer thought he was hiring a network engineer, or I was confused about the position, and I believe it is the first one. A support person does not need to be a network engineer to perform the tasks outlined in the job description. It was a basic onsite support position. You should keep your candidates more informed and not leave them hanging. Re-evaluate your interviewing practices. Very unprofessional!
- Explain the OSI model in detail. 1 Answer
Helpful (1)No OfferPositive ExperienceEasy Interview
I applied through a staffing agency. The process took 6 weeks. I interviewed at Two Sigma (New York, NY) in April 2015.
Recruiter call, Hiring Manager Call, On-site full day of interviews. The whole process was very well coordinated, and very well communicated. I met onsite with relevant peers that I would be working with and discussed the state of the company, my past experiences, and some personality aspects. The people there are definitely smart, and some might describe them as "mature" in their way of thinking, but I'd call it "conservative" with regards to understanding the goods, bads, and things that can be changed, or the difference between relevant history and capabilities for the future. Although there is a yearning for a progressive attitude and mentality there, there is also a sense that there are less chances that will be taken, and bit by bit, it will drive them back towards the middle of the road, where opportunity to make non-linear advancements or jumps with experimentation will be stifled by the highlighting of mistakes that are expected to accompany. The company and people there will do fine, but I think over time they will become more institutionalized than trailblazers.
- Accepted OfferPositive ExperienceAverage Interview
I applied through college or university. The process took 1 day. I interviewed at Two Sigma in April 2015.
Very straightforward HR screen. Asked questions about projects and previous work experience, interest in the company. Company culture information. Company benefits were explained. Discussed different teams on the company and what kind of team members they were looking for.
- Single thread or multi thread solutions? Answer Question
- No OfferNeutral ExperienceAverage Interview
I applied through a staffing agency. The process took 1 day. I interviewed at Two Sigma (New York, NY) in April 2015.
code test was easy and I thought the phone interview was impeccable as well. The interviewer was very kind and respectful. Talked about his background and then asked about mine. Talked about my projects and the research details. Didn't proceed after that.
- basic back ground and technical checks. Very respectful and likable. 1 Answer
Helpful (7)No OfferNegative ExperienceDifficult Interview
I applied through a recruiter. The process took 2+ weeks. I interviewed at Two Sigma (New York, NY) in March 2015.
The 1st round is general phone interview, usually HR. The 2nd round is a programming test via Web based on HackerRank, which takes about 2 hours. . The 3 rd round is a technical interview
- Why did you do your research that way? Answer Question
Helpful (6)No OfferNeutral ExperienceAverage Interview
I applied through a staffing agency. The process took 4 weeks. I interviewed at Two Sigma (New York, NY) in March 2015.
Process took 4+ weeks. They are extremely slow in moving forward. 1. Phone Interview: Started with HR round for 20-30 mins to see if there is a fit. 2. Online Coding Test: Have to solve a couple of questions in 2 hrs. There is enough time to complete the 2 questions if you know what you are doing. 3. Phone Interview: Followed with a technical interview, easy as they are all about basic OS, data structures, sorting algos etc. Easy to get past this as well. 4. Onsite Technical Interview: 3 Rounds. The process ended with HR showing you out after lunch. I am not sure if this is a positive or negative experience as the interview process have high standards, didn't expect any less but also too stringent and short sighted. My first 2 tech rounds onsite went very well but went a little over time meaning I was left with ~40 mins for the last interview. Every interviewer has a mind set that you have to solve 2-3 questions correctly and this became a problem when I was left with only 10-12 mins for the second question in my third interview. He was literally counting down and I felt like I as put on a clock to solve the problem within the time frame or would be kicked out. That is exactly what happened as I could only give him the algorithm with few hints but not code it. I also felt sick when the third interviewer looked down on me saying "Oh I know, zeros and ones it's very complex!" with a smirk on his face - Arrogant. Expecting a candidate to give an algorithm and code it bug free in around 20 mins for each question is random as the difficulty of the questions vary(also if you are coding in C++). This might not get you good candidates even if they are unless the firm is against C++ as I know they only focus on JVM languages. This is evident by the fact that almost everyone I met is in a team which has more than 2 openings for over 6 months. I know they are a great firm doing very well and was disappointed to not get the offer but felt like I could not have done anything much better except for may be managing my time better and I felt it should not get down to that. For other potential candidates, All the best and do manage your time well!
- Regex Matching, Trees, Algorithms, etc... 1 Answer
Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review