Solicité el puesto a través de una agencia de empleo. El proceso duró 1 día. Acudí a una entrevista en Vymo (Bengaluru) en jul 2019
Entrevista
It was a overall good experience, recruiter was very courteous and helped through out in setting up the interview. Interview took 1 full day and they made the offer within a week.
Preguntas de entrevista [1]
Pregunta 1
Hackerrank 1 hour challenge: 2 questions: DP and recursion
2 coding rounds, datastructure covered was tree, graph, array etc.
1 high level system design round
1 low level design round
1 hiring manager round(tech + HR)
Solicité el puesto a través de una agencia de empleo. Acudí a una entrevista en Vymo
Entrevista
They have a small office of one floor. The environment was kind-of dark. There were no cubicles - people were sitting randomly in groups. Felt like lack of budget/infrastructure but on the other hand, it was positive that working there seemed informal.
All the interviewers were very polite to me. None of them seemed to show their superiority in any way - unlike at other companies. They somewhat treated me like a guest.
The first two interviewers were young and didn't seem much knowledgeable to me. One of them was asking algorithm questions to which even she didn't know the answers.
Preguntas de entrevista [3]
Pregunta 1
Interview - 1 & 2 (Algorithm)
- Super reduce a string (candy crush style)
- Zigzag traversal of a tree
- Data structure to do Insertion, Deletion and GetRandom in O(1) time (use hash map and array)
Design round 1:
I was asked to design their system. Vaguely explaining. Some agent data is coming through a stream. I have to process, store and then send the data to the respective clients (mentioned in the request). How will I handle the case when the client reception speed is much less than the speed at which you are receiving the data?
What about storage? For different clients, we are receiving different fields. Scalability, kafka NoSql etc.
API for the request to handle request for different clients. Low-level design.
- Design the following system. The user clicks on "Download" button and is redirected to another page. On that page, he is waiting for the file to be created. Once it is created, the user will receive a link to download that file. Consider multiple users. There can be a service that fetches from DB and creates an output file.
- Extension: Let's say the request can be of 3 types. One requests for DB; one processes it locally and one sends the request to third-party. Design this - message flow, write API (function declarations) etc.
- Another extension: Let's say each request is undergoing processing by many components (services). say s1 -> s2 -> (s3,s4) -> s5. s5 will process only when it has received from s3 and s4. How will the message flow? Can this flow be customized in a file? What if s5 has read from s4 but the corresponding request in s3 is not present? Can they be out of order?