Header

Wed, 4 Feb 2009

On Hiring Staff - The T-Shirt Method..
@

Anyone who has honestly reflected on what they know about hiring, will tell you that no matter how locked-down you think you have it, you dont. There is still way too much left to chance and way too much that you just dont know. To avoid this, companies that care about preserving their culture will sometimes adopt a "default deny" approach. It's ok to miss a potentially good hire rather than to take on a bad one. This isn't silly geek risk aversion.. It's because one bad hire can do amazing damage to a culture (an area bad hires can be amazingly productive in).

We have been hiring and interviewing people for about 7 years and have learned many lessons along the way but without fail, the one that works best for me, is the T-Shirt test.

The T-Shirt test is simply to ask yourself: "how will i feel standing at a conference, with this guy next to me wearing my company T-Shirt". If you don't like the thought, you shouldn't make the hire.

Now this doesn't translate to only hiring good looking people (but if whats important to you when standing up at a conference is the looks of the person next to you - you probably dont read this blog). The immediate question that comes up is "what if the guy is a real rockstar - but isnt presentable?". In truth, im happy with that, and far prefer it to a very presentable GQ model with a brain of a pea.

The T-Shirt question is a good evaluation of how you feel about the candidate and personally i can tell you that everytime i have ignored it, i have kicked myself a little later.

Interestingly enough, this doesn't have to be just for tech-geeks. If you are sitting at a management level or at a board level, the same question applies. I.e. How do i feel about standing next to this person at X, and how do i feel about him representing me / my brand. If your answer isn't positive, either he shouldn't be there, or you shouldn't..

/mh

Blog
Video
Research
QotW
Categories
about:us (31)
blackhat (5)
blog (10)
broadview (2)
build-it (1)
cloud (12)
community (15)
conferences (60)
crypto (3)
fail (3)
foos (1)
fun (51)
goodbye (1)
hackrack (2)
Hope? (2)
howto (8)
imsojaded (2)
infosec-soapies (25)
infrastructure (3)
local (5)
mac (15)
management (7)
materials (3)
memcached (2)
mindless-politics (4)
mindmaps (1)
PCI (2)
post-it (1)
privacy (6)
product (2)
programming (5)
public (275)
qo[w|m|?] (5)
README (1)
real-world (14)
research (37)
reversing (4)
security-fyi (8)
security-news (6)
silly-yammerings (19)
tech-toys (3)
time-waster (6)
tin-foil-hat (6)
tools (46)
training (18)
travel (1)
tricks (1)
Uncategorized (3)
vendors (6)
videos (6)
vulnerability (7)
wasc (1)
webapps (6)
web_x.0 (2)
writing-advice (1)
zen-hacking (6)
Archives
August 2010 (4)
July 2010 (1)
June 2010 (4)
May 2010 (3)
April 2010 (3)
March 2010 (7)
Feburary 2010 (2)
January 2010 (3)
December 2009 (4)
November 2009 (4)
October 2009 (3)
September 2009 (5)
August 2009 (9)
July 2009 (1)
June 2009 (5)
May 2009 (4)
April 2009 (10)
March 2009 (13)
Feburary 2009 (12)
January 2009 (11)
December 2008 (9)
November 2008 (8)
October 2008 (5)
September 2008 (5)
August 2008 (6)
July 2008 (6)
June 2008 (6)
May 2008 (2)
April 2008 (3)
March 2008 (7)
Feburary 2008 (12)
January 2008 (9)
December 2007 (8)
November 2007 (4)
October 2007 (9)
September 2007 (14)
August 2007 (18)
July 2007 (13)
June 2007 (17)
May 2007 (2)
July 2006 (1)
April 2006 (1)
August 2005 (1)
June 2005 (1)
May 2005 (2)
Archives
Conditions of use Privacy statement
Top of Page Legal stuff