For the onsite interview I had the questions outlined below. Nothing was particularly hard, but nothing was particularly defined either. My greatest qualm was the fact that
(1) several of the interviewers seemed to have not prepped their questions (in one case the interviewer said "i haven't asked this in a while" and then proceeded how to frame it -- that's stuff that has to be done before the interview when i'm not there -- in another case, the interviewer said, "i like to talk about what i'm currently working on" which triggered me to think -- "then how do you benchmark me against the people you saw 3 months ago"),
(2) one interviewer fielded a phonecall during an interview (epic?!), and
(3) during my lunch chat, the person left me for 10 minutes, alone, to eat lunch, at Twitter (ALONE).
Describe the lifecycle of a tweet?
Infer a working alphabet from a set of words?
Design and write a CSV parser.
Questions that were clearly made up on the spot / just related to current work life:
How would you handle a text to tweet system?
The following metrics were computed from 12 interview experiences for the X Senior Software Engineer role in San Francisco, California.
X's interview process for their Senior Software Engineer roles in San Francisco, California is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having mixed feelings for X's Senior Software Engineer interview process in San Francisco, California.