Envié una solicitud electrónica. El proceso duró más de 1 semana. Acudí a una entrevista en Flywheel Networks (San Francisco, CA) en abr 2015
Entrevista
There's a phone screen with the lead engineer. He basically asked me about my experiences and what I was looking for in a role. He also explained Flywheel's business model and upcoming projects. Then an in house technical interview where they ask you problems to solve on the whiteboard.
Envié una solicitud electrónica. El proceso duró 3 semanas. Acudí a una entrevista en Flywheel Networks (San Francisco, CA) en may 2013
Entrevista
The interview process for the engineering team consisted of one short phone screen and one longer in-person interview with two current Flywheel engineers.
Phone screen: mostly focused on experience, projects, noteworthy items from my resume, etc. No technical questions. Lasted maybe 20 minutes.
In-person interview: The main interview covered multiple broad areas of programming but focused on algorithm design and complexity, database design/data modeling, and Ruby/Rails knowledge (Flywheel is primarily a Ruby/Rails shop). I was asked to design and implement a function to find the nth prime number, as well as come up with strategies to improve my solution's performance. The database portion focused on modeling a simple application and sketching a few SQL queries for different interviewer-provided scenarios. In addition to the technical interview, a few other non-engineering employees (including the CEO) interviewed me for personality/culture fit.
Preguntas de entrevista [1]
Pregunta 1
The Ruby/Rails questions covered a lot of ground and were by far the hardest to answer offhand, though I got the feeling they weren't expecting me to get every question right, but rather show them where and how large the gaps in my Rails knowledge are.
