I have completed the Online Assessment as of now and I am waiting for my results. The most important thing is to practice reading comprehension and extracting the necessary rules/constraints and using them properly within time constraints. Doable with enough practice.
- Question was about building an asynchronous event processing system. It was mainly about string parsing, dict manipulation, state management and applying logic with given rules. There were 4 parts, each part building on top of the previous one.
The recruiter reached out with an online assessment shortly after I applied.
I was given one week to complete it.
The assessment was a 3-tiered coding exercise on Hackerrank, where I had to design an error monitoring system. That required a complex imbricated queue + dict structure. You could run the test cases and then work on follow up questions.
It was a somewhat straightforward process - both questions I got I had already seen online. I would recommend going through Aced/Leetcode with tagged questions as other friends going through the process had this experience.
- Merchant fraud question where you have to implement charge, dispute, etc.
- Re-balance bank accounts such that every account has $100 dollars.
Overall, the interview process was well-structured and gave me a good opportunity to demonstrate my problem-solving and programming skills. The interviewers were friendly, professional, and encouraged me to think through problems rather than simply focus on getting the final answer.
What went well was the clarity of the problems and the collaborative nature of the discussions. I particularly appreciated being able to explain my approach, discuss trade-offs, and receive feedback or hints when appropriate. The process felt focused on understanding how I reasoned about problems rather than just evaluating whether I could produce a solution quickly.
One area that could be improved is providing slightly more clarity around expectations for each stage of the process, particularly regarding the scope and format of the technical interviews. Overall, though, I had a positive experience and appreciated the time and effort the interviewers put into making the process fair and engaging.
- Course Schedule
- the question was an implementation based question, given a merchant string and rules string we had to parse it by costumer id and merchant id and do some basic arithmetic operations
Till now the process has been relatively easy if you prep well. Make sure to practice when to use which data structures, explain why you are using them.
- technical question with multiple contraints
- multiple part question on array and string manipulation
Good. Communication needs to be good and technically sound you need to be.Overall, the interview process was well structured and gave me a good opportunity to understand both the role and the team. I particularly enjoyed the technical discussions, as they were practical and allowed me to explain my thought process rather than just arrive at a final answer. The interviewers were engaging, and the conversations gave me a clearer picture of the kind of problems the team works on.
What went well was the quality of the discussions and the opportunity to interact with people from different parts of the team. I also appreciated that the interviews covered both technical depth and broader problem-solving.
The main area that could have been better was the scheduling and communication around the different stages. At times, there was some uncertainty around timelines and next steps. More visibility into the overall process and expected timelines would have made the experience smoother.
Overall, though, I found the process positive and enjoyed meeting the team.
The coding problem was too long to be done within 1 hour. Should practice more and get fluent with basic language libraries and their APIs
- Experience, Professional history
- Loyalty and subscription tiers fee calculation problem
Can choose between HackerRank and a local IDE for execution. The question is given in several parts; each part's completion is a must to proceed to the next part. There were three parts in total, to be solved within 45 minutes.
Software Engineer
After one phone screening round there were 4 rounds. First was DS/Algo, second was a bug finding round, third was a high level design round, and fourth was a managerial round.
Software Engineer