Source | FastCompany : By KAT BOOGAARD
Getting that dreaded “thanks, but no thanks” email for a position you were really excited about is a tough pill to swallow—there’s really no way to sugarcoat it.
If you’re like most people, you immediately experience a mix of anger, sadness, and a dash of hopelessness. And, while that’s totally normal (you’re allowed to feel upset—at least for a little bit!), that doesn’t necessarily mean it’s productive.
Rejection is actually a great time to reflect, evaluate the situation, and determine where you can improve next time. So, in order to help you do just that, here are five questions you should ask yourself after getting turned down for a job—that don’t involve, “What the heck is their problem?”
Your search can be filled with many emotions, including blind optimism. It’s easy to get so swept up in the prestige of a certain employer’s name or the numerous perks of the company culture, that you neglect to think about the responsibilities and duties that would come along with the job you’re applying for. It is a job, after all.
So, after you’ve received that brutal dose of reality, it’s time to do some self-reflection and determine whether or not you really wanted that position. Were you only interested because you wanted an in at that particular company—regardless of what you were doing? Did you only apply because you thought it would be impressive to your friends and random Facebook acquaintances?
Interviewers can typically tell right off the bat whether you’re truly excited about the position, or if you have ulterior motives. Take some time to determine if you were actually eager to land that gig (and, if so, what exactly drew you to it), and you’ll be much better informed to continue through your search.
When your search for employment grows long, you may find yourself falling into the trap of driving on autopilot. You’re coasting along, putting in the bare minimum, going through the motions, and winging it in your interviews.