Loved this post. And I have some suggestions. Try 'em, if you like.
If you're taking the time to research the company you're applying to, keep that research in a subfolder in your primary folder for that job. A link to the company's website, for example, will save time when you're reviewing the position before the interview. Don't be afraid to slip into the conversation during your interview that you did some research - when the interviewer asks you if you have any questions of a general nature, you might ask, "I noticed on the company's website that there's a program involving x, y and z. Can you tell me more about that? How can I help with those programs? --or-- What would be my role in those programs, if the company chooses me for this position?"
Another subfolder idea: relevant work examples. Let's say you're applying for a job as a database administrator - bring with you copies of SQL statements you've written, flowcharts you've created for databases or processes you've designed, etc. Visual, physical-form work examples are especially helpful when you're doing an initial interview with someone at the HR level of the company; that HR manager is trying to screen you based on your resume and a list of skills supplied by the manager or department head who's seeking an employee, but that doesn't mean he or she actually understands what that new employee is supposed to *do*. And a big part of interviewing is demonstrating how well you communicate. That HR person has selected your resume based on how readable it was - now you have to show that interviewer that you know how to communicate in person, too. Work examples don't have to be elaborate, you just have to be able to explain them well. Don't be too pushy about providing work examples; just wait for the right opportunity to show them, such as if you're asked for them during the interview ("I'm glad you asked, I happen to have some right here," and bam, you're the most prepared prospective employee they've seen that day) or if you're asked to detail some examples of work you've done, then you can use these examples to supplement your explanation.
Speaking of websites, I was amazed at how many more interviews I scheduled after I built myself a professional website. And we're not talking about exec-level jobs, here - I was applying for basic admin assistance work - but many prospective employers complimented me on the site. I was often told that it not only made it easier for them to find and download my information, but it also made me stand out from the rest of the applicants. I was able to provide as much information about myself as I wanted to, broken down into sections on the site, and prospective employers found themselves coming back to the site during their resume review. I think employers want to know more about a person than is listed in a resume or CV - that's probably why so many employers are doing "vanity" (where they put your name into google and go look at the hits) and social network searches on prospective employees. I used a site called freewebs.com (it got bought by Vistaprint, it's called webs.com, now). Since then, LinkedIn has come along, and having a page there might be a good idea.
I do research companies but generally only after they call me for an interview. Even then it's pretty basic, so I don't have to worry about remembering a lot :D
If you're taking the time to research the company you're applying to, keep that research in a subfolder in your primary folder for that job. A link to the company's website, for example, will save time when you're reviewing the position before the interview. Don't be afraid to slip into the conversation during your interview that you did some research - when the interviewer asks you if you have any questions of a general nature, you might ask, "I noticed on the company's website that there's a program involving x, y and z. Can you tell me more about that? How can I help with those programs? --or-- What would be my role in those programs, if the company chooses me for this position?"
Another subfolder idea: relevant work examples. Let's say you're applying for a job as a database administrator - bring with you copies of SQL statements you've written, flowcharts you've created for databases or processes you've designed, etc. Visual, physical-form work examples are especially helpful when you're doing an initial interview with someone at the HR level of the company; that HR manager is trying to screen you based on your resume and a list of skills supplied by the manager or department head who's seeking an employee, but that doesn't mean he or she actually understands what that new employee is supposed to *do*. And a big part of interviewing is demonstrating how well you communicate. That HR person has selected your resume based on how readable it was - now you have to show that interviewer that you know how to communicate in person, too. Work examples don't have to be elaborate, you just have to be able to explain them well. Don't be too pushy about providing work examples; just wait for the right opportunity to show them, such as if you're asked for them during the interview ("I'm glad you asked, I happen to have some right here," and bam, you're the most prepared prospective employee they've seen that day) or if you're asked to detail some examples of work you've done, then you can use these examples to supplement your explanation.
Speaking of websites, I was amazed at how many more interviews I scheduled after I built myself a professional website. And we're not talking about exec-level jobs, here - I was applying for basic admin assistance work - but many prospective employers complimented me on the site. I was often told that it not only made it easier for them to find and download my information, but it also made me stand out from the rest of the applicants. I was able to provide as much information about myself as I wanted to, broken down into sections on the site, and prospective employers found themselves coming back to the site during their resume review. I think employers want to know more about a person than is listed in a resume or CV - that's probably why so many employers are doing "vanity" (where they put your name into google and go look at the hits) and social network searches on prospective employees. I used a site called freewebs.com (it got bought by Vistaprint, it's called webs.com, now). Since then, LinkedIn has come along, and having a page there might be a good idea.
Break a leg on your interviews. (-:
Reply
I do research companies but generally only after they call me for an interview. Even then it's pretty basic, so I don't have to worry about remembering a lot :D
Reply
Leave a comment