I disagree with anyone who says that code tests are scam. I work at Thoughtworks and we follow extreme programming practices. The most basic of which includes p

I disagree with anyone who says that code tests are scam. I work at Thoughtworks and we follow extreme programming practices. The most basic of which includes pairing. Pairing is a super strenuous activity which brings in productivity as well. However it is not everyone. Doing a code pairing round validates a lot of softer aspects. I personally believe in show and don't tell. So if I am interviewing with someone or vice versa I would rather appreciate that I get to see some code that an individual has written or have someone assess me on that rather than how I well I can articulate myself or conjure up jargons and buzz words. I am comfortable taking on large problems as long as there is flexibility in time. I spend about 15 hours over three days solving a problem that intrigued me when I interviewed 5 years back. I learned a lot about company, programming and myself int those three days. Years later as I am trying to make that experience smoother for others, I have done a 5 series blog on what we look into coding solutions. Hopefully, that solidified them a little bit and doesn't make them look like "vague" and "just a whim and fancy" coding round. Find my detailed take on coding problems given out by Thoughtworks recruiting here. http://priyaaank.tumblr.com/post/95095165285/decoding-thoughtworks-coding-problems http://priyaaank.tumblr.com/post/95095165285/decoding-though...