Arvi Krishnaswamy bio photo

Arvi Krishnaswamy

Entrepreneur and Tech Executive

Twitter Facebook Google+ LinkedIn

Only 1 in 10 startups survives growth from initial co-founders to 10 people. Only 1 in 10 makes the next leap to a 100.

Invariably, hiring is a struggle at startups as they attempt to scale organically while retaining the culture and roots of their early days.

At many startups and small companies that I’ve known, executives run a fairly tight ship. Even all the way through 70-100 employees, its not uncommon to see several people wearing many different hats.

Hiring is hard

It’s worth reading a compilation by @swaroopch about the startup hiring challenges in India. Also, @guglanisam has outlined methods that have worked for Morpheus portfolio companies.

There’s a few common problems that I’ve observed (note that these not exclusively startup issues)

  • Young leaders have limited experience with the recruitment process, skills assessment, and how to fill out a team.
    • Hiring is often whimsical, without a sense of balancing a team out so that they can collaborate well together.
    • Managers either look for people similar to themselves, or those who are the exact opposite.
    • Expectations for new hires are not set clearly leading to fatigue a year or two into the job.
  • HR staff are given position requirements which list totally unrealistic expectations about the role.
    • HR ends up spending months working with recruiters to fill positions.
    • Recruiters get frustrated and lose interest in chasing down the requirements.
    • Since it’s hard to find a fit easily, candidates end up being on the ‘back burner’ for weeks altogether and often lose interest.
    • Good candidates end up getting filtered due to the nature of the recruitment keyword filters. HR looks for ready skills, but cannot measure potential.
  • Candidates end up interviewing with half the company before decisions are made.
    • Particularly common with Indian subsidiaries of small companies, senior candidates go through several rounds of telephonic interviews with overseas interviews in addition to various rounds locally.
    • Sometimes, even junior developers end up going through a number of rounds of discussions.
  • Despite complex hiring processes with checks and balances, bad hires happen.
    • These are inevitably a major drain on the organization.
    • In addition to 15-20% payouts to the head hunters, the loss is the significant amount of organizational time and energy that goes in.
    • Bad hires lead to a knee jerk response in the recruiting strategy, and an eventual downward spiral.

Given the rapid go-go culture of small companies, there’s often very little time to reflect on hiring mistakes, and to work through these issues upstream.

Unfortunately, this ends up being a huge issue. For most small companies, people are often their biggest asset and hiring mistakes can blow through your plans pretty quickly, causing tensions with the team, a loss of productivity, and eventual attrition.


The folks at InterviewStreet have developed a model that lets you run candidates through programming tests and puzzles (including custom modules). I think this has huge potential, and I expect that this would alleviate a lot of the pre-screening that tends to happen in the recruiting process to sieve out resumes.

Make new friends, work with them

The relationship between early founders of a startup is like a marriage.

You end up spending so much time with your team at a startup, that it’s important that your working relationship thrives through the highs and lows.

It’s important to work with people who are nice. But in startups, it’s nice to work with people who collaborate when shit hits the ceiling.

So, how do you make new friends and find people to grow your startup team?

You local community may also offer a number of avenues for meeting great people. Community meetups like Blrdroid, Bangpypers, as well as larger events like JSFoo, RubyConf, Droidcon, and Meta Refresh are great places to make friends and exchange ideas.

If your organization is involved in open source projects (honking great idea if you aren’t), those can be a great place to collaborate and explore things.

The best part about the working relationships that come out of the community? You get to work with friends.

Try new faces with paid trials

While it’s great to work with friends, its hard to scale quickly enough that way. Invariably, you get to a point where you need to expand out and meet a bunch of new faces and put them through the paces of interviews. I believe that instead of having candidates go through a battery of interviews, some of this can be evaluated better through a paid trial.

Here’s how I see a paid trial working:

  • A mutually agreed upon period of collaboration with the candidate
  • A set of activities that would be performed together towards certain goals.
  • These activities would be structured to model fairly typical interactions and working that is expected as a part of the role.
  • These goals need not always be tangible, although thaπt helps.
  • The activities should have mutual benefits - offering both the candidate and the company insight into each others thought process, working style, communication, and work ethic.
  • A mutually agreed upon remuneration for the work. More than the money involved, this shows that you are serious, and that you value each other’s time.

To be clear, I’m not saying we should do away with all interviews. It’s not going to be economically feasible to invest organizational time and resources into running trials with every candidate. You’d still want to run a first round of interviews to prescreen the candidate, and then discussions later for behavioral screening, longer term career growth, compensation expectations, and other non technical aspects of the discussion. However, there’s the rounds of interviews in between which may be better served by a trial.

‘Paid trial’ is likely not the best name for this. @justjots suggests ‘role auditions’ or ‘job auditions’.

If the person you are looking to hire is currently freelancing, it’s often easier to evaluate them for a period and then see if they may be interested in joining you. However, if they are already working elsewhere, it would be hard to get them involved with you in a full time trial.

Instead, it may make sense in having them take up a small project and work with you in their spare time over the course of a longer period of time. The split of work being done remotely versus on premise is dependent on your organization, work culture, policies, and the role itself.

Some candidates may resist the process, concerned about the time and effort involved. However, once they consider the amount of time saved from avoiding multiple commutes to your office, time spent waiting in the lobby, multiple interviews, and then various follow-ups, they’ll likely be much happier doing work that they actually enjoy.

Lets discuss specifics with examples.

If you are looking for an iOS developer with geolocation and networking skills, it may be useful to pick a small, active but non-critical app and have the candidate build out a small feature over the course of a month. For instance, getting someone to design a new IB screen, build out a view controller & wire up data model service calls may provide some insights.

If you are looking for an python developer with web dev skills, it’s easy enough to carve out smaller working assignments to build a decoupled service or a standalone site using lightweight tools like Flask or Bottle.

Interviews can get fairly hypothetical, but there’s nothing like working code. Great engineers know that great engineers ship.

Update 1

Nikhil Pahwa mentioned to me that he’s been using trials at Medianama successfully for the editorial hires. Vijay Sharma is using trials at Exotel.

Update 2

CampusHash is running InternHacks, a program which promises to help connect companies with interns that have real experience building things via a series of hackathons.