Skip to contentSkip to footer

Product Engineer Interview Questions

Salaries
Interviews

7,929 product engineer interview questions shared by candidates

Interviewer asked me to explain the code which I wrote in my assignment round. Then he asked me to show the test cases. In my assignment submission, I had not write all the test cases, I wrote only for the main modules - manager(business logic) and dao(database interaction) layer(It was not mentioned in the problem statement that you have to write test cases for all the methods). Then he asked me why did not you write the test cases for service layer. He asked me to complete the pending test cases. As per the given time I wrote one positive and one negative test case for all the pending methods. Then he asked me to explain the test cases. After this he extended the problem to multiple parking areas and asked me to change the code. First I explained the approach and then made the changes. After this he finished the interview and in next 5 minutes HR told me that the interview feedback is negative. I asked HR for a detailed feedback. She arranged a feedback session with the same interviewer. (She was very helpful throughout the interview). Interviewer's statement - "It's not like we are questioning your skills, it's just that your skills are not matching with the requirement. Here at Go-Jek we follow TDD but you had not submitted your assignment with all the test cases. Also, you did not write the test method names properly. And third point - when I asked to extend the code you changed business and dao layer both. You could have avoided the dao layer or writing different modules to minimize the changes at multiple layers." I was very disappointed with this feedback, first of all if they think that test coverage should be 100% then why didn't they mention it in the assignment and after that why I was shortlisted for the next rounds. Secondly, I did not write random names for the methods, I wrote what most of the people follow (test_method_name_success / test_method_name_failure) and that too because the given time was very less, so I decided to write success/failure test cases. If I had more time, I would have written more test cases and with detailed names Thirdly, they had specially mentioned in the assignment problem that your code should be "modular" and if you are adding new feature where we have to store in the database then how can someone make the changes without affecting the database layer. I explained all this to the interviewer and left the room. I should have taken other glassdoor reviews seriously. Someone mentioned in his review that - "It's a complete waste of time and energy, the interviewer I met in code pairing round looked very rigid about his thoughts and approach. Not at all open and doesn't seem to be understanding other's views." Interviewer had some solution in mind and all the other solutions looked wrong to him. I spent my complete weekend on the assignment and wrote ~1200 lines of code and spent 2 hours in bangalore traffic(each side) for the F2F interview to have this bad interview experience.
avatar

Product Engineer

Interviewed at Gojek

4.1★
Apr 14, 2019

Interviewer asked me to explain the code which I wrote in my assignment round. Then he asked me to show the test cases. In my assignment submission, I had not write all the test cases, I wrote only for the main modules - manager(business logic) and dao(database interaction) layer(It was not mentioned in the problem statement that you have to write test cases for all the methods). Then he asked me why did not you write the test cases for service layer. He asked me to complete the pending test cases. As per the given time I wrote one positive and one negative test case for all the pending methods. Then he asked me to explain the test cases. After this he extended the problem to multiple parking areas and asked me to change the code. First I explained the approach and then made the changes. After this he finished the interview and in next 5 minutes HR told me that the interview feedback is negative. I asked HR for a detailed feedback. She arranged a feedback session with the same interviewer. (She was very helpful throughout the interview). Interviewer's statement - "It's not like we are questioning your skills, it's just that your skills are not matching with the requirement. Here at Go-Jek we follow TDD but you had not submitted your assignment with all the test cases. Also, you did not write the test method names properly. And third point - when I asked to extend the code you changed business and dao layer both. You could have avoided the dao layer or writing different modules to minimize the changes at multiple layers." I was very disappointed with this feedback, first of all if they think that test coverage should be 100% then why didn't they mention it in the assignment and after that why I was shortlisted for the next rounds. Secondly, I did not write random names for the methods, I wrote what most of the people follow (test_method_name_success / test_method_name_failure) and that too because the given time was very less, so I decided to write success/failure test cases. If I had more time, I would have written more test cases and with detailed names Thirdly, they had specially mentioned in the assignment problem that your code should be "modular" and if you are adding new feature where we have to store in the database then how can someone make the changes without affecting the database layer. I explained all this to the interviewer and left the room. I should have taken other glassdoor reviews seriously. Someone mentioned in his review that - "It's a complete waste of time and energy, the interviewer I met in code pairing round looked very rigid about his thoughts and approach. Not at all open and doesn't seem to be understanding other's views." Interviewer had some solution in mind and all the other solutions looked wrong to him. I spent my complete weekend on the assignment and wrote ~1200 lines of code and spent 2 hours in bangalore traffic(each side) for the F2F interview to have this bad interview experience.

Viewing 1521 - 1530 interview questions

Glassdoor has 7,929 interview questions and reports from Product engineer interviews. Prepare for your interview. Get hired. Love your job.