Oblong Industries Software Engineer Interview Questions
& Process

I applied for a developer role, and a recruiter contacted me for an initial chat about my background and what I can do. After that, I went through two technical phone interviews where I was asked about my experience related to the job and also about how I'd approach certain coding problems to show my thinking. Then, I had an all-day on-site interview. This involved meeting different people from the team and management, plus doing a coding challenge on their platform. The meetings were pretty standard, with a mix of problem-solving questions. The coding challenge itself was focused on Oblong's g-speak system and required good C++ skills, using their API docs (which were actually pretty good), and asking questions to an Oblong employee. Finally, I talked about my work on the exercise with one of the Oblong folks.

I had two phone screens, which were pretty standard. They involved a simple coding exercise and some questions about my background. The people I spoke with were very friendly. The on-site visit was a great experience. The location was cool, and the people there were nice, doing good work quietly. I was given a computer to do some coding, which felt like a normal workday. There were three interviews with engineers where they asked typical questions about my background and algorithms. I appreciated being able to demonstrate my coding skills on a computer rather than just being evaluated on a whiteboard.

The interview was split into three stages, but I stopped after two tests because I couldn't get basic info about the company or what they do. First, there was a phone screen and an online test. Then, another phone screen and online test. The third stage was a four-hour test followed by a three-hour interview. I wanted to know more about the test and the job before committing to the four-hour test, but they wouldn't give me details and took me out of the running instead. I would definitely avoid this company.