I applied through a recruiter. The process took 4 days. I interviewed at Ocrolus (New York, NY) in Sept 2022
Interview
Rounds: 1 Recruiter, 1 Hiring Manager, 1 coding, 1 system design, 1 VP Engineering. Total time about 4 hours. Standard interview process with LC type question and system design. Was able to get a good understanding of the product and vision by speaking with each interview at every round.
Interview questions [1]
Question 1
DS&A knowledge for the coding portion (LC-like question). System design somewhat related to product: Build a micro service that does X to achieve Y goals.
I applied through an employee referral. I interviewed at Ocrolus in May 2026
Interview
The interview process for a Senior Software Engineer position took place in May 2026 and consisted of five rounds: an initial HR screen, a technical round, a system design round, a leadership discussion, and a final executive conversation.
I received consistently positive feedback throughout the panel. However, communication completely stalled for two weeks following the final round, after which I received an automated, generic rejection stating the company decided to move forward with another candidate. It was disappointing to see a lack of transparency and communication at the final stage after dedicating so much time to their comprehensive loop.
Interview questions [1]
Question 1
The technical round lasted one hour. The first half was a conversation regarding technical background, and the second half focused on an object-oriented design and coding exercise where I was asked to implement a class to handle a specific business logic scenario.
I applied online. The process took 1 week. I interviewed at Ocrolus (Bengaluru) in Apr 2026
Interview
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.
Bowls
Get actionable career advice tailored to you by joining more bowls.
Want the inside scoop on your own company?
Check out your Company Bowl for anonymous work chats.