Me postulé en línea. El proceso tomó 2 semanas. Acudí a una entrevista en Oceanwide (Montreal, QC) en mar 2013
Entrevista
Had 2 interviews, one with two technical people, another with HR and CTO (if I remember correctly). The technical questions were relevant to the position, but it seemed they didn't prepare for the interview process beforehand, felt like impromptu questions, which is not necessarily a bad thing, unless the questions are posed in a manner that makes it a bit confusing. I think if I were prepared more I would have done better, or conversely, if they had prepared to properly probe into my skills then they could have gathered more information about me. But they were nice and friendly.
Second interview with HR and CTO went relatively well. General experience related questions, what I was looking for, etc.
Didn't get the offer at the end, not sure why, maybe my technical interview wasn't as good, or maybe because what I said I expected (job-wise) in a new position wasn't exactly what the position was doing.
Preguntas de entrevista [5]
Pregunta 1
What's a Singleton? What's the difference between using a Singleton and a static class?
What's a CDN? Describe what happens when you type in a URL in your browser and press enter. (They are looking to see how much I know about the request-response cycle starting from the browser all the way to the server and back.)
Me postulé a través de una recomendación de un empleado. El proceso tomó 2 semanas. Acudí a una entrevista en Oceanwide (Montreal, QC)
Entrevista
First interview: HR1 + Architect.
Architect asks technical questions reading from paper with questions, no good. HR1 girl looks all the time into the window (enjoying really great view) being bored by the technical details of the conversation. Questions asked:
1) What are process, application domain, thread?
2) What's GC and what to do(design/program) to reduce its overhead?
3) How would you design that and that for a given business use case.
Other general questions.
Second interview: HR2 + CTO.
Less technical questions, more related to project lifecycle and PM, interpersonal communication. CTO is really great guy, very positive and smart.
Overall: very positive nice people, interesting to talk to (and I guess to work with).
Overall company impression: a (relatively) small company trying to save its budget in all possible ways (except technology used?). They have relatively low salaries and the benefits are almost non-existing comparing to blue-chip employers. They are still great for a work experience gain and low-fat-agile-working-development-environment using the latest MS technologies.
