Me postulé a través de una recomendación de un empleado. El proceso tomó 3 semanas. Acudí a una entrevista en Handshake (Hershey, PA) en ago 2019
Entrevista
I first got in touch with Handshake earlier in the year, but the timing wasn't quite right. Circumstances changed and I reached out to a friend at the company. I got back in touch with a member of their people team, who listened intently to my goals and offered some good reasons why Handshake was a good fit.
The next step was an hour-long technical interview with the hiring manager. We had a great conversation while I completed two technical tasks in a very conversational, low-stress format. I should mention I was interviewing for a remote position, so the whole process was done via video chat (we used Zoom).
The final round was a ~5-hour long string of interviews with some breaks built in. The interviews were all with folks who I'd be working with on the team. The plurality of the time was spent on a technical challenge, which was also collaborative and more about process and problem-solving than the end product. There was also a software architecture portion of the interview and an interview with a product manager. The structure of this final round interview was sent in detail in advance of the interview along with some resources so I had the opportunity to prepare and put my best foot forward.
I ended up getting an offer and taking the job. Even if it didn't work out, though, I was impressed at the maturity and transparency of the process and thankful to have spent time with a group of truly nice people.
Preguntas de entrevista [1]
Pregunta 1
On which part of the product - development pipeline do you prefer to focus?
The process began with a standard recruiter screen followed by a four-level coding challenge. Unfortunately, the technical assessment was poorly structured. The requirements for each level were overly abstract, forcing candidates to make broad assumptions to pass the test cases rather than following clear documentation.
Furthermore, the coding environment lacked basic IDE features like IntelliSense. Requiring verbose code for complex, ambiguous problems without standard editor support felt unnecessarily tedious. I managed Level 1, but by Level 2, the lack of clarity made it difficult to stay engaged.
Preguntas de entrevista [1]
Pregunta 1
Something around timestamp based key value storage and retrieval. Then level 2 involved assigning priorities to each key and then retrieving the sorted list of keys and so on.
Me postulé en línea. El proceso tomó 2 semanas. Acudí a una entrevista en Handshake en nov 2024
Entrevista
Standard tech interview with a take-home assignment. Not a leetcode brain-teaser but more basic code design.
Phone Screen
Technical Phone Screen
Virtual On-site
- Take home assignment, basic CRUD app
- System Design
- Behavioral
Preguntas de entrevista [1]
Pregunta 1
Technical Phone Screen - Create methods to mock a vending machine. Vending machine should calculate change. User needs to call 2 methods, one to input change, one to select item, and 2 actions should be idempotent done in any order prior to vending items.
Virtual On-site
- Take home assignment, basic CRUD app
- Design a job board
Me postulé a través de un reclutador. El proceso tomó 2 días. Acudí a una entrevista en Handshake (San Francisco, CA) en sep 2023
Entrevista
I hesitate to call my experience an interview, because, laughingly, I didn't even get to speak to the internal recruiter who originally reached out to me via LinkedIn. We initially had a date & time set, and the recruiter switched the calendar invite to a different day & time 10minutes before we were due to meet, without even the courtesy of informing me. As it turns out, that day & time were not good for me, so I suggested a different day & time, and sent the recruiter a note. The recruiter had accepted the 2nd invite, and I thought we were all set to meet via Zoom. I joined the call, but the recruiter never showed - totally ghosted. I haven't heard from the recruiter since