Recruiting and Hiring in a Digital Age

Job Interview

Prospective employees should be excited about the job and the company before they even reach the interview.

In job searches, the burden of excellence is generally placed on the prospective employee. Countless articles have been written about acing the interview, writing a perfect resume, and cleaning up your online presence, but what about the recruiters, hiring managers, and business owners that want to hire candidates that are more sought-after than the position they have to offer?

Often, hirers function in a vacuum of feedback. Those looking for jobs often tread cautiously, and, once they have the job, there’s little point in giving a review to the hiring manager or recruiter who handled them.


Social media is a two-way street

You know how easy it is to post job information through a variety of different channels in order to reach the maximum number of potential candidates. Employees are doing exactly the same thing. A resume often accompanies a personal website, LinkedIn profile with professional summary, Facebook profile photos (surprisingly useful — I’ve occasionally received calls from recruiters who are surprised I’m female!) The initial contact is like a cover letter to a prospective employee — you need to show knowledge and understanding of their needs, just like you’d expect them to research your company beforehand. You may find out that they’re not the right fit for your position, but you’ve saved yourself from ruining a valuable potential contact in the future. This leads me to my second point…

“Qualified and Looking” doesn’t mean they want the job

They have three years of Ruby on Rails experience, and are publicly advertising for employment — perfect fit for your 6 month contract for a rails developer, right? If you’ve researched them a little, you might find out that their LinkedIn profile, as well as their personal website states that they’re looking for front end web development, particularly with jQuery.

I received an email from a recruiter about six months ago, that stated upfront that she had read my website and LinkedIn profile, mentioned a few details about what I was looking for (not what she was looking for) and expressed disappointment that I was happy with my full time job, and that she didn’t have any part-time consulting projects to offer, that I could do on the side. She did think my background was great, however, and wanted to connect on LinkedIn, stay in touch, and asked that I pass around the position she was looking to fill if I had any friends who might be interested.

This is classic “How to Win Friends and Influence People” stuff — flattery, interest, and a real or perceived desire to fill the other person’s needs will get you everywhere. In a few months, when I came back on the job market, this recruiter was one of the first people I contacted, to let her know that I was looking.

Be upfront with job information

On several occasions, I’ve been asked to pass on vague opportunities with even vaguer job titles and little or no descriptions from “well-known” (but unnamed) Boston-area companies. For whatever reason, I didn’t immediately leap to my feet, saying: “Great scott! I’ve got to tell all my friends about this Rails developer position!” Not being upfront about the details (exact job functions/description, employer, hours, salary range, etc.) will eventually waste the prospective employee’s time, your time, and cost you valuable potential leads.

Be Honest About Your Requirements

It’s pretty common to see very low-level web development jobs “requiring” 5+ years of work history with multiple programming languages, on top of a degree in computer science, or some similar experience. I used to think that these sorts of positions were some sort of weird anomaly, or a case of HR not quite knowing what they wanted. However, after I started getting contacted for positions like these, I realized what it really was — a game between HR and the applicants, where applicants would often try to pad their accomplishments to skirt under the experience bar, while HR raised the job requirements level to compensate.

The problem is, that this tends to eliminate a lot of very good, honest, applicants from the pool, while only the over-qualified and severe resume-padders remain. The experience level can easily be re-iterated in the job description (“3+ years of web development experience — and we’re serious about this one!”) and it only takes a quick glance at a resume to weed out the relatively inexperienced.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: