Becoming Less Clueless: Interviewing

I theoretically understand what I need to do in an interview. But I’m really bad at them.

It’s not that I don’t know the answers to the questions I’m being asked – of course I do. They’re either about me or reasonably basic technical questions about things I’ve done and know. But I get self conscious about everything – my voice is too high pitched, I can’t pull off a suit, do I have a giant pimple on my forehead preventing my interviewer from processing a word I’m saying, when are scientists going to develop technology that would allow me to be a brain in a jar – oops, was that another question? It definitely doesn’t help that I really haven’t done many of them. In August, though,  I applied to a job that I really, really want. And the application process here? Well, it helped me get a lot more confident and a lot less clueless about the terrifying prospect of a job interview.

One of the things that I find discouraging is getting back a form rejection before even getting to a coding challenge, let alone the interview stage. I have no idea what that means – what specifically did they find unappealing? These are entry level positions, and so it’s rather unlikely that many candidates have much  more to offer than I do. So what is it? There’s only so much I can change, and for all I know, the rejections stemmed from other candidates being from “better” schools! Luckily, this application process was not like that. A couple months after I sent in my application, they sent me a coding challenge.

Fine, I thought. This is good.

A coding challenge is something that I can control, far more than I could with if someone was deciding whether to call me based on my resumé. Some companies will send you a timed test, which are almost universally hated, but this was better. I got a problem and ten days to return my solution. And you know what? I do know how to program. I may not be the world’s best speaker. I may panic at everything. But I am good at getting things done. Good enough that a few days after I submitted my solution, I got an email from someone in HR asking me to set up a phone interview. That’s when my obsessive reading of the Glassdoor page started out.

Now. I am a giant nerd that thrives off having as much information as I can on any given topic. So I read every single review of the interview process and wrote down answers to every question people said they were asked. I read countless lists of interview questions and practiced my answers to those. I made flashcards. I even recorded myself talking so that I could get more confident with the sound of my own voice. And when the interview actually happened…it went well! So I got an invite to an in person interview.

This was far from perfect. I stammered through a few answers. There were questions to which I didn’t like my answers and that I wish I’d answered differently. But it went well enough. My preparations weren’t perfect, but they were good enough that I got an offer. It made me realize…I don’t have to be ready for everything. I’m probably never going to be the kind of person that’s effortlessly confident and always believes in her own ability. But I am capable of preparing for the most likely questions well enough that I’ll be solid, and sometimes, that’ll be enough.

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