I applied through a recruiter. The process took 4 weeks. I interviewed at X in Mar 2012
Interview
The interview consisted of two technical phone rounds. It wasn't a good experience from the start. I get it, they are Twitter and they pride themselves for being in a position they are right now. It doesn't mean they should disrespect an interviewee.
It took almost 6 weeks for the HR to schedule 2 rounds of phone interviews. Once in a while I had to check with the HR about the status of my application. It was frustrating.
Interview questions were fairly simple.
1. Reverse words in a given string.
2. Removing certain characters from an Array (don't remember the exact question)
First round was a good experience. He was respectful and asked standard interview questions. Second round was a disaster. Instead of evaluating my skill-set, he was focused on proving how good he is. Though the questions were simple, the attitude of the interviewer was really bad.
Overall a bad experience sparing that one phone round.
The process took 2 weeks. I interviewed at X (New York, NY) in Jan 2012
Interview
Submitted the resume through twitter careers website. HR got in touch to schedule a 45 minute interview. Was asked to write code on collabedit. The question was to find the subtree with maximum number of files given a filesystem tree. The interviewer clarified that directories need not be counted as a file. The interviewer also gave system call APIs (that he had made up) that should be used to access the filesystem. I provided him a recursive solution coded in C++.
Interview questions [1]
Question 1
What was the most challenging project you worked on recently ?
I applied through an employee referral. The process took 3 weeks. I interviewed at X (San Francisco, CA) in Apr 2012
Interview
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 confortable 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.