After speaking with a Twitter recruiter and an introductory call, I did two screening calls and an onsite, with about a week between each phase.
The first call was high-level experience based, but also spent some time describing the team structure.
The second call was more technical, and included a screen-shared coding problem.
The onsite was broken into four one hour parts with a break for lunch.
Each part was conducted by two engineers.
Three parts focused on white-boarded coding problems with an algorithms/data structures focus, while one was more soft-skills and experience focused (name a contribution you made to a team you were proud of, name a mistake you made at a previous job and steps you took to fix it, et cetera).
All parts had a ten minute section for questions from the candidate.
More or less what you'd expect. Interview Cake was good prep. A few questions were more architecture focused and experience-based.
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.