The process took 2 weeks.
Recruiter screen Hiring manager call Tech screen Onsite consisting of: Two mission and values interviews System design The hiring manager asked some really rudimentary trivia type questions. I've done a lot of hiring manager screens and this was the first time I've been asked to describe "what happens when a browser fetches a web page". It left a pretty bad taste in my mouth but I decided to move to the next stage. I didn't make it past tech screen. The recruiter did very little candidate prep and I had no idea what kind of technical screen I was walking into. It turns out it was a frontend interview. It was a three step interview where each step was unveiled one at a time.
It was frankly a poorly structured interview question, since you don't have the full picture of what you're trying to build and instead build one piece at a time based on the prompt given. I've had interviews and excellent candidate experiences at companies that treat the interviews like a collaboration session. Interviews here felt like a test. Ultimately, this company's interviewing process has a ton of rough edges and I think it says a lot for the organization. I'm not too disappointed.
Step 1: Create a react application that displays three queues. Each queue is box with different colors.
Step 2: Add buttons that move one box to the next queue. Step 3: Each task has a timer. When it hits zero it moves itself to the next queue.
The following metrics were computed from 5 interview experiences for the Labelbox Senior Software Engineer role.
Labelbox's interview process for their Senior Software Engineer roles is very selective, failing most engineers who go through it.
Candidates reported having negative feelings for Labelbox's Senior Software Engineer interview process.