Me postulé en línea. El proceso tomó 2 semanas. Acudí a una entrevista en Next Jump (Boston, MA) en oct 2013
Entrevista
They had come to my university's career fair and I submitted my resume then. However, I didn't hear back for a while. So, I applied online and got an email to come in for an interview 2 days later. The on-site had 2 interviews - one behavioral and second was technical with HTML/CSS/PHP/MySQL questions. They were all pretty basic.
I was then invited to their "Super Saturday" at NYC- they arrange your accommodation and travel expenses. BUT, I was handed a "train" ticket. Worse was yet to come. I checked in to my hotel room and was having shower, when someone was trying very hard to open the door. They make you share the room with a complete stranger and don't even tell you a word about it.
"Super" Saturday isn't so super as its very exhausting. They do arrange for your lunch and stuff. But, there are 50 other candidates and I soon realized that I didn't want to work for the company. Everyone of their employees kept talking about how "amazing their life is at NextJump and how work-life balance is super important to NextJump". The exaggeration was a bit too much and most of us had realized that they are lying. Some of the reviews from their ex-employees do talk about "long long" hours. In fact, the CEO did blurt it out during his speech that "if you're working for 60hours a week". There is just too much of "how awesome we are" and two tests of 30mins and 60mins each.
The technical questions included:
1. Creating a box containing two other boxes inside it (one on left and right, but 200px away from each other) and centering the outer box - pretty standard.
2. Finding the value of an element from an array, which occurs most number of times - there's an inbuilt php function to do this. Both, me and my interviewer, didn't know about this. I came back home and looked up php.net to learn it.
3. Create a counter in JS to continuously increment the value and display it in a text box.
4. Big-O questions - this is where I lose it for companies. I don't like studying for these sorts of things as a web developer.
5. Another 3 big php questions - they were solvable, but not in 40mins they give you. Then you have their employees saying "it could have been done in 20mins".
Me postulé a través de una facultad o universidad. El proceso tomó 2 semanas. Acudí a una entrevista en Next Jump (Rochester, NY) en mar 2015
Entrevista
On-campus recruitment, it was a 30 minute behavioral interview followed by a 30 minute technical interview with mixed questions about OOP, PHP, Algorithms, Database Design and HTML/CSS. Pretty basic questions if you know your way around web development in general. You really gotta find out about their culture to give good answers for the behavioral, because thats (according to themselves) the main thing that disqualifies a candidate (I aced the technical but it seems I didn't do well on the behavioral).
Preguntas de entrevista [2]
Pregunta 1
How can you align three divs to be besides one another (colums)
Me postulé a través de una facultad o universidad. El proceso tomó 2 semanas. Acudí a una entrevista en Next Jump (Cambridge, MA)
Entrevista
I applied through my college's career fair. The interview was pretty basic. It was divided into two parts, 30 minutes each. The first one was something like an informal talk about my background and things like that. The second one was a technical interview. The questions included:
a. Markup + CSS for two floated boxes separated by 200px empty space between them.
b. Find the the most repeated element in an array.
c. What is a class, object, inheritance?
d. What is a linked list? Where is it better than an unsorted array?
e. Some pretty basic Big Oh questions. I don't remember what exactly it was but was something along the lines of what's the insertion time for a linked-list.
f. Design DB tables for a gaming site.
g. Write a SQL query to get the most recent ratings of all the games sorted by their ratings (each game has multiple rows of ratings). Pretty standard case of using subqueries.
Preguntas de entrevista [1]
Pregunta 1
The questions were pretty easy- nothing was unexpected.
