Solicité el puesto a través de un captador. El proceso duró 2 semanas. Acudí a una entrevista en Airtime (Palo Alto, CA) en oct 2016
Entrevista
The interview process was very informal and there was no formal coding test that I can recall. After a couple of phone interviews which were wide-ranging the general assumption was that coding questions were a waste of everyone's time.
There was a single all-day interview on-site where I had four meetings with four different groups of people / individuals including my prospective team-mates, my prospective "partner" within the company, and the top product and technical people.
Like most good interview processes, the conversations were very fluid and interesting. There were no "gotcha" questions or dumb programming tricks.
Preguntas de entrevista [1]
Pregunta 1
I was asked to discuss the pros and cons of different front-end frameworks for web and desktop (via Electron or similar) development.
Solicité el puesto a través de un captador. El proceso duró 2 semanas. Acudí a una entrevista en Airtime (New York, NY) en ago 2016
Entrevista
Exchanged some emails with a recruiter then talked with HR. After that they emailed me a coding challenge. Then another call with CTO. And after that on site interview for about 5 hours with 5 people.
Envié una solicitud electrónica. El proceso duró 2 semanas. Acudí a una entrevista en Airtime (New York, NY) en may 2016
Entrevista
Had a 15 mins call with an HR recruiter, the schedule call via Airtime. They emailed me a coding challenge. The programming challenge was easy and straight forward. I got an email from recruiter that they didn't like my solution. I was disappointed because there was no feedback. There is no point in investing your time when you don't get back anything in return.
Preguntas de entrevista [1]
Pregunta 1
I don't remember the question but it was a simple graph DFS traversal related question for a disconnected graph.
