Solicité el puesto a través de una agencia de empleo. El proceso duró 4 semanas. Acudí a una entrevista en Gryps
Entrevista
First round is a technical assessment sent via Coderbyte. Multiple choice questions around various AWS products (mostly serverless) followed by two Leetcode medium style coding questions.
Second round consists of a coding exercise. It's fairly straightforward; you're essentially just executing a left join on two Python dictionaries. There's an emphasis on memory utilization since the company is run on a serverless stack. There's then a separate system design interview. I honestly don't know how to describe this because it's about as hand-wavy of an interview I've been in as far as system design goes. Just know how various serverless AWS products work and you should be okay here.
Then after that are the CEO and CTO interviews, mostly around fit. The CEO was pretty fun to talk to and I really enjoyed the conversation. The CTO was...nice enough, but there were times where it felt like he was reading off a script or really just rattling off a bunch of buzzwords and seeing how familiar you were with them.
Preguntas de entrevista [1]
Pregunta 1
Coderbyte assessment to start, which was honestly the hardest part due to the Leetcode-style questions.
The technical screen question was much easier. The system design was honestly a bit of a joke given how hand-wavy it was (no need to think about scaling, fault tolerance, tradeoffs, etc.)
The founder interviews are what they are. CEO was fun to talk to. In hindsight, my conversation with the CTO had a bunch of flags that I should've addressed.
Envié una solicitud electrónica. El proceso duró 2 semanas. Acudí a una entrevista en Gryps (Seattle, WA) en jun 2023
Entrevista
Passed recruiter screen, had a call with CTO where I was asked about a series of buzzwords related to data pipelines. CTO immediately showed lack of both technical and leadership skills.
Preguntas de entrevista [1]
Pregunta 1
Here's 15 different disparate frameworks, have you used any?