7 ms·
We Rejected Dan Shipper (And What I Learned About Hiring)
- deleted 14y ago[deleted]
- deleted 14y ago[deleted]
- dustingetz 14y agoOP uses the word "rejected" 9 times. A-level hiring is not about rejection. A-players aren't looking for a "job" and A-managers aren't trying to build an assembly line. It's about finding a mutual relationship where the whole is greater than the sum of its parts, and that requires a lot of things to come together. > As a startup, if you have the opportunity to bring on an A player in a low risk role (like an internship), you do it All circumstances are different, so maybe he should have found room for Dan, or maybe not. Engineering quality (and talent in general) is on a power law distribution. When you consider engineering quality to be a competitive advantage (not all startups, even YC startups, need this), your early hires are your future managers, and will tend to influence the future hires. Its tough to attract and close people smarter/better than you. I imagine myself now at age 26 (pretty decent engineer, doing functional programming and stuff), and compare to age 21 (cocky, overconfident) and while I was smart and driven and all that, it doesn't mean I can contribute to a rockstar team. I would drown and get left behind. World class teams at the top of the power law distribution, say the Clojure team[1], at age 21 I'd be a few orders of magnitude behind them and just not worth paying. at age 26, who knows, probably still at least 1 order of magnitude behind, not worth hiring. Square peg, round hole. At least I can see my trajectory of exponential growth over the last 5 years, and if that keeps up another decade, I can build or join a team like that. [1] http://thinkrelevance.com/team http://thinkrelevance.com/team
- quintendf 14y ago(OP here) I should probably note that the use of the word "rejected" was done to emphasize the humor of the situation (we rejected someone who is now being publicly recruited), and to draw attention to what a mistake it was. I would completely agree that A level hiring isn't about rejection, job descriptions, or assembly lines. That's why I am such a fan of what Jason Freedman is doing at 42floors. To your second point, I remain a firm believer that early stage companies (less than 10 people) in this hiring environment should be open to bringing on A players, even if they don't fit into an immediately defined role.
- mstdokumaci 14y agowriting one sided stories about your business relations in public, like this, is not ethically correct, in my opinion.
- deleted 14y ago[deleted]
- moistgorilla 14y agoYou probably didn't read the article. I came into it with a similar mindset.
- bmelton 14y agoEven if the article was entirely positive, I personally wouldn't want anyone to know when and where I was applying. What if I were happily employed elsewhere when that interview occurred? I don't want somebody that didn't hire me to have any sway on my current employment unless it's where I'm working at the time. In this case, Dan personally reviewed and approved the article, but that wasn't known at the time (nor was it disclosed), so the caution was certainly warranted.
- masterzora 14y agoCaution is certainly warranted but assuming that they did wrong rather than asking if they did right is generally a bad way to go.
- quintendf 14y agoDan reviewed this post in its' entirety before it was published. I gave him final say on whether or not it was published or submitted here. I agree that personal stories like this should have the approval of everyone involved before they are published.
- GavinB 14y agoI strongly suggest you add this to the post itself. If not early on, then at least at the end. My thought that "they probably let Dan sign off on this, but it would be good to know for sure" distracted from focusing on the broader point of your article.
- pjmlp 14y agoWho is Dan Shipper?
- untog 14y agoI didn't remember until I read the article. Even then... well, I suppose "celebrity intern" is something Silicon Valley is going to have to get used to?
- kbronson 14y agoSo what? What have this guy done? Oh, and we've rejected another set of John Does here, by the way.
- mikemac 14y agoI believe it's referring to this: http://bit.ly/IHTk05 http://bit.ly/IHTk05.
- chollida1 14y agoActual link the above obfuscated link refers to: http://42floors.com/blog/posts/consider-this-a-job-offer-to-work-at-42floors http://42floors.com/blog/posts/consider-this-a-job-offer-to-...
- deleted 14y ago[deleted]
- MortenK 14y agoA sophomore at Penn university I believe. He has written a couple of interesting blog posts, which were featured here on HN.
- oinksoft 14y agoA self-promoter.
- gcp 14y agoBut in a review between myself and the company cofounders, one sticking point kept coming up: Not enough relevant development experience. We were trying to build a core front end team that had an existing passion for mobile/tablet, and Dan was a square peg in that round hole. It's hard to comment accurately without knowing much more about both sides involved here, but generally speaking, rejecting a (skilled+proven) developer who's willing to learn a new technology because he doesn't have experience in it is just...a mistake.
- debacle 14y agoI agree. "Not enough relevant development experience." is an answer that I would expect from an HR drone, not someone interested in hiring the best and brightest.
- muhfuhkuh 14y agoIt screams that technical recruiter type ethic: "at least 10 years Ruby on Rails experience required" when Rails isn't even 10 years old yet.
- jsprinkles 14y agoNo, it doesn't. Sometimes you have to choose between investing a shitload of money into training someone in the platform that you have, or hiring someone who won't require as much time to ramp up. Never underestimate how much of an investment is required to train someone on a platform; what if it doesn't work out? You've just trained someone partially who can't work for you.
- brandall10 14y agoNo one 'trained me' on Ruby on Rails as I transitioned out of working on the MS stack for the past 11 years. I learned that stuff myself. After 4 mos using RoR on one small project, I worked to get my foot in the door for a sit down at a startup looking for their first engineering hire. They wanted someone with 3+ years experience. After seeing some of my code and doing a sample project for them (learning the basics of Sinatra/DataMapper/OAuth/FBGraphAPI to crack a problem they had a need for in a weekend), the CTO said I pretty much blew away many people he's seen who've had such experience, and in the end I was the one to say no to moving forward after the interview process. If you're looking at people who 'need' to be trained then you're looking at the wrong people. You're looking for people who can crack the more meta-problem of actually learning shit quickly and subsequenty getting shit done quickly.
- jvandenbroeck 14y agoI think the whole thing is kinda ridiculous, making a blog post to hire somebody.. Maybe I'm just outgrowing HN or it's because I'm from Europe that I don't get the fuzz. More on topic, I quite liked this blog post & think it was much more informant than the one from 42F
- mattdeboard 14y agoYou're conflating HN with a single blog post.
- credo 14y agoI know nothing about "Wheremyfriends.be, a simple webapp " and it is interesting to see how a brand is being built around one of its three developers. However, I hope we see less of these hero-worship posts on the front page (or at least limit the number of hero-worship posts until something more substantial has been accomplished) Btw self-seeking flattery of powerful, influential people is generally considered as sycophantic. Is there a good term for flattering people like the guy described in this post :) [edit] for chc and anyone else who didn't get the sarcasm, yes, the intern wasn't powerful. That is precisely why the smiley-question asked for a new term
- thenonsequitur 14y agoTurns out if you trace the etymology of sycophant, you end up with "fig-shower" (sykon = fig in Greek), where "showing the fig" meant something along the lines of "flipping the bird" today. http://www.etymonline.com/index.php?search=sycophant http://www.etymonline.com/index.php?search=sycophant The opposing hand gesture to bird-flipping might be peace-sign-showing. So how about "pacophantic". (And FWIW, I thought the sarcasm in your question was immediately clear, not sure how other people misunderstood it).
- debacle 14y agoThis isn't a powerful, influential person. From what it sounds like, this is a programmer who is engrained in the startup ecosystem, being blogged about by the founder of a startup because he was acquired by another, more noteworthy startup. The term you're looking for is self-seeking.
- chc 14y agoI thought we were talking about a college sophomore who wrote something cool and gained recognition for his skills. Who's the powerful, influential person that Mr. Farmer is flattering? I believe the term for flattering people like Dan Shipper is "paying a compliment." EDIT: You're right, I didn't get the sarcasm. In the context of a comment that described the OP as "hero-worship," it doesn't come across as sarcasm. If we acknowledge that the guy is neither powerful nor influential, it seems pretty obvious that the OP's "flattery" is merely paying a compliment to somebody he respects. I think we could use more of that and less "So-and-so is full of shit" articles.
- tocomment 14y agoIt's funny, when I read that 42 floors offer, I thought Dan Shipper was a name they made up for a hypothetical developer who "Ships" (produces) code. So I thought it was an open letter to all good developers that they wanted to hire them. Granted, I only read the first half of the post...
- saturn 14y agoTL;DR: HR at some no-name start-up gets it into their head that some kid can make all their programming dreams come true. They made a blog post to lure him. Later, HR at some other no-name startup makes a blog post proudly announcing that the kid in question applied there first, also making some annoying backhanded compliments about how their standards were too high or some lame shit. What next? Nothing at all.
- spudlyo 14y agoObsequious omphaloskepsis.
- krschultz 14y agoNot only do I hate TL;DR meme (I don't believe it fits the community at HN), but that isn't even an accurate summary of the article or the situation.
- spudlyo 14y agoAgreed. I thought the parent was ill served by editing the post and moderating the language, which for me more accurately described how I felt about the article and situation.
- SethMurphy 14y ago> it was clear that Dan had the mentality and intellect of an A Player. He was young, driven, and extremely intelligent. Young has nothing to do with mentality or intellect. Nice to hear someone who is in charge of hiring be honest and say it out loud though.
- sliverstorm 14y agoWhoa there. The quote can be interpreted two ways; the way you read it ("young, driven, intelligent" = "mentality and intellect of an A Player") and the way I read it ("mentality and intellect of an A Player. In addition, he was young, driven...")
- SethMurphy 14y agoAgreed, but without the additional language you added, I did read it differently.
- dpritchett 14y agoThere's no legal upside to publicly being interested in young people. The best you can really do is look for inexperienced people with low salary requirements.
- orangecat 14y agoEither way, "young" is surrounded by a bunch of other clearly desirable attributes. Were I a litigious applicant over 40, I would find that significant.
- sliverstorm 14y agoNaming names in these "Why we didn't hire this person" always comes across as showy posturing. If you want to talk about insight gained in the hiring process, you don't need names. You only need names if you want people to be impressed by all the famous people you turned down.
- jsprinkles 14y agoThey're trying to ride the Dan Shipper bandwagon. I thought that would have been clear; there's no other reason to write this post.
- deleted 14y ago[deleted]
- ericson578 14y agoWhat is an "A Player"?
- dpritchett 14y agoIt appears to be a reductive staffing methodology invented by this book: http://www.amazon.com/Topgrading-Leading-Companies-Coaching-Keeping/dp/1591840813 http://www.amazon.com/Topgrading-Leading-Companies-Coaching-... The key points: - Hire people who are awesome - Fire people who aren't
- biot 14y agoThe term A-player originated in the sports world a long, long time ago. It is literally a player of the sport who is considered A-grade material. This phrase, like many other from the sports world, has been adopted into the business lexicon.
- jcc80 14y agoIt's anybody who you hire at your startup - until they leave and then all of the sudden they are C players. Because, if you only hire 'A players' and you have decided to hire John Doe #4 for some combination of skill, experience and vibe, then John Doe #4 is now an 'A player' by default until proven otherwise. And thus the myth continues - "We only hire A players."
- prawn 14y agoFirst time I've heard the term, but I take it to be the sort of person who is brilliant enough that you hire them and then work out what to do with them. I know a sporting example might not be overly popular on HN, but let me try! In the NBA draft, teams will choose between drafting to fill a need (e.g., they're weak at centre, so they'll draft the best big guy), or drafting the most talented player still available (e.g., a brilliant point guard even though they already have two). In this hiring context, it's a bit like drafting on talent alone - take the "A Player" and worry about the details later. In the NBA example, this means trying to force a fit (shifting a SG to SF), trading them for things you do need (an elite SG for a decent big and a roleplayer), or rebuilding your team around them. Michael Jordan was drafted third in 1984. The first pick (Olajuwon) was a top-tier talent but the second pick (Bowie) was a bit of a bust. Portland took Bowie ahead of Jordan because they already had Paxson and had recently drafted Drexler.
- silverlake 14y agoHiring is random. There have been numerous studies that show people are highly influenced by interviews despite the fact that it's not a good indicator of ability. Would you have hired Systrom or Krieger (instagram) as engineers? AFAIK, they had no experience building large-scale sites, yet put together instagram. Would you have hired Paul Bucheit when he applied to Google? AFAIK, he hadn't done anything spectacular yet. A-players are by definition people who have done something big. Who hired these people to give them a chance to do something big? What about the larger group of people whose startup flamed out before they could demo their skills? It's all a crapshoot. Hiring is easy. A small startup is receiving resumes from a self-selected group of people who want to work there despite the low pay and lower job security. Most of the people reading HN could build an instagram-type system. So once you filter for ability with some stupid programming quiz, just pick the guy you like. If your company succeeds, he will magically be considered an A-player.
- jrockway 14y agoI'm waiting for the michaelochurch analysis of this situation.
- dpritchett 14y agoDid Google also reject Dan? (Kidding, I have really enjoyed Michael's recent spurt of blog activity.)
- nhangen 14y agoThis feels like a reach to prove superiority and save face. Surprised Dan approved it.
- georgieporgie 14y agoAlways hire A Players Words cannot describe how tired I am of hearing these sorts of weird sports metaphors used to describe tech talent. Are we really so immature as an industry that we have to constantly rely on sports metaphors? It's as bad as talking about ninjas and rockstars. Also, I'm really sick of all these mindless, droning, uninsightful posts about hiring in general. Who cares? Tech interviewing and hiring is a joke, and everyone here knows it. Larger companies act like you're saddled with the new hire forever, even though in most places reading HN it's extremely easy to fire people. Small companies act like they absolutely have to find the best talent in the universe, even though what they actually need to do is get some product shipped. It's all just ego stroking and an attempt to codify insecurities. How about more awesome submissions about hacks, ingenuity, and product success, and less B.S. about name-dropping, baseless pontification on interview tactics, and overuse of bad metaphors. While were at it, let's drop the bubble FUD and ridiculous guesses about big company tech strategy. /rant
- 0xDECAFFEE 14y agoBut what about all the Ruby on Rails brogrammers?