The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Rename the section "development platforms/tools" and then you can fit them in without stretching definitions
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
I don't use a blanket list of skills and such, because after being on the receiving end of resumes, I've noticed they are mostly lies. "I opened or modified an xml file, I should list that now" I only write my skills under the appropriate experience and projects.
Skills table at the top, above all else. If you go through H.R. or recruiters this is an absolute necessity. They are keyword monkeys and will do nothing but scan for keywords, in our field. Only hiring managers with technical expertise attempt to read into it. Make the skills chart easy for the drones and they won't review the rest of the document. You can then focus the CV on what the hiring manager wants to see.
There is a lot of contention on single page vs. multi-page resumes so I have designed mine to stand-alone on the first page with the additional pages being available for those that are interested.
I concur; it is very important these days to have an "HR and recruiter" section at the top with keywords (such as XML and JSON).
Just like Ennis, I also design my CV/Resume to have the front page be for these drones and then have subsequent pages for the details. I have been at both ends of the CV, presenting and reading, so I know what I like to see when I am going to consider a developer to join my team.
Edit: For God's sake don't call it "HR and Recruiter Section" though! Call it something like "Platforms and Technologies".
- I would love to change the world, but they won’t give me the source code.
Why bother? No offense, but it's not like you can differentiate yourself based on "knowing" XML and JSON. Everyone knows them - or they will after they read one page on wikipedia. There's not much to know, unless you want to count all of XML's "we pretended to throw away the useless cruft of SGML but kept a ton of it anyway - you're welcome" kind of stuff that no one uses anyway.
If you're going to list technologies, let them be cool ones - things you can actually call technologies without sounding like a marketing guy.
Sneak XML and/or JSON in the descriptions of past functions if you want. "Wrote JSON parser that improved the efficiency of the backend by 21%" is a lot more impressive then "hey I know how to use angle brackets", which is basically what listing XML as a "tech you know" does.
How do you group knowledge of technologies such as XML and JSON in your cv?
I am reluctant to put them under Programming Languages "group".
What title should I use for them instead? thanks.
XML is a computer language, but not a programming language. It is reasonable to list it as computer language that you know, but not a programming language.
FWIW, consider also where you might list the following languages that are arguably not programming languages: - Windows "batch file" - job control languages - XML - XSL - unix/linux shells such as bash, csh and friends - SQL - editors (which may or may not have commands/macros) - MS Word, Excel, PPT (and associated WordBasic, VBA etc.)
[Actually I consider XSL and shells to be programming languages. They have variables, comparisons, tests, loops and pass the Turing test...]
Having just had the benefit of a consultant reviewing my CV/Resume ... Paid for by the company not me! Don't have a section/group called "Programming Languages" just have an up-front table of "skills" ... then you don't have to badge them. Other posters have mentioned HR and low-paid trimmers who will just look for key words. So make sure those key words appear somewhere on Page 1. And the guys that haven't been in this space for a while will say things like "why are you even mentioning XML?" ... just like my colleague who "failed" to have "microsoft office" on his CV ... the job he was after included writing documents, handling spreadsheets, and presenting stuff ... lost out to the guy that mentioned all of that "trivial" stuff on his resume
Last Visit: 31-Dec-99 19:00 Last Update: 18-Jan-17 12:14