Thoughtworks interview questions

Here is feedback that I really want to provide to the panel of interviewers. 1. String comparisons are not the best way to write conditions. Appreciate the use of integers/enums 2. OOP has the "is a" and "has a " concept that needs a deeper understanding 3. Interviewers need to be calibrated as to what they are looking out as signals and not just start taking interviews as first-time engineers 4. O(N) or O(N^2) or O(logN) .... is very important. Just ignoring them implies the lack of depth of the interviewers. 5. Obsession with Test-driven development is good, but not the "only" characteristic that you look in a software engineer. Problem-solving is more desired as you may be asked to move mountains for your clients. The entire hiring process was excellent from the recruitment and the leadership angle but failed miserably from the tech angle. This is something a services company should strive to refine going forward. There is no right or wrong here but the scope for improvement is vast.