Excellent advice!

Vitaliy wrote:
> David VanHorn wrote:
>> Ok, I don't see much of this on the list, but I figured "why not?"
>>
>> I'm looking.
>>
>> I'd like to stay within the indianapolis / dayton / cincinatti area, but
>> anything's negotiable.
>> Obviously I'm an AVR fan, but I can work with anything.
>>
>> Resume on request, code samples etc.
>> I do analog, digital, SMPS, some RF, layout.
>>
>> A couple of recent projects: http://www.gizmag.com/go/4701/
>> And this one, which I did the barcode reading system for on a single 8 pin
>> AVR : http://www.beyondconnectedhome.com/products/microwave.html
>>
>> I've done a bunch of projects over the last 10 years plus, telecommuting
>> from home, but most of my clients have me under non-disclosure, which 
>> makes
>> it difficult for me.
>>
>> Anyone have an opening, or know of one?
> 
> Don't have an opening at this time, and if we did we would prefer someone in 
> Phoenix (telecommuting didn't work very well in the past).
> 
> However, if you want some unsolicited advice from an employer's POV, read 
> on. :)
> 
> The first thing you want to do, is have a resume readily accessible by a 
> potential employer -- e.g., put it on your website, or attach it to the 
> e-mail solicitation. I find it very annoying when something basic I need to 
> make a decision (personal references, code samples, etc) is "available upon 
> request." Why would anyone want to withhold that information, anyway?
> 
> In your resume, *clearly* state your objective, and list the projects you've 
> worked on. Again, be as specific as you can. I see a lot of resumes which 
> under "Skills/Experience" have a long list of buzzwords. As someone has 
> said, "you can't get a job doing something you haven't done before." A list 
> of the latest and greatest tools and technologies tells me nothing about 
> your personal skils and experience. Don't do that.
> 
> Instead, pretend that you're actually talking to the interviewer, and for 
> each project:
> 
> - Write a brief description of the project.
> - Explain what *you* did on this project. If you were working on a team with 
> twenty other people, the interviewer would want to know what your personal 
> contribution was.
> - List the tools and technologies which you used on the project, and (unless 
> it's obvious) explain how each technology was used.
> 
> Even if you signed an NDA, you should be able to tell the interviewer all of 
> the above, leaving out details that would identify the company you've worked 
> for, or the product you developed.
> 
> It's OK, and even advisable, to list "hobby" projects that you did in your 
> spare time. If anything, it tells me that you like what you do.
> 
> Above all, keep in mind that your resume will be read by a person, not a 
> machine. Write your resume accordingly.
> 
> Once you have the perfect resume, post your resume on a site like 
> Monster.com or CareerBuilder.com (both are free). Then do a search, and send 
> your resume to companies that you would like to work for. It's a good  idea 
> to modify the resume based on the company's needs, to make the content more 
> relevant (the job description usually tells you exactly what skill set the 
> company is looking for). Remember that HR people look for the perfect match, 
> so the more points you hit, the better are your chances of landing an 
> interview.
> 
> Good luck,
> 
> Vitaliy
> 
> PS A while back, there was a discussion with the subject "Re: [OT] Job hunt 
> advice". I highly recommend it. 
> 


-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist