I'm not a fan of the column format because it causes problems with a lot of automated resume parsers that many recruiters and larger HR departments use. Most of the recent mods I've done to my resume are intended to get better results from parsers than from people. Is that a good or bad thing? Overall, I think it is good although I have created custom, less parser focused, resumes when I know I'm sending it directly to a hiring manager rather than a recruiter or overworked HR department.
One thing that I've been told to improve my resume is to make it more accomplishment oriented rather than task oriented. For example, saying what your project accomplished, like a cost savings for the company, rather than just a straight up description of the project. The tricky part is working that into something that's still resume parser friendly.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm not a fan of the column format because it causes problems with a lot of automated resume parsers that many recruiters and larger HR departments use. Most of the recent mods I've done to my resume are intended to get better results from parsers than from people. Is that a good or bad thing? Overall, I think it is good although I have created custom, less parser focused, resumes when I know I'm sending it directly to a hiring manager rather than a recruiter or overworked HR department.
One thing that I've been told to improve my resume is to make it more accomplishment oriented rather than task oriented. For example, saying what your project accomplished, like a cost savings for the company, rather than just a straight up description of the project. The tricky part is working that into something that's still resume parser friendly.