Getting an Interview
Getting an Interview
Interviews for Top Jobs at Lab49
- Software Engineer (8)
- Senior Software Engineer (6)
- Java Developer (5)
- Senior Consultant (4)
- Senior Developer (3)
- Developer (3)
- User Experience Architect (2)
- Senior Software Developer (2)
- Front-End Web Developer (2)
- Software Developer (1)
- Human Resources Coordinator (1)
- .NET Developer (1)
- Senior Java Developer (1)
- Consultant (1)
- Java Software Engineer (1)
- Agile Project Manager (1)
- Computer Programmer (1)
- Associate (1)
- Automation Engineer (1)
- Technical Delivery Manager (1)
- Senior Associate (1)
- Lead QA (1)
- Various (1)
- Quality Assurance Engineer (1)
- QA Engineer (1)
- Delivery Manager (1)
- Product Owner (1)
- Front-End Engineer (1)
- User Experience Designer/Architect (1)
- Accepted OfferPositive ExperienceDifficult Interview
I applied through an employee referral. The process took 3 weeks. I interviewed at Lab49 (Washington, DC) in April 2015.
I applied via a referral. I received a phone call within a few days of the referral being done. The recruiter explained the position and expectations and asked me to describe myself and what position I was looking for. The first phone call itself had some Java questions, which is rare. This was followed by 2 Phone interviews and then an onsite interview once I cleared these. They did expedite the in-person because I had another offer in hand by that time.
- Describe an architecture I had mentioned in my resume Answer Question
Helpful (1)Accepted OfferPositive ExperienceAverage Interview
I applied through a recruiter. The process took 2 weeks. I interviewed at Lab49 (New York, NY) in March 2015.
Seemed fairly straightforward: About a 1 hour technical phone screen with a Principal Consultant and after that I went through a 4 hour interview with 3 developers and 1 person from HR. Each developer had a different amount of time working with the company: 6months, ~2years, 8 years. The first developer asked me to finish a couple of function declarations to fit the tests they had pre-built. The second developer asked me how I would design a user interface for both an administrator and user and how I would set up an api to handle the data. The third developer asked me about how I would solve larger problems in a team setting. The HR representative asked me about previous jobs and normal HR stuff. It was all pretty enjoyable and easy going actually. All of the interviewers were nice people, everyone seemed very knowledgable about coding and excited to build cool applications. I would say I had a very positive experience.
Helpful (2)No OfferNeutral ExperienceDifficult Interview
I applied online. The process took 4+ weeks. I interviewed at Lab49.
I first received a phone screen from the recruiting manager. Then I got another call with a senior designer, mostly talking about my background and questions about Lab49. Then I got called for in person interview, with hours of challenging design exercise and some HR talks.
- The design exercise was quite challenging, especially for the candidate who doesn't have any financial background Answer Question
Helpful (2)No OfferNegative ExperienceAverage Interview
I applied through a recruiter. The process took 3 days. I interviewed at Lab49 (New York, NY) in January 2015.
A simple phone interview. Then a rather basic (although I'm guessing they'd call it 'nuanced') question requiring you to implement a simple interface with some simple statements like "we're agile so we expect the code to look a certain way." Whatever that means. I assumed it meant make sure you provided test cases.
- What is the difference between List, Set, Map? What is the scope of a spring bean? How to implement an immutable object in Java? What is good about spring what is bad about spring? What is good about Java and what is bad about Java? Answer Question
- How to implement an asynchronous system? Answer Question
- Coding Test (No specifics as they sent an email saying it was their IP. LOL. ): The coding test was a very simple interface of a VERY simple algorithm. Although they did leave off some rather important details about how you would receive some critical required data and left that for you to conjure up. Fun, fun. They also had some special requests like "We utilize agile methodologies and adhere to coding standard best practices. " I've really been doing agile for the last 4-5 years. What the hell does that even mean. I assume they meant TDD so I made sure I had nice unit tests ready to go. Another good one... "The implementation should be thread-safe, and performant." Thread safe, that's easy. Done. Performant though? I kept everything at O(log n) which I thought should be performant enough. Answer Question
Helpful (2)No OfferNegative ExperienceDifficult Interview
I applied through a recruiter. The process took a week. I interviewed at Lab49 (Bethesda, MD) in November 2014.
- If you were given a string with any combination of matching parentheses, write an algorithm that ensures no set of parentheses are left unmatched. No other characters except for parentheses will be in the string. 1 Answer
- Talk a little bit about how you go about testing your applications. If you use automation which tools do you use? 1 Answer
- No OfferNegative ExperienceDifficult Interview
I applied online. The process took 2+ weeks. I interviewed at Lab49 (New York, NY) in April 2014.
Interview process was quite technical. It started out with the Lab49 recruiter herself asking a series of technical questions with 2 choices. Then came 2 phone interviews where the interviewers asked the usual multithreading concurrency framework, object oriented programming and spring questions. The 2nd phone interviewer asked me to design a class which would execute parallel tasks in a non-blocking fashion. The 3rd interview was on skype with a senior staff engineer from Lab49. This was more design oriented and the interviewer was not very patient with me and seemed to judge me from a pre-conceived bias. He barely asked me questions for 20 minutes and abruptly ended the interview although I did answer most of the questions correctly.
- Design a non-blocking executor framework which handles multiple tasks concurrently. 1 Answer
- No OfferPositive ExperienceDifficult Interview
I applied through a recruiter. The process took 2 weeks. I interviewed at Lab49 (New York, NY) in April 2014.
1.Recruiter asked me few multiple choice questions and later she scheduled a phone screen Got a call from UK and asked about my automation skills and framework details and it was went well.2nd level also phone screen interview.Somebody from NYC called me and it went well. Later scheduled me 3-4hrs of interview at onsite interview 1.They gave me some 30 min test on basic programming skills in Java,Automation skills,SQL and Linux 2.automation engineer had taken 30 min discussion and drilled down my automation skills and frameworks which I was working on 3.Another person (I guess he is a techno PM) gave me few scenarios in real time and asked me to prepare the plan of execution 4.Finally QA Global head took 20 min and asked me all my previous experience on Agile/Automation and process. I like the whole process of discussion .
- Linux and SQL Questions Answer Question
Helpful (2)No Offer
Terrible. Idiot apparently didnt realize that Java developer != Java Jepordy....oh...and the next time you try and trip someone on concurrency....you might want to actually know something about concurrency.
- Why are you asking questions about how exactly the jvm handles memory management? Why was this important? Was this a Java dev interview or an interview for a C/C++ developer? Answer Question
- No OfferNegative ExperienceAverage Interview
I applied online. The process took 2 weeks. I interviewed at Lab49 (New York, NY) in March 2014.
Initial Phone Screen by Recruiter followed by technical phone screen. Recruiters are good and nice to talk with. Then came the Tech interview. He called me 10 mins later and then started talking all nonsense - we don't have managers here, we work for only 50+ billion dollar companies, all are seniors here & what not. Finally 10 mins he asked some basic java questions which he also not sure when I responded with a question back he continued saying ok lets leave it... Finally it ended & I was relieved. Bad experience
- Nothing difficult question.. Interviewer was a difficult person :) Answer Question
- No OfferNegative ExperienceEasy Interview
I applied through a recruiter. The process took a week. I interviewed at Lab49 (New York, NY) in March 2014.
I was contacted via LinkedIn. The recruiter was fairly enthusiastic about the company and largely sold me on the idea of working for them. Then, came the ten or so multiple choice trivia questions that she asked. They seemed to be satisfied with my answers, so they scheduled me for a phone interview. However, approximately 5 minutes before the phone interview was scheduled to begin, I received an e-mail stating that they'd need to reschedule. Having conducted many technical interviews at my current job, I know that asking trivia questions, even as a gateway to a more advanced technical phone screen is not a good idea since you will get too many false positives and too many false negatives. Not only that, being asked to reschedule, 5 minutes prior to the interview is also very unprofessional and I've never been in the position where I've had to do such a thing to a candidate whenever I've been scheduled to conduct an interview.
- Multiple choice trivia questions. Answer Question
Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review