Skip to main content

Hiring for success

                             

Hiring for success

It goes without saying that you hire great people and they build a company for you.
Here are three points to consider when you are hiring, particularly if you are hiring to build your first product.

1. Don't hire someone if you would not work for them

This has nothing to do with how smart the person is; it is all about the attitude and personality. This is the philosophy Facebook adopted in their early days and Zuckerberg publicly admitted that he did not hire people if he thought he could not work for them. If you hire B grade players they would end up hiring C grade players and the quality continues to drop.
Pay attention to equal employment opportunity laws and make sure you clearly state your requirements in the position description. You will be asked for feedback from candidates with qualifications and experience meeting the selection criteria but eventually failed to make it.

2. Hire the smartest people and get out of their way

Once you finished hiring the smart people, immediately get out of their way and let them do what they are good at. Obviously smart people don't require managers to tell them how to do their work. This is not just for start-ups, increasingly large enterprises are looking up to start-ups for innovation, agility and inspiration.

3. Invest in people and provide enough challenges

Smart people are not going to stick around if they are not challenged enough. Create an environment where they are constantly challenged and there is a healthy competition.




Comments

  1. Cool and enlightening points mate. Will use it in my future hiring endeavors.

    ReplyDelete
  2. Will agree with previuos comment, very nice to see so wise article in blogosphere!I want to advice you to visit quite helpful site which offers a tons of helpful articles and writing help which fit all your needs!

    ReplyDelete

Post a Comment

Popular posts from this blog

Microsoft Dynamics XRM proxies–Early bind in ASP.NET web service

  As a hands on Development Manager I often get to lead by example, in my latest attempt to fast track re-development of some of our Java based web services to ASP.NET web service, I went about this using XRM based early bind method. I also explored SDK and JavaScript to execute the Dynamics rest API. For a starter our web service methods roll up large datasets therefore JSON based service was obviously not suitable. Also the java based services made calls to multiple stored procedures through Hibernate frame work, the idea was to convert any calls to Dynamics CRM using XRM with LINQ and other bits and pieces using NHibernate framework. I am keen to learn alternative methods and very open for feedback on the approach I have taken here. Without further ado here are the steps.   1. Re-Compile XRM to include proxies for Dynamics CRM customisations. This was easily done by executing the following commands within the CrmSvcUtil.cmd file REM $0\..\..\Microsoft.Xrm\bin\CrmSvcU...

External Authentication providers for SharePoint 2010–(Oracle/Sun Directory as user stores)

External Authentication providers for SharePoint 2010: Thank you for continuing to read my blogs. It is a Sunday afternoon and the Roosters are leading Panthers 10 points to 6 in NRL, by the look of it, it has all the signs of turning into a one sided match in the second half. I thought I might write a blog about SharePoint and Single Sign On with Non-Microsoft Technologies. The Problem: Often Organisations would like to utilise their existing stack of technologies with SharePoint. This is due to the popularity of SharePoint as a platform to consolidate and provide a range of application services either to replace an existing set of tools or compliment an existing applications suite. We fall under the latter. I am working within a truly heterogeneous environment at the moment, the extranet applications are built on a mix of technologies such as OpenText Livelink for DMS, Java and JBPM for for workflow and front end portals, Sun Directory and Oracle for User data and other DB La...

Combine agile and rapid prototyping to deliver a successful Microsoft Dynamics CRM project very quickly

  The Situation: If you are in the Software Development space you would have been at some stage, part of a long and winding CRM project. Also the reasons for the lengthy CRM projects range from requirements changing through the course of the project, lack of strong vendor selection process to strong leadership to make critical decisions. There is no silver bullet that can get you through the project without any of the above simply because projects are established and executed by people. How do we tackle a CRM project without much fuss.?   The Solution discussion: Microsoft Dynamics CRM provides the basic building blocks and the tools to extend it to meet your custom requirements. It is also easier to deliver a successful Dynamics CRM project faster by Combining Agile and rapid prototyping. This is exactly the approach being demonstrated here. This approach may not work if you don’t have enough experience within delivery team to estimate work effort accurately and execu...