When answering this question, avoid minimizing the importance of prioritizing defects. While all defects in code are a problem and need to be addressed, spending time on minor defects with low impacts is inefficient and may result in the project missing its deadline or exceeding its budget. Emphasize that you understand the importance of first identifying and prioritizing all defects and assigning your resources to the most impactful and highest priority defects.

"It is rare that my team and I initially develop a piece of software with zero defects. Since we normally employ the agile methodology, defects are identified after each day's work coding. Once I understand the defects, I then prioritize them and assign my team members and other resources to correct them. We address the highest priority defects quickly so that their impact is minimized. To lower priority defects which will not impact future work are then assigned to the appropriate person on the team to be corrected as the other team members continue to work developing new code."