My Second Round Interview Experience
Yesterday, I attended a face-to-face interview, and it was my second round. The experience taught me an important lesson about dynamic thinking in coding.
Interview Process
The interview started with a self-introduction. After that, HR gave me a written paper. Once I completed it, they asked me to solve coding questions.
Question 1:
Shift Timing Check
The first problem was based on two time shifts.
Example 1:
- Input:
10:00 – 12:00and1:00 – 3:00 - Output:
True
Example 2:
- Input:
10:00 – 12:00and12:00 – 2:00 - Output:
False
I wrote the code, but HR was not satisfied with my answer.
Question 2:
Character Count in String
Then, HR gave me another question.
Input:
aaabbcdddd
Expected Output:
a3b2cd4
I wrote the code for this as well, but again, HR was not satisfied.
Feedback from HR
I asked HR politely why they were not satisfied with my answers.
HR explained:
“You are writing code with static thinking. You are not thinking dynamically.”
That feedback made me understand my mistake. I focused on solving the problem only for the given example instead of writing general, reusable logic.
My Response
I accepted the feedback and replied:
“Okay sir, I understand. I will improve and practice writing code dynamically.
Thank you for the opportunity, sir.”
What I Learned
- Writing code is not enough
- Dynamic thinking and generic logic are very important
- Interviews are not about knowing everything, but about learning and improving
Conclusion
Even though I didn’t clear the round, this interview gave me valuable feedback. I am going to work on my problem-solving approach and improve my dynamic coding skills. Every interview is a step forward, and this experience motivated me to become better.
Top comments (0)