On Wed, Nov 2, 2011 at 10:47 PM, Rajeev J Sebastian < rajeev.sebast...@gmail.com> wrote:
> As you suggested, the most important change we can make is to test > directly with code. > +1 to Sidu's suggestion about having candidates write code before they come in; have used that to much success. > Do you do your tests in Python, or whatever language the fresher knows? So > far, we have not received a single resume mentioning Python. Let the candidate submit code in a language/platform of their choosing. You want to give them the opportunity to put _their best foot_ forward. That said, you should also list out languages/platforms that you prefer; these would be the ones you've worked in and can evaluate the best in. They don't necessarily have to be the primary tool you use at work every day, just a common medium to trade insights into code. - d _______________________________________________ BangPypers mailing list BangPypers@python.org http://mail.python.org/mailman/listinfo/bangpypers
