Behavioural round in an interview.
“It is frustrating to code sometimes. You spend the whole day or two to solve a problem and then finally solve it knowing a small semicolon was missed. How do you handle such situations?”
This happened in an interview recently, where a project head from Optum took the behavioural round to evaluate my skills. While I answered most of the questions honestly, I also found myself repeating that I am an optimistic person who believes any bug can be fixed. Errors are not as bad as they seem to be, but only give us another opportunity to learn a new thing that day. I was expecting to have some technical questions and was least prepared for this kind of question. It was obvious that anyone would share positive experiences in such an interview, and my mind only kept on track to give honest answers from my experience.
In this post, I will share a few questions that came my way. For every question, I will share how I answered it and how it could be answered differently.
How does your day look like, starting from getting your story assigned? I answered that we discuss in the team who picks what and work accordingly. We then have a daily Scrum call for all projects of the POD and a separate call for the project team to discuss progress and blockers. He further asked if we had grooming sessions for the stories.
Any challenge that you faced and are proud of solving it?
Any examples of having a hard time with lead?
Any examples of bad code that you found from juniors?
Any examples of suggestions that you made implemented? I answered that we have strict guidelines in the current organization. Instead, I should have mentioned that the CI/CD implementation that I suggested in the previous organization was accepted and approved.