Ho presentato la mia candidatura tramite segnalazione di un dipendente. Ho sostenuto un colloquio presso Vymo nel mese di dic 2022
Colloquio
I was gone through 4 rounds of Interviews: 3 technical Round and 1 Managerial Round .
After clearing all rounds and getting a call for congratulations, they told me to send documents for the offer letter process and even gave me a joining date, but later on, they just withdraw by saying they have reshuffled employees and now have stopped hiring.
It was really unprofessional by HR Team and no proper reason was given to me.
Domande di colloquio [1]
Domanda 1
1st Round - DSA (Linked list, Stack, Queue)
2nd Round - DSA(Rainwater, Quadralet)
3rd Round - System Design, Leetcode Hard
4th Round - General Managerial Questions along with resume
Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 3 settimane. Ho sostenuto un colloquio presso Vymo (Bengaluru) nel mese di ago 2025
Colloquio
The interview process consisted of five rounds, including coding, DSA, system design, and managerial HR interviews. The questions were moderate to easy, and all interviewers were calm, positive, and supportive. The entire process took about three weeks. HR was very cooperative, informative, and helpful throughout. Overall, it was a smooth and professional experience.
I accepted an offer from Vymo.
Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Vymo (Bengaluru)
Colloquio
Initial Screening (30-45 mins) – A recruiter call to discuss my background, experience, and role expectations.
Technical Round 1 (1-1.5 hours) – Focused on coding, problem-solving, and test automation frameworks.
Technical Round 2 (1-1.5 hours) – Covered API testing, performance testing, and debugging real-world scenarios.
System Design Round (1-1.5 hours) – Discussion on designing a scalable test automation framework.
Behavioral Round (1 hour) – STAR-based questions on teamwork, leadership, and conflict resolution.
Domande di colloquio [1]
Domanda 1
The one thing they asked me was how I would handle a critical bug in production just before a major release
