Review my resume. Please.

you're overqualified ;-) Seriously, one thing you can do is taylor your resume to the company you're targetting . It takes more work but it increases your chances.

best regards, matt tudor

Snipped...

Infotainment is not a word. Not where engineers live at least.

And keep it short, because the personnel type who reads it first hasn't a technical clue. Avoid all jargon.

Hi there,

Quite impressive technical skills, but how about experience of project managemnet? Have you work as a team leader? (size of team?) Any direct contact with customers (e.g. customer/service oriented business environment)? Do you help train other engineers?

And yes, there are some problems with the use of some terms: > Extensive working experience with various 8-, 16- and 32 bit > microprocessor and several DSP architectures on hardware and software > (Assembler language) levels. Proficient in C/C++. Could it be simplified as "... on hardware and software (assembler and C language)" ?

In overall, it seems you are giving too much details of what you were doing instead of summarizing all into a list of skills. (And some information are overlapped). Using point form in the right places can make it easier to read without losing the professional touch. Try reorganise some of the information to make the descriptions of what you done shorter, and make your skills more noticable.

Hope these comments didn't discourage you too much. Your technical skills are very impressive and I think you should be well qualify for a lot of jobs. Good luck on your job hunting! :-)

Joe

I thought that maybe the cover letter should be a non-tech version for the HR types and the resume would have the tech stuff for the hiring manager.

But then, my resume hasn't won very many bites these past few months.

One thing that I've found to be helpful is to put hyperlinks into your resume that point to the places where you've gained your education and work experience. You can link to the company, or perhaps right down to the product(s) / project(s) on which you worked. (Assuming that you'll be e-mailing your resume, of course.)

Also, I've kept a marketing / sales brochure for every product I've ever helped develop. If I make it to an interview, I bring along this "portfolio" and show it off - it usually makes a good impression.

Good luck,

Mark

You say so much in the first sentence of the summary it's hard to grasp what you're trying to say - which since it's meant to be a summary rather suggests that you haven't thought about it.

Stephen

Hi All, Thank you very much for your interesting comments. I'm going to fix my resume according to your recommendations.

I have several additional questions to you:

1. I'm not sure about my TSCHNOLOGIES section in the Technical Summary. This is what I got right now:

... TECHNOLOGIES Ethernet, MOST (Media Oriented System Trasnport) and CAN (Controller Area Network) Communication Protocols: TCP/IP, DOCSIS Control Communication Interfaces: USB, I2C, SPI, RS232, RS485 I2S Data communication format Device Drivers: Ethernet, USART, USB, I2C, SPI devices; input/output user interface (keypad, displays), audio codecs, RF devices (frequency generators),. ...

Well, Ethernet, MOST and CAN are low-level transport protocols. It's all clear here. I2C, RS232, RS485 are control interfaces. But what should I do with USB and SPI? I can't classify them as pure Control or Data transfer interfaces. Or perhaps I need to list all these technologies with no classification? What do you think?

1. Cover Letter contains all the generic information about myself (7+ years of experience, self motivated, company success blah, blah, blah). What technical information shall be put in this letter? Somebody has already mentioned that these letters are usually viewed by HR, so too much techical stuuf will bore them. What are your opinions guys?

1. This is kind of of-topic question: I'm originally Russian, therefore my name is totally non-american. I also speak several additional languages beyond English and Russian. Hebrew is one of them. These who participate in hiring process, do you think it can scary potential employer for any reason? Of course, there is no much I can do about that anyhow :-), but maybe I don't need to mention all the languages I speak. What do you think?

Thanks again for your help, Vladi

In message , snipped-for-privacy@charter.net writes

Hi Vladi

I once employed a Russian - also Vladimir - in fact he's now a UK citizen. I've no idea if this applies to you, and no offence is intended, but while his English was very good, his accent was almost impenetrable. I took a gamble, but I'm sure it would hold him back with many employers.

Of course, colleagues quickly adapt to an unfamiliar accent, but there's no time in an interview. If this does apply to you, then you could maybe pre-empt the situation by saying from the outset that you know that some people have trouble understanding you accent initially.

Cheers

It's hard to know what would be best. I'd like to think that it doesn't make any difference, but to be safe you might want to leave it out of your resume and bring it up during the interview *if* it seems like a plus then.

In the US, it is illegal to discriminate based on race or religion. As a result, employers do not or at least should not want to know about those things. If you want to inform a potential employer that you speak Hebrew, do it in such a way that leaves your religion and ethnicity undefined.

Your language skills and even your cultural insights could be valuable for many companies. Just make sure you don't end up as a translator (:

Erm.. they're not quite the same, you know. The USART can work in either synchronous or asynchronous mode. UARTs lack the former. If they don't understand USART chances are they don't understand UART either.

I doubt if the recruiters/Human Resources people understand much at all, but they pattern match. If the employer is looking for UART experience, then they will look for UART. They might be able to infer that USART might be related, or they might not.

It's important to have jargon and acronyms somewhere on the resume ("Tools used", "Languages Used", "Skills") especially if you upload your resume into a resume database. The recruiters/HR people don't look at each resume, instead they do a keyword search. If the employer wants OSPF skills and your resume says "routing protocols", then your resume might be missed if they search specifically for OSPF.

It is according to the one respected dictionary I checked.

I think that if this resume does get you an interview (and I doubt that it will, its VERY difficult to read), you will be asked specific questions about one or maybe two of this shotgun list of communication protocols. People will want to know how you used them, how you programmed them or designed with them, and what the outcomes were. How these protocols are classified in your resume will be immaterial to them.

Your cavalier attitude to the cover letter indicates your misunderstanding of the importance of this letter. Most HR people won't get past the cover letter unless it moves them to learn more about you. There are lots of good books that have been written about the art of crafting a well written, compelling cover letter. Check one of these books out of your local public library and read it.

In my experience, multi-lingualism is the hallmark of intelligent, rapidly learning people. There is no need to conceal this ability. I think that for most businesses this ability (to speak multiple languages) is a neutral skill in that it probably doesn't fit into the firm's requirements for an engineer. I wouldn't list all of the languages that you speak on your resume unless you are applying for a position that requires these skills.