AutoX Interview Questions

The interview started directly with a LeetCode-style coding interview, skipping the usual recruiter call or phone screen. This first round focused on graph traversal algorithms like DFS and BFS, which are fundamental for a Controls Engineer position. While the problem wasn't overly complex, I wasn't able to solve it within the given time, and that was the end of my interview process.

So I had two rounds where we did basic CV and ML Python operations. The interviewers were nice and knew their stuff, making it pretty cool initially. After that, they said I'd move on, but then poof, radio silence for like 3 weeks even after I followed up. They finally sent a generic rejection saying something about 'a change in short-term goals.' Honestly, the ghosting and the lame excuse just showed they don't really care about candidates. It felt disorganized and like they just don't communicate well when their own stuff changes.

They just care about how you code and approach a coding problem. Literally no other interaction regarding yourself as a person, your experience, or your knowledge. It's a very biased way of evaluating a candidate.