Senior Software Engineer applicants have rated the interview process at Lab49 with 2.8 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 32% positive. To compare, the company-average is 47.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Senior Software Engineer roles take an average of 21 days to get hired, when considering 19 user submitted interviews for this role. To compare, the hiring process at Lab49 overall takes an average of 23 days.
Common stages of the interview process at Lab49 as a Senior Software Engineer according to 19 Glassdoor interviews include:
Phone interview: 41%
One on one interview: 22%
Skills test: 17%
Group panel interview: 7%
Background check: 4%
Presentation: 4%
Other: 2%
Personality test: 2%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 3 days. I interviewed at Lab49 (New York, NY) in Jan 2015
Interview
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.
Interview questions [3]
Question 1
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?
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.
I applied through a recruiter. I interviewed at Lab49 (Budapest) in Nov 2025
Interview
First Round: regular HR round talking about the company, and relevant previous experiences
Second Round: 90 minutes live coding. Allowed to read docs or ask questions, but can't use AI or google the solution.
Difficulty is a bit hard to judge, because the problems were the type where knowledge of specific patterns is required, and that determines whether it's hard or trivial.
Style of coding and a compact and "elegant" solution were emphasized over relevant skills, or thought process.
There was no followup or any feedback after the second round.
Interview questions [1]
Question 1
Make concurrent calls to a paginated API and concat the results in order. Display the results, then write various algorithms working with the above data.
I applied online. I interviewed at Lab49 (Budapest)
Interview
They said the interview process will take 4 rounds. Two technical coding interviews and two talking interviews. The first interview was about clean coding. The task was finding a bug in the code. Then refactor it how I want it.
Interview questions [1]
Question 1
Fix the bug. Then refactor the code how you want it.
I had 2 HR screenings then a hackerrank technical interview in which after solving one exercise the interviewer wanted me to solve another one and even though the interview was supposed to last 90 minutes he cut it short at 60 and that was it. I was not able to finish the second exercise. So what do they want?