J'ai postulé via un recruteur. Le processus a pris 3 semaines. J'ai passé un entretien chez Block (Sunnyvale, CA) en janv. 2016
Entretien
Hiring was quick and responsive. I cold-emailed a local recruiter and immediately scheduled my interview. Since Square wants to see how you code in real-life, interviews are peer-to-peer, interactive, and very fun. This, of course, has its downsides. My first technical interviewer and I had great chemistry; but my second technical interviewer and I had a lukewarm connection at best, which is what got me rejected.
Questions d'entretien [1]
Question 1
Pretend you don't know the alphabet. Given a list of alphabetically ordered words, can you construct a new "alphabet" using the letters that you have and your knowledge about alphabetical orderings?
Hi,
Thank you for taking the time to tell us about your experience with Square. We are happy to hear that you had a good experience with the Software Engineer interview and that you saw the benefits of a peer-to-peer coding interview. The candidate experience is very important at Square and we value your positive feedback. Thanks for sharing.
Best,
The Square Talent Team
Expérience positive
Entretien moyen
Candidature
J'ai passé un entretien chez Block (Melbourne)
Entretien
Inital take home, followed by extension interview, followed by a coding challenge, followed by system design interview.
The whole process took 3 months!
The interviewers are usually really nice and want you to do your best.
The interviewer was nice, and he is friendly and willing to give hint, the question has 2 follow-ups, it was hard to complete in time. The question was not a typical LeetCode
J'ai passé un entretien chez Block (San Francisco, CA)
Entretien
Phone screen and then a full day of interviews. 3 pair programming challenges, a system design review and a prior experience interview. There was also an onsite lunch with a person from the company.
Questions d'entretien [1]
Question 1
To design a hotel booking system. Pick any part (backend, frontend, database, api etc) and deepdive into that, explaining the decisions along the way.
