throwmeaway32

I have to disagree with this, I purposely hate it when applicants put information on their resumes that should have no bearing on my hiring them. It actually makes me worried as then if I decide to not hire them what if they say 'oh it's because I was too old' and try to sue.

Same with photos, marriage status or anything else.

If I shouldn't be asking it in a interview then you shouldn't be putting on your resume.

Also if your university reviewed this and said it was ok then please considered them useless.

My opinion (I interview and hire engineers):-

- Education goes at the bottom

- Tech skills go at the top

- The aligning on the work/url/date is really hard to read, just left align it, separate with -'s.

- The additional experience is almost a waste of space, I'd personally use the equivalent space to expand more on tech skills.

- You have 'proficient' then 'other', does 'other' mean not proficient? Use similar complementary terms to describe your skill levels i.e. 'Proficient at' and 'working knowledge of' or something like that.

- What's the difference between employment and technical projects? Some of your tech projects read like paid work so it's hard to tell what your skill level would be if I brought you in for a interview. if it's volunteer work I would put it under work but do something like '(volunteer)'

Basically your CV makes me have to think wayyy too much, I'm having to interpret things and guess what you mean, so I'd have no idea what to expect your quality to be if I got you in for a interview therefore I probably wouldn't bring you in.

Also if you're not doing it already then people connections is key (meetups etc)

- To plot a pixel in VGA Mode 13 it was quicker to do memaddress = (y<<6) + (y<<8) + x rather than (y * 320) + x to index into the frame buffer. Bitshifts are nicer than muls.

- Precompute your sin table into an array of 255 entries and then access it using index&255 to wrap around to avoid those pesky floating point calculations.

"One seeking a managerial position isn't necessarily asked to demonstrate and perform his skills on spot, are they?"

Yes they are (kind of), they are asked questions/problems which are used to gauge their ability to manage and do the job expected of them; in the 'best' way achievable in a interview scenario. Just like coders are asked questions to try to gauge their ability.

I'm not saying either ways are perfect, but it's not like a managerial interview is easy/non-challenging.

[Edit: Ooops saw a similar reply below, done way earlier...will keep mine here for consistency on my part]

Be passionate about the problem space the job and code exists in.

- Order of subjects :- Skills => work experience => Academic project =>education.

- Change 'Languages' to 'Languages (in proficiency order)' or something like that, I hate it when people just arbitrarily put the order of thier languages down so you have no idea what to ask them questions on.

- You descriptions are quite wordy and redundant, and can be cut down a lot:-

i.e.

"Implemented bug xes/feature requests to existing Java document management product." => "Implemented bug xes/feature requests to Java document management product."

"Code was deployed to IBM Websphere servers and required the use of SQL, XML, JDBC. Projects were managed using SVN and JIRA/Confluence and utilized jUnit testing and code reviews." => "Deployed to IBM Websphere servers and used SQL, XML, JDBC. Projects managed using SVN and JIRA/Confluence and utilized jUnit testing and code reviews."

"Designed and implemented custom document and workflow management systems for clients primarily using Java/IBM Filenet in both individual and team settings, including travel to client sites." => "Designed and implemented document and workflow management systems using Java/IBM Filenet in both individual and team settings, included travel to client sites."

"Developed an iOS app designed as a sales tool. Built using JavaScript/Cordova and managed with Git, utilizing jQuery and various libraries for JSON data visualization." => "Developed an iOS sales tool app built using JavaScript/Cordova/JQuery and various libraries for JSON data visualization."

How would you calculate your hourly rate? same as if you were a contractor? thanks btw