onX Software Engineer Interview Questions
& Process

The initial interview went really well, the recruiter was super nice. But the technical interview wasn't the best. The person interviewing me didn't even try to get to know me before hitting me with super specific questions that only someone working at a top company would know. They asked really specific map questions. You can tell how smart someone is by how much they focus on certain topics. A good engineer can learn new stuff quickly, so if the interviewer doesn't get that, they're probably not a good engineer and shouldn't be in charge.

This company put me through 6 rounds of interviews for a senior role and then ghosted me. After trying to follow up with four different people (two recruiters, a recruiting coordinator, and an engineering director), this company finally rejected me. The recruiter told me they picked someone else but that I had positive feedback and they wanted to consider me for a lower position, Software Development Engineer. I interviewed again with a different manager and got rejected again. The recruiter called to say they chose another candidate, but that I had positive feedback and should reapply. I did, and this time got rejected via email, which was surprising. I actually got rejected!! Wow, at least they emailed me. This isn't about being angry about rejection; I've faced hundreds. This is to highlight mishandled recruiting that disrespects candidates like me who are serious about job hunting, preparing, and interviewing for hours daily. Job searching isn't a game, but sometimes recruiting feels like it.

I applied at a career fair and heard back about a month later about scheduling an interview. The interview itself was with the hiring manager and recruiter and lasted about 45 mins to an hour. They asked a Leetcode Easy question and an architecture question, and also asked about my background. It was just one round of interviews and I got the offer about a month later.