Wednesday, June 12, 2019

5 Things To Do When a Hiring Manager Texts You



After a minute, you answer:

"I know this is a joke. Who is this? And why are you harassing me you a**hole?"

While you might think it's a friend playing a prank, the reality is that this can happen in today's job market where employers are looking for ways to speed up the hiring process, including an initial text interview.

So, now that you've called a potential employer an "a**hole" let's look at some ways you can make a better impression in the future when participating in a text interview.

1. Don't rush it. Your first inclination when hearing from an employer might be to toss off a few lines as you're ordering that latte, but don't do it. No employer is going to expect to hear from you within a few minutes, so take the time to form your thoughts.

2. Be prepared. Sometimes when an employer expresses interest, your brain can short-circuit for a moment, especially if this employer is one of your top picks or your job search has stalled. Be prepared with some standard answers to interview questions, such as "What makes you excited about your work?" or "How do you stay motivated?"

3. Be concise. Just as you would on the telephone or in a live interview, you need to respect the time of the hiring manager. Be concise with your answers, but don't be afraid to let your enthusiasm shine through.

4. Don't be sloppy. This is your first encounter with an employer, so be professional. Don't use text slang, don't abbreviate, make sure your auto correct doesn't make you sound like an idiot -- and always proof the text before sending. Forget the emoji -- there's too great of a chance it will come off as unprofessional and immature.

5. Show interest. Just as you would ask questions in an interview, don't be shy about asking questions of the hiring manager. Show your interest and knowledge by saying something like, "I just read online that the company is expanding into Asia. What an amazing opportunity -- do you know when operations will begin?"

A version of this post ran earlier

No comments: