Okay, let's start with your qualifications list:
Technically competent engineer with work experience in software development and electrical system design.
The word "competent" sounds mediocre. One would hope all applicants are at least competent.
• Held a high responsibility engineering position where leadership and engineering skills are required.
If it was high responsibility, describe the responsibilities. What sort of leadership decisions were you making?
• Designed, prototyped and tested microcontroller based projects.
This isn't so much a skill for the summary as it is a specific task to include in your experience.
• Friendly team player with a “Get it done” attitude.
Being good on a team is important, but you don't provide any evidence of working on a team or what your role is when you work in teams.
Professional Experience:
Nortek Automation, Huntington Beach, California
Engineer, August 2006-April 2007
• Developed well organized software for automation machines.
Tell us a bit about what the software was designed to do (as much as you're allowed to share without violating any confidentiality agreements anyway). What type of automation machines? What was your role on the project? Did you work with others to do this, or independently? Did you start from the beginning in implementing something entirely new, or were you improving upon existing software?
• Designed the electrical system in automation machines.
Again, were you working independently, or as part of a team? What challenges did this project present? Were you starting on an entirely new machine, or improving upon an existing design? When you were done, did it work? Did it improve the efficiency of some operation? Were there less breakdowns? I.E., what measurable outcome was there that you did the job well?
• Assisted clients with hardware and software troubleshooting over the phone and in the field.
What type of clients did you work with? Were you dealing with technically knowledgeable people, field engineers, business owners? What types of troubleshooting problems were you dealing with? What sort of problem solving skills were needed for this job? Did you have to come up with novel solutions to novel problems, or were you sitting in a call center with a flow chart asking, "Did you try...?"
Cal Poly Pomona College of Agriculture, Pomona, California
Webmaster, January 2004- January 2006
• Maintained Cal Poly University Pomona’s College of Agriculture website to ensure proper operation and update information.
Who were you working with here? Were these faculty pages, or Ag-extension service pages? What was "proper" operation? Were you dealing with the public, doing customer service, etc?
As a new graduate, you should also list your most relevant coursework along with grades (unless they were all mediocre grades, in which case leave out the grades) and any awards received. I'd also move your degree information to the top, and leave out the start date (I don't know if it's common to take 5 years to complete the program you were in, but it looks odd...people just need the graduation date).
And, as others have suggested already, change the job title to specifically match the job for which you are applying, and also match the objective to that as well. If resumes have too vague of objectives, it looks like you're just sending out a generic resume to anyone and everyone rather than that you're really interested in the specific company to which you're applying.