I applied through other source and the process took 3 weeks - interviewed at Lab49 in February 2014.
Interview Details – The company found my profile in LinkedIn, the vacancy looked interesting so we decided to start the interviewing process. The process itself consist of several parts: at least two technical phone interviews, one Skype interview with a Senior Stuff Member.
Technical interviews were quite professional: the first one was about OOP, Java Basics(collections, structures), the second one was about Threads, non-blocking algorithms, Design Patterns and how to apply them, we also designed a hierarchy of objects for a given business domain.
Everything was really promising and enjoyable by me as a Java Developer because until the third interview I hadn't got any weird, odd and unsuitable questions as we do in many cases having interviews around.
So the third interview was with a Senior Stuff Member, who I didn't get the position of, but after that interview I received a very short answer that they are not going to proceed with my candidacy without any explanation why. All questions were about me become a Java Developer, have I ever heard about other Java-based languages and if I used them, about projects I participated in and which problem I faced there. So it was just a chat between two people.
I feel frustrating and don't really satisfied with the result because they didn't clarify the purpose of decline.
Interview Question – Non-blocking algorithms Answer Question
I applied online and the process took 2+ weeks - interviewed at Lab49 in December 2013.
Interview Details – Great HR team. They were probably the smoothest, quickest HR to deal with in my entire life. That part they have nailed down. Interview process included a couple of phone interviews, on-site interviews. Questions included were general .net framework questions, some threading questions, a little bit on data structures. On-site interview included some questions on WPF, they made take a computer test where I had to tweak a little bit of the code there, which I thought was awesome. Then some questions on WPF in general, which should be easily answerable for some one with a few years experience in that domain. Seemed good bunch of people. The office looked very sharp and slick with a great view.
I think overall if you want to stick to UI work, or web design, HTML 5 this seems a great place. They seem to have bunch of primarily web design folks in their office. But if you interested in more intense server side stuff, or more in computer science, this probably isn't the place for you.
Interview Question – Nothing really unexpected, standard questions. Answer Question
Reason for Declining – Found better offer elsewhere.
I applied through a recruiter and the process took 2 weeks - interviewed at Lab49.
Interview Details – Contacted via Linked in. Short phone interview, than 2.5 hour in person interview with 2 managers, then 40 minutes with a VP.
Interview Question – Detailed, in depth end-to-end software design questions. Designing the front/back end for a mobile application. Answer Question
Reason for Declining – Got a better offer elsewhere
I applied through a recruiter and the process took 2 months - interviewed at Lab49.
Interview Details – * Introductory call with recruiter.
* Technical phone interview with engineer.
* Live coding challenge, done over the phone with screen-sharing, using Node.js with an option of using CoffeeScript. Involved multiple separate challenges to complete, each of which came with a test suite for the interviewee to check his/her work.
Interview Question – Design the back-end architecture for a music-recognition service on the whiteboard. Answer Question
Very Difficult Interview
I applied through a recruiter and the process took 3 weeks - interviewed at Lab49 in July 2013.
Interview Details – Was initially contacted by an internal recruiter (not a head hunter) 10-15min screening to see if I was currently looking for a new job, if my background was generally a good fit, what my salary requirements were etc. This was followed by 2 phone interviews. The first one was fairly high level "tell me about some of the projects you're working on now" "how much experience do you have with Fixed income", etc. The 2nd phone interview was a bit more difficult. this was much more detailed in regard to what are the different charts or tools used to measure success\risk\budget on projects. After the 2 phone interviews they had me come in for a 4hr face to face interview. This interview was very interesting. They started out by telling me that they only hire 10% of the people who make it to this point. They also tell me that project managers rarely do very well with the exercise they were about to ask me to do. They gave me a list of different types of projects, and asked me to create a project, identify all the functional components, stakeholders, everything. Then detail how I would plan it, how I would deliver it, how I would mitigate risk, what my product backlog would look like, how I would manage expectations, etc etc. This was about a 2-3hr process. Though this was intense, it was really a GREAT way for them to see how I actually manage projects and for me to show my style, creativity, etc. After this process I spoke with the regional HR manager about the typical things like Comp, benefits, travel, etc. As a final measure, I was asked to come back in for a 4th round and meet with the COO and the head of North America Delivery as a 2 on 1 interview. This interview was clearly designed to apply stress and pressure to see how I would react when put in an uncomfortable position. Throughout the whole process it was constantly reiterated that Lab49's project managers would be facing off against very senior members of hedge funds and investment banks, and that being able to deal well with stress and pressure was key to this role.
I think it is important to note, that through this entire gauntlet of an interview process, everyone was very encouraging. It was clear that no one, at any time, was TRYING to trip me up. they WANTED me to do well, and they knew that their process was stressful. As soon as I realized this it helped tremendously. So if I didn't know the exact answer to a question, I would just walk them through how I might " measure risk" or " set the length of a sprint" even though there probably was a textbook correct\incorrect answer. They seemed happy with this approach.
Interview Question – "name the 3 types matrices used to manage risk in a project using information taken from PMBOK (Project Management Book of Knowledge)
"If you have 5 projects running concurrently, describe a single matrix that would easily show how each of those projects were doing" View Answer
Negotiation Details – they told me up front, didn't really matter too much what I was making or what I was looking to make, they measured my experience, my background, and how well I did with the interviews and my comp would be in line with what others in the role they offered. When given the offer, I did say I had another offer on the table for the exact same amount, and they upped my base by 5K without me even asking for it. Truthfully, that extra $5K didn't matter from a monetary prospective, but was a major plus for me from an integrity prospective. Made me feel like my offer wasn't just the product of a cold calculation dropped into an excel sheet. Which is how I have felt at other places before.
I applied through a recruiter and the process took 4 weeks - interviewed at Lab49 in March 2013.
Interview Details – Their internal recruiters handle outreach and initial screening, very to the point, nice and brief, say 10-15 minutes. Subsequently, a couple of phone screens of a technical / process nature to suss out your talents. In person interviews handled by internal recruitment co-ordinators, very professional, courteous and helpful. Before and after each round there's introductions and then contact details provided for followup.
Interview Question – If you were setting up your own consulting practice from the ground up, how would you get everyone aligned in practice and make sure they were doing a great job? View Answer
Very Difficult Interview
I applied through a staffing agency and the process took 2 weeks - interviewed at Lab49 in March 2013.
Interview Details – Three phone interviews, with the first being with HR and very basic, the second two being with different developers. Finally in-person interview with various employees. The process was relatively quick, and relaxed. The in-person interviews got very technical, and they are clearing looking for exceptional candidates.
I applied online and the process took 1 week - interviewed at Lab49 in February 2013.
Interview Details – The Hiring and interview process is well organized and seemed professional. The turn around time was quick. The Hiring person asked basic, six, core java/OOPs questions to validate our java knowledge. Followed by two levels of technical, phone interviews (scheduled on different days).
Both interviewers asked questions adaptively on what i have worked and what i spoke about. The interviewers were giving some hints for me to think on the areas where i was not strong, to check on my thinking process.
Interview Question – Not difficult questions if you are technically strong. Answer Question
I applied through a recruiter and the process took 2 weeks - interviewed at Lab49.
Interview Details – Contacted by an in-house recruiter through LinkedIn. Two phone interviews, both technical software engineering phone screen type interviews. If you are comfortable with Java and/or C# these should be easy.
The on-site consisted of four interviews. The first interview started with a coding exercise on a laptop. I thought this was a great idea, because it allowed me to code as I normally do. The second interview had an algorithms and architecture focus. The third interview was with a senior manager, but that too was technical.
Following that I spoke with HR.
Interview Question – I was asked some behavioral questions with respect to how I would handle clients and I was also asked my opinion of the financial services industry. Answer Question
I applied through a recruiter and the process took 2+ weeks - interviewed at Lab49 in November 2012.
Interview Details – Got contacted by recruiter. I was hesitant to interview at first since i'm pretty well placed at my current company. Later decided to interview with them since recruiter mentioned that they can match/exceed my current compensation.
There were 2 Phone Screens and 4 in person interviews.
Phone screens were very basic - One went over basic web concepts and other one was on web security and distributed systems.
Onsite interviews had some whiteboard programming and some basic questions. Overall the level was easy.
I did not find the employees smart or up to date with technologies. There were some instances where they were wrong. One positive thing is that they accepted it instead of arguing, which would have been a major turn off for me.
2) How do you implement last-mile messaging.
3) How to avoid CSRF
4) Problems with updating DOM with a fast moving data.
Interview Question – Are you married?
Why the hell do they even need this information Answer Question
Reason for Declining – Offer was pretty low compared to my current comp. It was a waste of my time going onsite by taking a day off. Recruiter told me that they will match/exceed my comp but i was let down.
Also, they are still on some legacy stuff (IMO) - Silverlight, .Net. I wanted to do more cutting edge.
Your feedback has been sent to the team and we'll look into it.
The difficulty rating is the average interview difficulty rating across all interview candidates.
The interview experience is the percentage of all interview candidates that said their interview experience was positive, neutral, or negative.
Your response will be removed from the review – this cannot be undone.
Simply post an anonymous review for a recent interview experience or current/former employer. Your post is anonymous – and if you're worried someone will be able to identify your review, you can even post without telling us your job title and location. Learn More.
No thanks –