El proceso tomó 2 semanas. Acudí a una entrevista en X (San Francisco, CA) en dic 2018
Entrevista
I applied for a Full-Stack (Front-End focused) Software Engineer position after a Twitter recruiter reached out to me. Overall my experience was great.
The phone screen included implementing fizz-buzz, string manipulation and a basic tree/graph question.
The on-site was short and sweet: only three sessions. The first session was a pairing/realistic challenge to modify a super basic full-stack application, both front-end and back-end. Nothing tricky per se, but you have to be able to debug things a bit as you go and rely on your interviewer(s) for help, just like you would if you were pair programming. The second interview was a system design question where you get to describe how you would implement Twitter (!). The question is obviously very broad and you're dealing with the subject matter experts, so I'd recommend listening carefully to their suggestions and questions and going the way they point you to. Last but not least, I had a resume dig of sorts with the team's manager where we went through my resume and talked about every professional step I've taken, highlights and lowlights, and a fair bit of introspection about strengths and failures! Again, nothing tricky here, just be genuine.
Preguntas de entrevista [1]
Pregunta 1
Modify an existing full-stack JS project to add features or fix bugs
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
