Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Timed coding tests... are the that valuable?

xkrebstarx (1703372) writes | about 2 years ago


xkrebstarx (1703372) writes "A buddy of mine recently applied to a "tech-giant". Before setting up a phone interview with him, the unnamed company issued a timed coding test to gauge his coding prowess. He was allotted 45 minutes to complete an undergraduate level coding assignment. I would like to ask the Slashdotters of the world if they find value in these speed-programming tests. Does coding quickly really indicate a better programmer? A better employee?

Coding should be calm, deliberate, and cautious. Writing code under pressure leads to bugs, short-sited designs, and a maintenance nightmare. Of course our employers want us to produce "more code", but is coding quickly sustainable?"

Sorry! There are no comments related to the filter you selected.

You either got it, or you don't. (1)

attemptedgoalie (634133) | about 2 years ago | (#42540787)

Do you format when you code?
Do you use stupid variable names?
Do you error check at all?
Do you comment your code?

That's what you find out in 45 minutes.

2nd round interview is collaborating on code, troubleshooting, etc. Take this existing structure, make it do this differently. Go.

Check for New Comments
Slashdot Login

Need an Account?

Forgot your password?