I was referred by a friend. The recruiter contacted me shortly, asked why Twitter, what I would like to work on and if I had any time constraints.
I was shortly scheduled 2 phone interviews consisting both on talking about my projects and interests and also CS problems, writing code online. Both interviews allowed time for any questions and short discussions afterwards.
Then I had 6 on-site interviews with back-end people (that's what I opted for). They mostly consisted of whiteboard coding and some let me write on the computer. Some were CS questions some architectural and backend.
I recommend preparing for it, read about algorithms and be comfortable writing code both online (though just a text editor - no feedback) and on a whiteboard. Depending on what you are applying for be prepared for architectural / design questions too.
Overall everybody was really nice and have a very positive perception. I got to ask about some of their challenges and discuss their solutions.
Implement a hash table (in C)
Given an array with all elements sorted on each individual row and column find the K-th smallest one
The following metrics were computed from 75 interview experiences for the X Software Engineer role in San Francisco, California.
X's interview process for their Software Engineer roles in San Francisco, California is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for X's Software Engineer interview process in San Francisco, California.