lifehacker.com: I'm getting ready for job interviews and I want to make sure I'm as prepared as possible. For example, what questions should I be ready to answer in virtually any interview, regardless of the job type?Sincerely,
Questioning Mark
Dear QM,
You're right that most job interviews come with a set of stock questions, and while many of these seem easy to answer, it's always best to know what you're in for before you head into an interview.
6 comments:
Ah the days of college interviews I am reminded of again! Looking back, preparing for my interviews themselves was a huge process, and in the beginning of applying to colleges, I worried about what questions I would be asked the most. But in hindsight, I learned that the best way to prepare for any sort of interview is really just to understand yourself, your goals, your needs, your aspirations, what you're good at, bad at, or what you hope to improve upon. You must be honest with yourself. I think this a pretty comprehensive list of all the things you should reflect upon to evaluate yourself in the best way possible, so that you not only present yourself in the most positive but truthful light, but also to see if the place you are applying to, whether it be school or job, is your best fit.
I think this is a comprehensive assessment of interview jargon and what it means. I don't think there's anything earth-shattering in this article, but, like most lifehacker articles, it presents it in a very succinct package, which I appreciate. I always appreciate the reminders and slightly different examples that each article about interviews gives, regardless of how redundant the information is. My strategy with interviews has tended to be knowing myself and what I want, and then communicating that as best as I can to the interviewer, but knowing the "code" behind certain questions is equally essential.
This is a really useful outline for practical use. The questions that would throw me off the most have to do with weaknesses and describing how I dealt with a problem, because I wouldn't know how far to delve into answering those kinds of questions without giving away any negative hints to my hopefully future employer. the one I wouldn't have thought of is the salary question. But now that I read this over, that kind of question also gives your interviewer an idea of how much you think your skills are worth.
I'm taking a StuCo class called "How to get a job", and we were given a list of 100 questions, that compromised 98% of any basic job interview. They didn't include industry-specific questions like, "How would you light this scene?" or "How would you solve this coding problem?", but it is still incredibly helpful. Apparently people who interview a lot (like theatre freelancers) have memorized good answers to most of these, as well as common questions asked for their specific trade.
This article is something we talked about with joe pino in metaskills. I was remember that joe explained to us we must do our homework on an organization before we even think about applying there. For instance, if someone were to apply for a faculty position here they should be aware of our faculty, venues, seasons, mission, and community, etc. I also like the portion of the article about discussing a time you solved a problem. I always approach this question not as "when did you save the company" but rather "when did you change something that made a positive impact"
Welcome to the page of another generic breakdown and list of every question that could be simply asked in an interview. This list has it all, and I everyone one of these questions pretty much came up in my last interview. The site does a good job to explain how to simply and effectively answer their questions. Knowing what you want, how to convey yourself, and what they want are definitely essentials in an interview and this helps you define all of them.
Post a Comment