My earliest round was a recruiter screen that went well, followed by a coding assessment that felt practical rather than like the usual LeetCode-style exercise. The question was timed, but the framing was closer to real-world work. The recruiters and interviewers also seemed knowledgeable and genuinely approachable.
As I moved further through the process, I ran into a different kind of hurdle: a CoderPad session where I had to build a small command-line tool in Python for field technicians. The scenario involved rebooting remote servers through an API. The 60-minute session was divided into parts, and I had to connect the logic to a local backend and a POST endpoint. The task focused on implementing the tool from the ground up.
The process varied a lot in what it tested. One step involved a general practical coding problem, while the next required building a structured CLI workflow around a specific API contract. I didn’t reach an offer in the end. Looking back, the role seemed to require comfort with realistic implementation, along with careful execution when the requirements were tightly specified.
Discussion
Loading comments…