Lumity Interview Questions
& Process

First, there's a phone call to set up a phone interview with either the Head of Engineering or a lead. If that goes well, you'll have a full day technical onsite interview, which includes lunch.

I applied online and heard back for a phone screen within a couple of weeks. It went well, and I got invited by the director of engineering for an onsite. That's when things got weird because they wanted me to fly from Florida to California without paying for it. After like 10 emails, they said I needed another phone screen. I did good on that one too, and they said the next step was an onsite. A couple days later, another email said another phone screen. The interviewer ghosted me initially, rescheduled for later that day, and then showed up the next day. After that third phone screen, I had to ask for an update and they told me I wasn't a fit.

The interview process included a first round phone screening. The second round involved a screen share, but the coding was done on a chalkboard, not a typical IDE, to test whiteboard coding ability. The interviewer asked about specific methods while I was solving the problem, suggesting they wanted detailed knowledge of every method, which is not practical for an engineer who should focus on the general approach rather than memorizing every function. IDEs exist to simplify automation. The interviewer also asked to discuss issues in a scenario where logic would suffice, implying that not all situations require a meeting and that micromanagement is ineffective.

A UI Engineer was looking for candidates through Vettery. The whole process took about two weeks. I had a phone call with the VP of Engineering, and then the next step was a phone screen. The interviewer looked at my resume right before the tech screen and realized I wasn't qualified for the role, so we didn't even get to the coding part. They were actually looking for someone to lead them through some difficult, unsolved challenges, not just a contributor.