Ask YC: "Rock Star" Job Titles
So someone mentioned to me the option of working full-time for a period of time on a very exciting project. The cost benefits would simply yield supplementary income, nothing super spectacular, so not getting the gig doesn't immediately mean I'll be shit out of luck with money.
But then I saw the job post and it said "ROCK STAR Developer" and immediately I didn't want to work for this company. I was asked why by a third party, and I explained how the whole cliche of calling people ninjas and rockstars is pointlessly chic, and trivializes what you want the person to do because their name "looks" hip and trendy.
And dear god I know one thing if I know anything: trendy fails to deliver.
Anyone else here have an opinion on the whole "rock star" job industry mentality?
125 comments
[ 5.4 ms ] story [ 173 ms ] threadit's pretty simple: if you want to find the top 1% of developers out there, don't hire like 99% of companies.
I would use something like that as a flag of caution but I would want to see the job description/website/product information before making a final decision.
The Omni Group calls their support staff, "Support Ninjas", and I thought it was humorous the first time I saw it a couple of years ago.
http://www.omnigroup.com/company/people/
If it's a churn and burn shop that pays nothing then yes, stay away. If it's an over zealous HR person, than give them the benefit of the doubt. :)
I too am turned off by these titles for this reason. When I'm recruiting I just go for what seems honest and appealing -- nothing overly flashy or trendy, but not boring either. I think the best positions combined with the best companies will always stand out in some way, but that way will probably continue to change.
You want to get my attention? Tell me you're looking for a professional, and you're going to treat me like one. I want to know that I get 8 hours a week to work on opensource. I want to know that you're looking for craftsman, not ego maniacs. Mostly, I want to know that I'm not working with a group of people that saw the word rockstar and thought to themselves "Oh, rockstars huh? That's totally describing me."
Also, please please please don't tell me you have funding from a "Top Tier" VC. It's a sure fire way to convince me that you care more about your ego than running a successful company. Who the fuck cares who funded you? I don't care who, I only care that you're going to be around for a long time. And, you're going to consider anyone that gives you a ton of money to be "Top Tier", so it's completely meaningless anyway.
edit: i read 8-hours-a-day -- sorry. that is somewhat reasonable.
The unreasonable side comes from the inability to create hours. You can only add work. Side projects are always additive, unless you can stop work on a core project to do the side project. That's often bad for business, unless you're Guido.
The solution is to just work more to make up the hours. Most people don't want to hear that though, because they like the idea of getting a gift of choice from a company.
Allowing your employees to donate some time towards open source projects is probably a good way to attract talent. Advertising for "rockstar ninja" positions is not.
Seems like he's saying he's passionate about Open Source and wants that to be part of his job, not that he won't work on anything else. There are lots of people in the world who've learned that working on proprietary code means you say "goodbye" to it when you leave the company, whether you like it or not, and want to make sure they don't have to do that in the future. They've also learned that wholly proprietary companies are sometimes bitches about contributing to Open Source software even outside of business hours and on your own time and equipment!
If you're working for a company on Open Source software, you get to keep tabs on that code for the rest of your days, sending patches, if you like, etc. It's a major selling point for some of the best developers I've ever known--in fact, the very best developers I've known generally work on only Open Source software (so I'm excluding myself from this categorization of "very best", since I work on some proprietary software in addition to my predominantly Open Source work).
You also never know when one of those completely unrelated side projects will come in handy.
Actually, I find that the coding questions a company gives you can say a lot about the company. I really liked FriendFeed's interview problems, even though I struggled with them, because I saw them and went "Wow, these two questions test for nearly everything you need to know about a candidate, and do so with really simple problem descriptions." That's elegance - doing a lot with a little. While with some company's problems, you gotta wonder why they bother.
(That applies to some of the interview questions I asked at my last employer...damn, I was an idiot. But nobody else was asking any coding questions.)
Ultimately it is nothing but an upfront investment I have to make just to gain an interview, without a guarantee for a job. How would you like a job ad that read "to apply, send us 1000$ in cash"?
The advantage of places with puzzles is that everyone else had to go through them too (you hope; if it's just you, something's wrong). That keeps the bar high and ensures you won't be working with idiots.
Most worthwhile things require some up-front investment without a guaranteed payoff. Finance means putting the money up now for a hopefully higher return later. Education requires that you study now for skills later. Startups require that you build something now and hope you can get people to pay for it later. (Well, not always, but the bootstrap approach of finding a customer first requires that the customer pay up first and then take on the risk that you can't deliver.)
The trick is on doing due-diligence on the job first and making sure it's something worth investing in.
With college also, you get something in return for your investment (hopefully) - skills.
Of course if you just feel like chilling, why not choose some job puzzles.
http://lists.clug.org.za/pipermail/clug-work/2008-July/00062...
I noticed that the posting following yours was looking for a 'Python Ninja and Sensei'. What's next? Python Sumo?
"When everyone is a rock star, no one is."
Everything from GE calling their Six Sigma employees "black belts", to sales forces looking for "movers and shakers", to Fortune 500 companies overusing sports analogies, to people looking for "rockstar" developers.
It's trite and makes them look awful.
Pirates need love too!
"Pirates ship it."
If you really believe you want a star, say John Resig or someone similar, you better have a kick-ass project and be prepared to pay for him ... otherwise, you're just hoping you can get someone good on the cheap.
As a startup, I'm running cheap. But, when it comes time to hire folks, I'm stocking the damned fridge with the best stuff money can buy, buying great chairs and huge monitors, and anything else I can to make working for me and with me the best work experience of their lives. Even if it costs $5000-$7500 right off the bat to equip a developer, that's chump change compared to the opportunity cost of hiring a new one to replace him if he leaves. And it's a small percentage of their total compensation package. (And we have that wonderfully alluring Open Source thing going for us, so we won't lose folks just because they don't get to see their code set free.)
Reckon we could hire Resig? I hear he likes Perl.
Most startups are masters of spin, you pretty much have to be. Every developer is a "Rock Star", every VC is "Top Tier", every release is a "Revolutionary enhancement", and even though there could be 8 players in any one market, each one is somehow or another the "Leader", "Market Leader", or "Top Ranked" one.
Don't be turned off JUST by the job posting...
While the term "rock star" is a bit silly, a goal of mine is to grab someone from that 1-5% pool at a company that actually writes good code.
I suspect Google's example is the main reason for this change. Or evolution.
It's always possible that some horrible HR person posted the job. I've talked to some horrible HR people at Microsoft and Google in the past (when they were "cool" places to work with super smart types).
I think the most obvious move is to interview and talk to the people you will be working for/with. In many cases the specific project or team is as important as the company.
The job ad is just to get that initial interest. To get you to commit to sending a resume or taking a phone call.
Yeah but that seems to be what PG is saying here.
1) Code Baristas
2) Python Jockeys
3) CrackerJack Developers (retro!)
Ruby Commandos?
:)
T-Rex's
I disagree.
Puns are hacker activities. The real power of a pun is being able to see things from different angles and perspectives. References to "reddit", cynicism and reasons not to learn seem to be closer to what you mean ~ http://news.ycombinator.com/item?id=248509
after all reddit was in its begginings a hackers place
Had to complete the circle.
My employer follows the Starbucks antipattern of calling employees "partners". No longer content to be a UNIX Engineer, I'm henceforth a UNIX Barista.
Thank you for this. You've made my day.
If I read an ad that was looking for an expert in graph theory, or genetic algorithms, or whatever, with a strong knowledge of C++ for a small team where there were still opportunities to be treated as a co-founder ... then we're getting somewhere.
The problem with "rock star" and "ninja" isn't just that they sound dumb, it's that they're usually just a way of saying, "We don't really know what we're looking for, but if you're a workaholic, it might be you."
Everything I do pretty much falls into either software or electrical (hardware) engineering, at a higher or lower level depending on the job. I don't think of mechanical and structural engineers as having a monopoly on the term.
We have:
... along with the usual "senior software engineer" and such. You might think that would remove the meaning from titles, but I can tell you... I'll take a Mighty God of Thunder or a Head Greenskeeper for my project any day over someone that put Senior Software Architect on their business card.