Nitin Reddy nitinreddy3

What Hiring Should Look Like

This is definitely not the first time I've written about this topic, but I haven't written formally about it in quite awhile. So I want to revisit why I think technical-position interviewing is so poorly designed, and lay out what I think would be a better process.

I'm just one guy, with a bunch of strong opinions and a bunch of flaws. So take these suggestions with a grain of salt. I'm sure there's a lot of talented, passionate folks with other thoughts, and some are probably a lot more interesting and useful than my own.

But at the same time, I hope you'll set aside the assumptions and status quo of how interviewing is always done. Just because you were hired a certain way, and even if you liked it, doesn't mean that it's a good interview process to repeat.

If you're happy with the way technical interviewing currently works at your company, fine. Just stop, don't read any further. I'm not going to spend any effort trying to convince you otherwise.

	var Aws = require('aws-sdk');
	var sinon = require('sinon');

	// Only works for 'createBucket', 'update' and a few others since most API methods are generated dynamically
	// upon instantiation. Very counterintuitive, thanks Amazon!
	var createBucket = sinon.stub(Aws.S3.prototype, 'createBucket');
	createBucket.yields(null, 'Me create bucket');

	// For other methods, we can 'assign' the stubs to the proto, already defined function won't be overridden
	var listBuckets = Aws.S3.prototype.listBuckets = sinon.stub();


	var commentSchema = new Schema({
	postId: {
	type: String,
	hashKey: true
	},
	id: {
	type: String,
	rangeKey: true,
	default: shortId.generate

	/*
	* A simple asyncAll example.
	*
	* Ignores any error handling and only returns the results to the done callback.
	* Each task is expected to take a callback for its first parameter.
	*/

	// Example call:
	asyncAll([doSomething, doSomethingElse], function (results) {
	console.log('all done', results);