<p>I had an officer interview for one of my EC's this morning. I didn't think it was going to badly until they asked me one particular question I didn't have a good answer for. I answered it, but afterwards I thought of a much better answer. I am now kicking myself; that one question was the only downfall of my interview. </p>
<p>It was like a rapid fire interview with four people asking me questions one after the other; I hated it. How do you handle such an interview? How do you get over the fact that you had a stupid answer?</p>
<p>A lot of times, if you don’t have a good answer, it’s best to improvise, or just honestly say that you don’t know. It depends on what type of question they ask though. For an interview, I feel like it’s best to show your personal interest in the job at hand, and why you more than anyone else would be completely committed to taking responsibility. Anyone can have the skill sets to “qualify” for a position, but if they don’t seem like they could care less about, it’d be hard to have faith in them. What kinds of questions gave you trouble?</p>
<p>Well, there were a lot of questions about leadership, what you would improve (about the organization), why you should be chosen, etc. I answered them just fine; I’m not worried there, and I think those were the most important, so hopefully it won’t matter that much. They asked me “what is procrastination?” to which I gave a literal defintion when I should have expanded on it saying that it’s “detrimental to the achievement of goals and to the success of an organization as a whole; therefore, it should be avoided”… Or something to that effect. Erghhhhh</p>
<p>I wouldn’t stress about it too much. It’s understandable that a question like that would be taken with it’s literal sense, and I’m actually surprised that they asked something like that. If you answered everything else just fine, it should be enough. Good luck!</p>
<p>Thanks. I just hope it was enough. I will find out tomorrow I guess!</p>