Glassdoor users rated their interview experience at X as 75% positive with a difficulty rating score of 3.5 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for Internship and Software Engineer rated their interviews as the hardest, whereas interviews for Estagiário and Outbound Sales Representative roles were rated as the easiest.
The hiring process at X takes an average of 77 days when considering 8 user submitted interviews across all job titles. Candidates applying for Internship had the quickest hiring process (on average 21 days), whereas Publicitário roles had the slowest hiring process (on average 150 days).
Common stages of the interview process at X according to 8 Glassdoor interviews include:
One on one interview: 45%
Presentation: 18%
Group panel interview: 18%
Background check: 9%
IQ intelligence test: 9%
Here are the most commonly searched roles for interview reports -
Asked about my background, and a technical question. The process was pretty standard, but I wasn't prepared enough for it. It was a phone interview, and the problem was in javascript. I had to code online in a shared document.
I applied online. The process took 1+ week. I interviewed at X
Interview
The initial call was from the HR explaining what the teams are and the different roles. Went on for about an hour. He was actually extremely informative and adept at answering my questions.
This was followed by 2 phone screens. Both were bad in my case. Firstly, my interviewers called 10-15 minutes late. The interview was riddled with technical faults, network problems, call dropping. All in all, it was just a really bad experience.
Interview questions [1]
Question 1
If there are N lanes and K cars in each lane and Cars[i][j] = (position of car, length of car), and if a frog has to cross the road in one straight jump (vertically down), not encountering any car, write a function to determine if he will be able to do it. You are given a frozen state of the road.
I applied through an employee referral. The process took 2 weeks. I interviewed at X (San Francisco, CA) in Feb 2013
Interview
Twitter reached out to me several times over the years. Most recently it was for an SRE position. I spoke with the team lead and had a nice positive conversation, then was set up for a screen with another SRE. Though I was told I would need to do live scripting with the other SRE, he decided not to do that with me, which was good, since I had told everyone along the way that my strength was not in scripting, and if the job required heavy scripting or coding or code analysis that I was not the right person for the job. Nonetheless, when it came to an in-person interview, it was all about scripting. I found that a bit frustrating and a waste of my time. In general, I felt that the right hand had no idea what the left hand was doing.
Interview questions [1]
Question 1
Live scripting question with no preamble on a white board in front of a 23-year-old engineer.