Solicité el puesto a través de un captador. El proceso duró 2 semanas. Acudí a una entrevista en Airspace (Carlsbad, CA) en feb 2020
Entrevista
Phone screen with a pair programming problem that tested basic React skills. Invited to onsite to test node and react skills. All the exercises were pretty trivial; no leetcode. Panel and soft interview segments we're poorly organized, they even said folks didn't make it to them.
Recruiter was a good communicator. Found out no offer, found a better candidate. Don't really know what I could have done differently.
Solicité el puesto a través de una agencia de empleo. Acudí a una entrevista en Airspace (San Diego, CA) en ene 2021
Entrevista
A couple of conversations with an outside recruiter, hiring manager, and then a panel interview. The people seemed like they were fairly edified and competent, but at the same time were not all respectful.
Preguntas de entrevista [1]
Pregunta 1
No programming involved, just conversing with the hiring manager and others.
Started with a basic phone screen with the CTO.
Next part was a take home programming assignment creating a basic web page using a geo location ruby gem. There were predefined tests that needed to be written before doing any real coding. After you finished the assignment you had a remote interview with an engineer to go over your assignment.
Next step was the on-site interviews. This consisted of a couple of groups interviews. The biggest interview was the "pair programming" interview which involved a couple of engineers watching you debug a system while making confusing and unhelpful remarks. The bulk of this interview consisted of running a test suite and fixing test failures. Fixes ranged from simple typos to inheritance and attr_accessors. The most tricky problem dealt with inherited class level variables.
Preguntas de entrevista [1]
Pregunta 1
The most tricky problem dealt with inherited class level variables in Ruby.
