Ocrolus interview questions

Overall Process: The process consisted of multiple rounds including a technical coding round followed by a system design discussion. Technical Round: The coding round covered: Implementing a basic mock of an Elasticsearch-like system (indexing + querying concepts) Classic problem: Product of array except self System Design Round: This round was not upto the mark with a typical system design evaluation. Instead of discussing system design concepts (like scalability, architecture, trade-offs, etc.), the interviewer focused primarily on language-specific questions in golang such as: what is the role of Go's built-in testing package? Explain how function calls work in Go What are the key differences between value types and reference types in Go? These questions are more suited for a language fundamentals round rather than system design. Feedback / Observation: The structure and intent of the system design round felt unclear.

I was a referral from mutual connections with the hiring manager. I have also worked for two of their largest customers for a total of 7 years. I was told they needed to hire quickly, and was moved very quickly through the process over Christmas and New Years. I got to the final round with the CEO and he asked me about my coachability and "partying". He asked about this from a previous role where I moved to Sydney to open an office there. He clearly did not speak to anyone who managed me, because what company would move me to a new continent to start their business? I was then ghosted for a month and told they had potential hires who were referrals for the job (I was one), and who had worked for their clients (I was one).