
onX Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 51 interview experiences · FREE TO READ
Which role are you interviewing for?
18 roles · 51 reportsCandidate interview experiences
First-hand accounts from people who interviewed at onX.
Software Engineer
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.
- What is your approach to testing?
Full Stack Engineer
Got referred by old coworkers. It was like a 6-week thing with about 6 rounds. Started with a recruiter chat, then the hiring manager, then a lead engineer. Had to do a take-home coding test, and then a panel of 3 people reviewed it. After that, another hiring manager chat, and finally a product manager interview. The interviews weren't too tough and felt pretty positive. The technical part wasn't hard either, and it seemed like the panel just looked at the code for the first time during the review. Didn't get an offer in the end, and no one really told me why. Communication was a bit rough, and it seemed like some interviewers thought I was going for a different team.
- Can you describe how you would handle migrating from an older system?
Lifecycle Marketing Manager
Went through three rounds of interviews and really enjoyed them all; the conversations were smart, the questions engaging, and the people were open and generous. The only thing I didn't love was the time it took to hear back between rounds, which in one instance was almost two weeks, making the whole thing a bit more stressful than it needed to be.
- Can you share an instance where you addressed a strategic challenge? Describe your approach and the reasoning behind it.
Product Manager
I had an HR screen, then talked to the Hiring Manager, followed by 4 meet-the-team interviews. The people seemed really cool and it felt like a great place to work. The questions were pretty much the same every time, often asking vague things about past successes. They didn't ask any technical questions or case studies, so I couldn't really show off my skills – it felt more like they were checking for culture fit. Honestly, after 6 interviews, they couldn't even be bothered to give me any feedback.
- What makes you want to work in product?
- What is your motivation for interviewing with OnX?
- Tell me about a time you had a win.
onX Interview Questions
Quoted word for word from onX interview reports.
“Write a function to return the length and width of a rectangle given its bounding box (left lower and upper right points) on a Cartesian plane.”
Read reports →“How would you find two numbers in an array of size n that add up to a given integer x?”
Read reports →“For a hunting app, would you be comfortable viewing footage of deceased animals?”
Read reports →“Can you download the Android app from the repository they shared and make sure it runs correctly?”
Read reports →“Could you write a function to check if a point falls within a given bounding box?”
Read report →“How would you determine if two distinct rectangles overlap?”
Read report →“How would you implement Mapbox into an Android application?”
Read report →“Solve a simple algorithm problem and write tests for it, such as the palindrome problem.”
Read report →“Can you explain what an AB split is and its purpose?”
Read report →Formats, difficulty and experience
Across all 51 onX interview reports.