Only suggestion, remember the first screen is some HR clerk, so consider how to think past them. This would include a simple cover letter. Second if you are asking for advice on EEtimes, them I am concerned you may need to reflect why would someone consider hiring you if you need our advice?
I think sometimes it is good to ensure the language and terminology being used in your resume is similar to that being used in the job posting to which you are responding. The person initially seeing your resume at the company may be less technical than the person you finally work for, so being able to express your skills in their langauge can be helpful.
And, please, please, please, research the companies you interview with. You are better prepared to answer the interviewers questions and it demonstrates that you are interested enough in the company and job to spend some time up front.
As a hiring manager, I find it more difficult to assess a candidate if I can't ask questions specific to my business. Yes, a good engineer can adapt to just about any situation, but as the person doing the hiring, I want to make sure that someone that I hire wants to adapt to MY company.
if you are good in fundamentals, doesnt matter where you write about courses in your resume, either before or after the work experience, prepare well and you might land up in the job. But to answer your question straight, training shouldbe after your work experience.
My Mom the Radio Star Max MaxfieldPost a comment I've said it before and I'll say it again -- it's a funny old world when you come to think about it. Last Friday lunchtime, for example, I received an email from Tim Levell, the editor for ...
A Book For All Reasons Bernard Cole1 Comment Robert Oshana's recent book "Software Engineering for Embedded Systems (Newnes/Elsevier)," written and edited with Mark Kraeling, is a 'book for all reasons.' At almost 1,200 pages, it ...