Pop quiz, job seekers!
I schedule phone interviews with candidates by email. I have a very specific template I use, example below:
Thanks for applying for the <job title> position with <company>. I’d like to schedule a phone interview with you Tuesday February 26 between 11:30am – 1:00pm Eastern time. Please let me know if you have 30 minutes available during that time and at what phone number I can reach you. Thanks, and I look forward to speaking with you!
If you received this email, what information would you include in your reply?
A resume submittal, a job application, or a request for information are the job seekers first opportunities to demonstrate how they complete an assignment for the employer. Too frequently job seekers focus on the quantity, not quality, of job applications and hence do not read for critical details. And that can adversely impact the impression they make on a recruiter or hiring manager.
The above example is a great case in point. I sent the email above 4 times yesterday. 50% of the respondents replied with a specific availability time–but not with the phone number. Not following this one simple request for information above needlessly drags out the scheduling process, but more than that it demonstrates that you didn’t read for detail. That’s not the first impression you want to make.
Another example: Although my current employer is based in Seattle, we have other locations in the US and Canada. Recently I was sourcing for a position based in our DC metro area office. About 20% of the applications I received were from candidates based in the Seattle area. Concerned that there was an issue with the posting, I audited all of the websites to which the position had been scraped (Indeed, NWJobs, etc). None of those sites showed the position located in Seattle; all stated it was for our DC metro area office. Curious, I reached out to a couple of people to ensure they knew it was in the DC area; both replied, “Oh, I saw RealNetworks and just applied assuming it was in Seattle.”
Take the time to read things carefully–and respond appropriately. It’s as much a part of the hiring process as the interviews.
You are almost guaranteed to be asked the above question one or more times during an interview process. And nearly every interview preparation guide advises to research the company. So everyone should have a great answer. Right? Then you might imagine my consistent disappointment at how poorly most candidates answer this question when I ask it in an initial phone screen.
The answer I most frequently receive: “Well, I’ve used your software, and I know you’re based in Seattle. . .” and that’s it.
I’ve said this before, and I’ll say it again: The interview is the final exam of your job search–but in almost all cases the only two grades given are A or F. I recommend preparing accordingly.
How? There are a lot of potential information sources:
That’s just a few resources of the multitude available to you. So what do you with with all of that information once you have it?
Well, first off–study it. Learn it–at least the basics. Understand the financials; they are key to the health of the company. Know who the key players and products are. Understand what’s going on with the company, and with their key competitors. This will help you not only be able to blow away the interviewer, but you should also be unlocking questions you’d like to have answered in the interview process about the company, product, leaders, financials, etc.
Again, I repeat: This is the final exam of your job search. Do you want an A? Or an F?
Happy Friday, everyone. It’s going to be a wet and windy weekend here, thanks to a storm that has us under a Winter Weather Advisory. Glad I’m not out on a boat today; there are healthy whitecaps on the Sound. It’d be unpleasant.
What’s on tap for everyone this weekend? I’m modifying my prior plans to wash the car and work in the garden…
I touched on this subject earlier this week, but it bears revisiting and expanding a bit.
I’m an enthusiastic home cook. I don’t do it as much as I’d like, but I do enjoy spending an afternoon or evening messing around in the kitchen. One of the things I’ve learned over the years is that the feedback loop is a critical part of the learning and self-improvement process in cooking (as it is in anything we do). This was brought to mind as I made a dish last week, Coconut Fish Stew with Basil and Lemongrass. It was something I’d made before, but it’d been awhile. I pulled out my notes and reviewed–the feedback from those who ate it last time was that the lemongrass was chopped too finely (per the recipe) making it tough to eat, and that could have used more vegetables. I took that feedback and used it in making the dish. As I went, I also recalled that I didn’t like how I had cut up the fish last time, and that I wanted more variety of seafood so I added large prawns. I also added white mushrooms and an orange bell pepper along with a bit of Sriracha to give it a bit of heat. The finished product:
The verdict? Much better this time. But it could do with a different type of rice, perhaps…and it needed more fresh lime juice as it lacked acid.
Why do I share this? Because cooking, like job hunting, is an iterative process. You execute a process, collect feedback, and incorporate that feedback into the next iteration with the final goal of achieving a desired result. In my case, it’s perfecting macaroni and cheese or a killer grilled pizza dough. For you, the job seeker, it’s about executing the process (writing a resume, interviewing for a job); requesting feedback and incorporating that feedback into the next iteration; and continuing that process and feedback loop until success is achieved–you’re hired.
This process should never stop. It’s tough for our egos, but it’s important to always be asking for feedback. The moment we stop is the moment we stop growing–and achieving our goals, like getting that next great job.
How many of you have interviewed for a new job in the past 5 years?
If you didn’t get the job, do you know why? What could you do to make yourself The Right Candidate?
I am always surprised at how few candidates actively request constructive feedback after an interview loop. I know it can be difficult to hear you didn’t get a job (or didn’t even get to the second round of interviews). It can be a blow to your aspirations, your hopes, your ego. And the prospect of then asking for why you weren’t selected–well, that can seem like insult on injury.
But you should always ask for feedback. It’s a feedback loop that is invaluable. Think of it as a gift someone is giving you for free that will help you become The Right Candidate. If you actively seek out feedback, really process it, and take action on improving your skills/experience/interview technique/etc–you will be able to leap high enough to grab that brass ring job the next time it appears.
Here’s a case in point: I recently received an email from a candidate I spoke with about a position nearly a year ago. At the time, we had discussed her resume and she’d asked for feedback as to where she might have a skills or experience gap. I provided her with feedback on what types of experience might make her a more qualified candidate for this type of role in the future. As a recruiter, it’s not uncommon to have these types of exchanges–and it’s extremely rare to hear from the candidate again beyond “Thank you for the input”.
Imagine my surprise, then, when I received the following nearly a year later:
Hello Jon – I hope this email finds you doing well. I just wanted to let you know I took to heart your suggestions and I have been supporting the executive team of a local non-profit for nearly a year. You were correct, there are many complexities to supporting true C-level executives. I now have the missing piece to compete for those positions of higher responsibility and challenge.”
(Note: I requested and received permission to use this email excerpt from the prior candidate.)
The email above exemplifies Doing It Right when it comes to constructive job search feedback.
Guess who I’ll remember the next time I have an EA search open up?