Me postulé a través de una recomendación de un empleado. El proceso tomó 3 meses. Acudí a una entrevista en X (San Francisco, CA) en jul 2013
Entrevista
My overall experience interviewing at Twitter is generally positive. Everyone I talked to seemed really excited about working at Twitter, and I got the sense that Twitter has many of the things I was looking for in a company; e.g. transparency (within the company), fast-moving environment, focus on employee learning, exciting place to work.
The actual interview process was somewhat prolonged. I was initially put in touch with a recruiter in April via a friend's referral; it took a few weeks until I started actually interviewing (beginning with an online coding question and then a couple of phone interviews, all of which were very doable). It took several days to a week to get feedback after each of the initial interviewing milestones. To the recruiter's credit, I was always asked whether I had any timing issues, and I get the feeling that things could have been sped up if I really needed them to be.
I eventually got to the on-site interview stage (in July), which had about 5-6 interviews. As one might expect, this was kind of exhausting, but I found myself actually liking this format, mainly because failing 1 interview out of 5 or 6 is much better than failing 1 interview out of 3 or 4. The majority of these interviews involved coding questions, although there was one that tested system design and one that tested *nix fundamentals. The coding questions were generally what you'd expect from any other premier tech company; there's not really much insight I can provide here.
I received an offer about a week or two after the interview.
Preguntas de entrevista [1]
Pregunta 1
I'll speak in generalities here.
1) There was a question with an optimal solution involving 3 data structures. I almost went down an optimal-ish path, but then I second-guessed myself and tried to solve the problem with different pairs of data structures, which wasn't optimal. Lesson learned: don't be afraid to explore paths that seem outlandish to you at first.
2) The system design question (there are many potential examples for such a question, e.g. "design a scalable online bookstore") thoroughly tested many of the concepts I learned in distributed systems. Granted, I was interviewing for such a position, but it really drove home how valuable my distributed systems class was.
3) I wasn't expecting *nix-related stuff at all. I'm really glad I took an operating systems class where we were required to implement a lot of fundamental tools.
Phone screen, followed by two coding rounds, one system design, and one HM/behavioral round. Prepare with LeetCode tagged questions related to data structures, algorithms, and system design topics. Prepare for Behavioural in STAR method.
Went through two screenings and virtual onsite. Technical team members were friendly and great to speak with. Recruiters were pretty awful - the one that set up the virtual onsite gave everybody different zoom links and trying to find the correct room to join really cut into my interview time and made me stressed out during the VO. Main recruiter scheduled a phone call to discuss results after the VO for when it was past midnight in my timezone but never called or responded to my followup.
To the recruiter: you don't need to try to keep me warm by scheduling a phone call and ghosting me when I only asked you whats the decision timeline. If its rejection just email to let me know instead of wasting more of my time especially when its late in my timezone.
In general this would've been a positive experience if the recruiters weren't so bad.
Me postulé a través de una recomendación de un empleado. El proceso tomó 2 semanas. Acudí a una entrevista en X (Londres, Inglaterra) en abr 2025
Entrevista
Ho effettuato un colloquio conoscitivo con HR dopodiché una sessione di live coding e domande tecniche con il responsabile dell'area. Domande vertevano su vari algoritmi e complessità in termini di tempo e spazio
Preguntas de entrevista [1]
Pregunta 1
Risoluzione di un problema algoritmico che richiedeva l'utilizzo della funzione xor