J'ai postulé via un recruteur. Le processus a pris 1 jour. J'ai passé un entretien chez Wireless Generation, Inc. (Brooklyn, NY) en juil. 2011
Entretien
Interview consisted of a coding exercise and various questions on patterns. Finally I was asked how I would break down a spell check service into sub modules and direct the work of other developers.
I felt the feedback provided after the interview was substandard. I was told that I didn't have enough 'runtime' experience and that my definition of 'loose coupling' didn't match their definition.
Not sure what is meant by 'runtime' experience. My definition of 'loose coupling' was, I thought, quite brilliant.
After asking for code samples, and an hour on the phone, I would appreciate more substantial feedback. This seemed all rather vague based the time I spent with them. Would I work there?
J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien chez Wireless Generation, Inc. (Brooklyn, NY) en oct. 2012
Entretien
There was a pre-screen followed by an in-persion interview. The whole process actually worked as a recruitment tool since the people they had interviewing me were bright and it was obvious they took the process seriously. Work-life balance was something that was mentioned by each of the interviewers and it seemed obvious to me they weren't just giving lip service to the concept but that it was a shared value.
Questions d'entretien [1]
Question 1
For me the design question was the most challenging.
J'ai postulé via un recruteur. Le processus a pris 2 semaines. J'ai passé un entretien chez Wireless Generation, Inc. (Durham, NC) en févr. 2012
Entretien
-Phone interview where they asked some general tech questions, questions about projects I was working on, and did a Collabnet coding problem.
-1:1 was 3 hours in their office, 1 hour each with 1 guy. First was ok - asked to design/architect some kind of storage solution, which seemed odd as I was interview for a software position, not systems. Second was awful. Guy needed a bath (not good in a small room), and asked a bunch of college-level questions like making you implement data structures on the whiteboard, rather than how to apply them. Definitely brush up on how to implement things like Lists, Maps, etc. Third was a management-type.
The place is very young - only been around maybe 9-12 months and they like cutting-edge university mentality types. Applied, long term corporate software folks will not do very well.
Open environment, no cubes, just long tables and a loft atmosphere. Agile, pair-programming approach. Tobacco Road campus so traffic/parking could be an issue.
Questions d'entretien [1]
Question 1
Interview questions were very theoretical - how to implement linked lists, sets, hash maps, etc.
J'ai postulé via un recruteur. Le processus a pris 1 jour. J'ai passé un entretien chez Wireless Generation, Inc. (Brooklyn, NY) en janv. 2012
Entretien
Phone interview then which is most of the basic questions such as spellcheck, then an in person interview where you meet like 5 different members of the team. Each person asks a problem solving question. Maybe, they should just see some samples of some of the work that you have done instead of asking theoretical questions.