Me postulé a través de un reclutador. Acudí a una entrevista en Ocrolus (Nueva Delhi) en ago 2022
Entrevista
The recruiter connected me through LinkedIn with the job opportunity. The interview process is so long that it takes around one and a half months. That they take 4 rounds of interviews. The first round is the coding round, the second round is system design, the third round is with the hiring manager and the fourth round is with VP. After each and every round needs to connect with HR for the Update interview in fact after scheduling an interview they don't call for whether you cleared the round or not they just scheduled the interview. So when I took all the rounds of interviews after one week HR called me and ask me about my NP, and salary, and HR said she will call me. And Next day I call HR and she said my profile is not selected and we can't take it forwards, so it was just wasting of time and disappointing to give an interview at ocrolus. Not Recommended.
Preguntas de entrevista [1]
Pregunta 1
Coding round: a familiar problem that you will iterate on and improve, just be comfortable with DSA fundamentals. Design round: plan out a pipeline for a simplified version of their product
Me postulé a través de una recomendación de un empleado. Acudí a una entrevista en Ocrolus en may 2026
Entrevista
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.
Preguntas de entrevista [1]
Pregunta 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.
Me postulé en línea. El proceso tomó 1 semana. Acudí a una entrevista en Ocrolus (Bengaluru) en abr 2026
Entrevista
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.
Me postulé a través de un reclutador. El proceso tomó 4 días. Acudí a una entrevista en Ocrolus (New York, NY) en sept 2022
Entrevista
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.
Preguntas de entrevista [1]
Pregunta 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.