Monday, September 19, 2011

Recent Thoughts On Hiring and Being Hired

The job market is insane right now. It got to the point that I was receiving job-related email so often that I changed my LinkedIn profile to say I lived in Jacksonville, Florida (I don't - I'm still happily in NYC). However, I do read every job related email that makes it through Google's spam filter, and a few things did catch my eye recently.

Recruiters doing it right:
One recruiter emailed me and didn't ask for a resume, but did ask to see my github account. Setting aside the fact that plenty of code lives outside of github, this request impressed me. If they actually have people doing a bit of research on applicants via their open-source contributions, I imagine they're much better at hiring than their competition.

A different recruiter asked if I was available or if I knew anyone I'd be interested in referring, but the conversation was unique because the recruiter offered a $5,000 referral fee if a friend of mine was hired. Occasionally I will pass a recruiter's contact information along if the job sounds interesting, but I never spend more than 2 minutes thinking about who I know and if they are a match. Obviously, when 5K is the reward, I spent significantly more time considering who I knew with appropriate skills and desires.

Recruiters doing it wrong:
Don't bother telling me that you're offering a $500 referral fee. It's not that $500 is insignificant, but referring a friend is such an unlikely event that the payoff needs to be much higher due to how infrequently things come together. Also, if your competition is paying 5K and you're paying $500, that can give a false impression on what you'll provide as salary. I'm guessing some cool companies only offer $500, and that's cool - but, I think you'll be better off focusing on where you are superior to your competition and omitting where you're definitely behind.

Programmers doing it wrong:
If you're out of work right now there should be a significant reason why. Perhaps you are tied to a small town or a specific domain - those are valid reasons. However, if you find yourself without the skills you need to get the jobs that are available in your area, you've likely been neglecting your craft. This summer, a family member asked me if I could tell his son my secret to success. The best advice I could come up with was: Hit the job boards and see what the largest technology need is and get to work learning it.

Once upon a time the technology I knew the best was Pegasystems. I was laid off and I ended up spending plenty of time on and the various IT specific clones. There were jobs available, but everyone wanted someone with a Microsoft background. I ended up turning down some well paying jobs working with dead-end technologies and took a decent paying job that allowed me to use .Net. Twelve months later I accepted a job making 125% of the decent salary - which was the most I'd ever made. If you are passionate and have high demand skills you should always be paid well.

Another thing that surprises me is programmers who are "too busy to read about new technology or attend conferences". Perhaps I value innovation more than other programmers, but I simply can't understand this perspective. I see my job as more than whatever feature I'm currently working on. To me, my job is to provide the most features in the shortest amount of time possible. On occasion that means needing to get something out as soon as possible. However, my general working mode is annual production, and in that timeframe inefficiency adds up. On occasion innovation can offer productivity boosts that I couldn't match if I worked 24 hours a day using more dated solutions.

As an employee, I feel it's my responsibility to the company to ensure I'm not ignoring any innovation that could drastically impact my delivery speed. As such, I need to be on top of as many relevant innovations as possible. Interestingly, a side-effect of this attitude is that I should also have the necessary skills to find another job should I find myself looking around. This is an everybody wins situation, but only if you choose to do the right thing.

That's all I have off the top of my head. If you have any interesting experiences with hiring or being hired, please leave me a comment.


  1. Jay, I just hired five tech people five different ways: friend referral, social networking, pitching at meetups, contingency recruiting, and hourly recruiting. To find top talent, explore many avenues.

  2. Just a random note on Conferences - I, for the most part, don't attend them, simply because it's so expensive for me. A flight from New Zealand, plus accommodation, plus visa costs, plus the entry fee to the conference itself... That adds up pretty quickly, and I could easily be paying 10% of my annual salary for just one conference (especially if it's in Europe) - not to mention the fact that I'd need a week off work (3 days, say, for the conference, plus a day flying there, and another day flying back, or more! Could be upwards of 30 hours each way to the UK).

    But yes, I agree that you need to constantly learn new things, or at least be *aware* of the latest and greatest things that are out there in the market, so that if an interviewer says, "Hey, what do you know about node.js" (for example), then you're able to reply intelligently, even if you've never had a chance to actually do anything with it. Sure, it's not as good a look as being able to say "Oh yeah, I know that, and here's a link to a little project I made using it", but there's only a finite amount of time in the day, so you have to prioritize (and it gives you an opportunity to explain why you chose what you did :P).

  3. @ipsi, the Yow! conferences in Australia are quite good, if you're looking for something closer to home.

  4. I've learned the hard way there's no point in learning new technologies for your work, for the simple reason no one will listen to you.
    They would say "mind your own bizzwax" or "its your job to do it" or "why are you waisting time" even of you say uve done everything u were tasked , ull be frownd upon for not telling your boss so, or ull be soon be fired because they didn't have something for u.
    In the end technology will be decided on the whim and interests of upper managment with no relavence of what you think or say. If u don't have a life like me and wanna learn something new go ahead but expect it to be used at work. Just lay low. Don't take my word for it :

  5. @elhannan, I once worked for a few companies like that. Thank G-d I don't anymore. It sounds like you need to look for a better place to work where your passion for learning new skills and applying them will be rewarded.


Note: Only a member of this blog may post a comment.