Weride.Ai Software Engineer interview experience

We talked through smart pointers—what they are and how I used them in practice—and then moved into interview-style reasoning that mixed coding knowledge with language mechanics.

The interview format kept bouncing between explanation and application. The coding part centered on an algorithmic problem tied to resource usage over time, with a clear expectation around rate-limiting thinking. The approach that fit the prompt was the token bucket model, and the discussion emphasized both the implementation shape and the underlying logic.

I didn’t get an offer, but I felt like the early C++