Lab49 logo

Lab49 Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 114 interview experiences · FREE TO READ

3.6 Rounds average
Average Typical difficulty
46.5% Positive experience

Which role are you interviewing for?

23 roles · 114 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Lab49.

Showing 4 of 114
Lab49 logo
Lab49

Senior Java Developer

Engineering · a year ago

Senior Average Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Background check Offer
Interview formats
Technical Behavioral

So I had this super disappointing experience. I went through four rounds of interviews and they verbally told me I got the job. I trusted them and even turned down another offer. Then, after 15 days of no contact, they suddenly told me my profile was 'on hold.' They gave no explanation, took no responsibility, and offered no apology for the delay or how it messed up my career plans. It really shows a lack of professionalism and empathy for candidates. It makes me wonder how they treat their employees if this is how they handle hiring. I'd tell future candidates to be careful and not rely on anything they say verbally.

Confirmed questions1 question
  • Would you be willing to work 7 days a week, like people used to do without holidays?
Lab49 logo
Lab49

Lead Software Engineer

Engineering · a year ago

Lead Average Negative experience No offer 2 rounds
Interview process
Technical screen Technical screen
Interview formats
Coding Technical

I did two tech interviews at Lab49. The first one was pretty standard and went fine, with some general questions about data structures and a coding challenge similar to LeetCode. The interviewer was engaged and responsive. The second round, however, was way different. I got a codebase that was only partly done and had to use multithreading to implement an interface. After I got the task, the interviewer just seemed to check out and started doing other things. I had to ask my clarifying questions over and over to get his attention, and even then, he took a while to get back into it before answering. At one point, he even gave me wrong info, which I only figured out later when I was coding. All in all, the lack of focus and professionalism in that second round felt really disrespectful and left a bad taste.

Confirmed questions2 questions
  • Solve a LeetCode-style coding problem.
  • Given a partially written codebase, implement an interface using multithreading.
Lab49 logo
Lab49

Test Automation Engineer

Engineering · more than a year ago

Entry Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Coding Technical

The interview kicked off with a recruiter chat that went smoothly. The recruiter was pleasant and to the point. Then, the technical round felt a bit off. It was just one interviewer, no one else, no recording, no oversight. It was mainly about pair-programming in Java. What really caught me by surprise was that the most crucial technology was only touched upon with a single question, which seemed pretty shallow. No other questions came up about this tech or other testing/automation areas. It was heavily focused on Java programming. The interviewer also didn't seem very interested in my past work, what I did, or the challenges I faced. No soft skill or problem-solving questions were asked either. This technical interview was basically just a long pair-programming session.

Confirmed questions1 question
  • Tell me about yourself, and then solve mostly algorithms in HackerRank.
Lab49 logo
Lab49

Front-End Web Developer

Engineering · more than a year ago

Mid Difficult Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Technical Coding Behavioral Other

I was first contacted by an in-house recruiter. The whole thing took about 5 days. I interviewed at Lab49 in Washington, DC back in December 2015. It started with an initial multiple-choice interview with the internal recruiter, which was more about weeding out unqualified candidates than actual hard questions. After that, I had an online/phone interview with a developer using CoderPad. They gave me a program outline and I had to fill in a missing part. I did make some mistakes while coding, but I ran the code, identified the issues, and fixed them while they kept me talking about my debugging process. Then, they added more requirements, and I updated the program accordingly. It felt like a good phone screen, and I even recommended CoderPad to my previous employer. I liked that they had a pre-built program with tests I could run anytime. It felt more like collaborating on development than an interview. The in-person part in DC lasted about four hours with five different people. The first two parts were technical, both using CoderPad again. The first involved implementing an algorithm in JavaScript with some sample code, which I didn't know initially but they explained. I had one problem during development but debugged it quickly. The interviewer found my solution unusual and asked how it worked without 'setTimeout', which I explained in detail, also asking about other methods. This also felt like pair-programming. The second technical interview was more of a Q&A, touched on my resume a bit, and involved another short CoderPad session with specific questions I can't recall now. The third interview was with my potential boss (more of a lead, actually), and it was a more typical management-style interview. Finally, I spoke with HR who mainly discussed company and office details and logistics. A bit of a surprise was how secretive the company is about their business, I couldn't get many details about their work or clients. However, I was satisfied that the people I met seemed great, and I felt I'd be happy working with them. I got an offer the very next day. HR sent an email with answers to some remaining questions, and I accepted the offer the same day.

Confirmed questions4 questions
  • Could you implement a specific algorithm using JavaScript?
  • Can you explain some JavaScript code concerning inheritance, object methods, detached functions, callbacks, and closures, particularly with edge cases?
  • Implement an algorithm in JavaScript.

Lab49 Interview Questions

Quoted word for word from Lab49 interview reports.

Given a string containing only parentheses, write a function to verify that all opening parentheses have a corresponding closing parenthesis.

Read reports

Implement a URL shortener service using Flask, with access to Flask and Python documentation.

Read reports

Can you write a function that takes a string and a set of characters, and returns the string with all specified characters removed? For example, removeAll("Hello There", "el") should result in "Ho Thr".

Read reports

Regarding this JavaScript code: [1,2,3].foreach((i, v) => { let temp = i; }); console.log(temp), what would be the output?

Read reports

Could you explain what "duration" means in the context of fixed income?

Read report

Regarding Java anonymous classes, can they exclusively extend a class, exclusively implement an interface, do both of these, or do neither?

Read report

How would you go about creating an immutable object in Java?

Read report

Can you explain the distinction between static and volatile keywords in Java?

Read report

How do you use the math library and throw exceptions with messages?

Read report

Formats, difficulty and experience

Across all 114 Lab49 interview reports.

Interview formats

Technical 34.4%
Coding 25.2%
Behavioral 24.1%
System Design 5.8%
Presentation 5.4%

Interview difficulty

Easy 11.4%
Average 58.8%
Difficult 29.8%

Candidate experience

Negative 36.8%
Neutral 16.7%
Positive 46.5%

Reports by job function

Engineering 85
Design 9
Consulting 6
Operations 6
Product 4
HR 3