Arcesium | Principal Engg | Bangalore | Oct 2024 | Reject
Summary
My interview experience with Arcesium for a Principal Engineer role in Bangalore concluded with a rejection, which I received via a generic HR email after completing all technical rounds.
Full Experience
Overall, my experience with Arcesium was positive, but I was disappointed not to receive specific feedback regarding the rejection. It felt akin to a company withdrawing at the last moment without sharing a reason.
The process began with an Initial Phone Round with a Recruiter, where we discussed the job description and the overall interview process in detail.
Next was the Coding Round. I was tasked with implementing a blocking queue that included get(), put(), and multiput() methods. The key challenge was to correctly use locks and conditions to handle concurrency effectively.
Following that, I had a System Design Round where I needed to design a distributed job scheduler and executor, covering aspects of architecture, scalability, and reliability.
The final technical round was a Database Design Round. Here, I explored the use of both SQL and NoSQL databases before designing a comprehensive data model for an e-commerce platform, with a particular focus on the payment service's requirements and considerations.
After successfully completing all these technical rounds, I received a generic rejection email from HR. From my perspective, it seemed they might have been looking for specific domain knowledge that perhaps I didn't demonstrate sufficiently for the role.
Interview Questions (3)
Implement a blocking queue with get(), put(), and multiput() methods. The solution should leverage locks and conditions to ensure proper handling of concurrency and thread safety.
Design a distributed system that can effectively schedule and execute various jobs. The design should cover aspects such as job submission, task distribution across multiple nodes, fault tolerance mechanisms, and methods for monitoring job status and progress.
Explore the use cases and differences between SQL and NoSQL databases. Based on this understanding, design a detailed data model for an e-commerce platform, with a specific focus on the requirements and architecture of the payment service. Consider tables/collections, relationships, and data consistency for transactions.