QA Engineer at Vinove
- Difficulty
- Process took
- 1-2 Weeks
- Rounds
- 3
- Format
- Remote
- Applied via
- Company Website
How it went
- Look, I didn't get selected, but honestly, the whole experience was pretty good.
- I learned few things about areas I need to work on.
- Even if you don't get selected, it's good interview practice
What they would tell you
- Look, I didn't get selected, but honestly, the whole experience was pretty good.
- I learned few things about areas I need to work on.
- Even if you don't get selected, it's good interview practice
How to prepare
- Brush up on manual testing basics, they really focus on fundamentals
- Practice Selenium questions, especially framework design
- Don't ignore Java basics if you're into automation
- Be ready to explain your current work and projects in detail
- Have examples ready for behavioral questions
Their background
I'm a software test engineer with around 2.5 years of hands-on experience in both manual and automation testing.
Round by round
- 1
Offline Assessment60 min
So this was basically a written test, and honestly, it was tougher than I expected! Most questions were around manual testing, you know, the usual stuff like test case design, defect lifecycle, and testing methodologies. But they also threw in some Selenium questions which caught me off guard. I spent way too much time on a couple of tricky bug reporting scenarios. The test case writing part was okay, but some questions really made me think twice.
- 2
Technical Interview60 min
This round was actually pretty chill! The interviewer was nice and didn't make me feel nervous. We talked about my experience with testing, and he asked me to explain some automation frameworks I've worked with. There were a few coding questions in Java, nothing too complex, just basic stuff. He also gave me a scenario where I had to debug a failing test case, which was interesting. Overall, felt like a good conversation rather than a grilling session. Questions:
- Explained my current testing process and methodologies
- Selenium framework design, how I structure my automation projects
- Java basics, loops, conditions, and OOP concepts
- Debugging approach when tests fail in production
- How I handle flaky tests and test maintenance
- Test data management and environment setup
- 3
HR Round45 min
This was with the HR manager, and she was really sweet! We talked about everything, my career goals, how I handle stress, team conflicts, etc. She asked about my current company and why I'm looking to switch. The conversation felt natural, like talking to a friend. She explained the company culture and work environment, which sounded pretty good. No stress at all in this round, just a friendly chat about mutual expectations. Questions:
- Why are you looking for a job change?
- How do you handle tight deadlines and pressure?
- Tell me about a time you had a conflict with a teammate
- What are your career goals for the next 2-3 years?
- How do you stay updated with new testing tools and technologies?
- Questions about salary expectations and notice period
What came up
A candidate-reported account, lightly edited. Interview processes change by team and date.