It took almost a month after I applied for HR to reach out. I had almost thought I'd been rejected.
The OA was the vibe-coding OA that people have been talking about a lot on the forum lately. After doing it myself, I felt that ten minutes to communicate with the AI product manager was nowhere near enough, unless I used speech-to-text input.
Onsite 1: Calculate Equation Expression.
Onsite 2: A recent new problem.
The last part is worth paying attention to. Almost none of the earlier code could be reused, but once I understood the logic, it was straightforward. The idea was that the freezer sections would always be at the ends of the input data. There might be more than one freezer section. In the output, the freezer sections had to come last. I could compare the section numbers of the freezer areas and the regular areas to see whether the freezer areas were at the higher-numbered or lower-numbered end, and decide the sorting order accordingly.
Onsite 3 (behavioral): They dug deeply into past projects and asked whether I had received negative feedback before and how I had responded. Overall, it felt more like a conversation.
Onsite 4 (system design): Design a Dark Store Inventory System. They put more emphasis on consistency for this question. From my discussion with the interviewer, my conclusion was that they wanted me to design it directly around a relational database. Caching wasn't as high a priority here. The follow-up was how I would release the system once it was built. I described the whole process, from packaging through CI/CD and rollout, along with some standard Kubernetes knowledge.
These were all questions other people had mentioned, and overall they weren't very difficult.
I'm still in team matching. I'm hoping for a team with a good atmosphere, and good work-life balance would be even better!
Discussion
Loading comments…