El proceso duró 2 meses. Acudí a una entrevista en Skillz en may 2023
Entrevista
Going to give a lot of thought to this one since it was one of the more interesting processes I've been through:
Multiple rounds:
1. Cold email from recruiter. You can expect weeks in between responses from them via email in the beginning phases.
2. Phone screen. Initial phone screen was very high level and going over background. Be sure to do stack research on the company as the recruiters will listen for buzzwords that will fit the specific stack.
3. HackerRank OA: the recruiter told me the question before I even begun, but the prompt was extremely simple to begin with. Easy pass here.
4. "Technical Round": 2 back to back 60 minute system design rounds. Again, recruiter tells you exactly what they will ask so not too bad.
5. If you pass this round, they fly your to Vegas and bring you into their office non-technical rounds. Nothing special here, you basically just repeat yourself 4 times in a row to non-technical stakeholders.
6. Offer: This is when you can expect to get called by the recruiter 5+ times a day. They send out a survey to your references (which is around 20 long response questions) and bring it to the hiring committee. The recruiter is also very candid with your ranking among other candidates (e.g. 'you're probably their second choice', 'there's probably a 70% chance of offer at this pint', etc).
Recruiters here are extremely pushy and a bit obnoxious. Very hard to get ahold of until they want to get ahold of you and then they blow up your phone an inappropriate amount when you are further along in the process.
There's a very strange policy worth mentioning where they favor gameplay over experience (for example, if you don't do well in one of the technical rounds, they will pass you along if they have record that you played a ton of Skillz games) which also was a very big red flag in my book. Strictly enforcing RTO for new hires while parts of the company are remote seems unfair as well.
Sketchy company to begin with if you do your research. All of the engineers I spoke with were fantastic though and probably do great work, but it's clear this company is a bureaucratic nightmare
The interview process was quite long but well-structured and straightforward. It included multiple stages such as an introduction, technical rounds, system design, behavioral discussions, and an in-person interview. All the interviewers were knowledgeable, professional, and clear in their expectations, making the overall experience positive and informative.
Preguntas de entrevista [1]
Pregunta 1
I was asked to provide a system design for a mobile application.
Solicité el puesto a través de un captador. El proceso duró 3 semanas. Acudí a una entrevista en Skillz (Las Vegas, NV) en dic 2024
Entrevista
I was reached out to on LinkedIn by one of the Senior Technical Recruiters. After an initial phone call, the recruiter said he liked my profile and I would be a great fit for the company. He asked me to apply to their job post, and I did. He said he would soon share the coding interview date.
But after that, the recruiter simply ghosted me. I messaged him multiple times but got no reply. After a few days, I received a generic email that they won't be moving forward with my application.
While I understand that a company has the right to decide who they choose and who they don't, but I'd expect the recruiter who reached out to me to convince me to apply to their job will at least let me know the update on my application or their decision, and not ignore my message. It shows poor ethics. And I'm honestly glad that I didn't move further in such a company where they don't value people's time and effort.
The interview process consisted of 4 to 5 rounds, each uniquely designed with no repetitive questions. The questions were practical, grounded in real-world scenarios, and closely aligned with my own work experience. The entire experience was smooth and enjoyable, with a relaxed pace that made it stress-free and comfortable.
Preguntas de entrevista [1]
Pregunta 1
One of the features I developed, including its design, implementation, and any challenges encountered along the way.
