Earlier quoted context omitted.
Being sloppy writing code, though, can be disastrous. I know I've rejected resumes for tech writing positions that contained spelling errors. I would hope a tech writer would at least use a spell chekker.
Unfortunate time for a typo there ;p
Why isn't there a universal data format for résumés?
241–250 of 472 posts
Re: Why isn't there a universal data format for résumés?
#242Re: Why isn't there a universal data format for résumés?
#243Earlier quoted context omitted.
It varies. There is a reason there is some level dislike for HR cohorts. Keyword bingo is one of those things. Minor anecdote incoming. I applied to a company A. It was a fit. I think I used the right keywords. Zero response. I talked with my buddy there. She talked with hiring manager. I got hired by company A. I later found out HR was unhappy, because it undermined their 'process' - such as it is. There just has to…
Do you really care that you made HR unhappy though? Seems like you shouldn't, the company/team management is probably happy to pursue references over the funnel of random candidates, and the unhappy HR staffer is better off learning from the experience.
Re: Why isn't there a universal data format for résumés?
#244Earlier quoted context omitted.
Perfectionism and pedantism are good qualities some teams are after, it is unsurprising that some people would reject a candidate who did not bother “properly” writing the name of the technology they use.
nodejs came out on 2009, I've used it non-stop since then and probably built close to 100 things with it. I am on the author's list of both node and v8. I write it as nodejs because that's how I got used to it on the mailing lists and several places that I frequent. If a "team" decides not to hire me because of the latter, then ... thanks, I guess?
But at this point we're getting into the territory of what's seen as a positive in some niche communities may not be seen as a positive signal outside that community. And in business communications, what masters most is knowing who your audience is, and how your message is received.
Re: Why isn't there a universal data format for résumés?
#245Earlier quoted context omitted.
Absolutely. We typically receive hundreds of resumes for every position. The easiest way to winnow them down is to throw out any with spelling or grammar errors. It is astonishing how high a percentage include these errors. There is absolutely no excuse to have spelling and grammar errors in your resume if you are serious about trying to find work.
Some people aren't native speakers. Do they really need to know how to spell perfectly to work for you?
Perfectly, no. But in formal communications, they need to show that they're at least making an effort to get things reasonably correct. And if it matters enough, you can always find a native-speaking friend to review your resume or cover letter for you.
(Source: been there, done that, applying for jobs in other countries).
Re: Why isn't there a universal data format for résumés?
#246Earlier quoted context omitted.
Absolutely. We typically receive hundreds of resumes for every position. The easiest way to winnow them down is to throw out any with spelling or grammar errors. It is astonishing how high a percentage include these errors. There is absolutely no excuse to have spelling and grammar errors in your resume if you are serious about trying to find work.
Some people aren't native speakers. Do they really need to know how to spell perfectly to work for you?
Re: Why isn't there a universal data format for résumés?
#247Earlier quoted context omitted.
>It's "Node.js" with a dot. If you spell it "nodejs", that's a serious red flag and you shouldn't be surprised if it gets you automatically discarded -- even by a human reviewer. Oh, really!? I'll be very glad NOT to work at a company that throws aways candidates because of such triviliaties.
Even back in the era when reading resumes and hiring was a manual human process, the standard advice was that resumes should be perfect. Nicely formatted, with no spelling or grammatical errors. You have ample time to think about the content, to proofread it yourself, and to have someone else proofread it. It's the first impression the potential employer has of you, no reason to not make an effort.
Re: Why isn't there a universal data format for résumés?
#248Earlier quoted context omitted.
Some people aren't native speakers. Do they really need to know how to spell perfectly to work for you?
FYI Not an English native speaker It’s a document sent to tons of people. Revised by tons of hiring managers. Can’t you spend 5 minute looking at a dictionary? If you cant be bothered to spend 5 minutes researching this for an important document, what makes me think that you will spend 5 minutes trying to be good at your job. Lack of care on your resume is lack of care on lots of other things.
Re: Why isn't there a universal data format for résumés?
#249Earlier quoted context omitted.
That's exactly what I mean -- people believe in Big Data so much these days that when something appears in a sufficient portion of search results, it must have actual validity.
Isn't that the same as natural language? "Bone Apple Tea" gets corrected both because it's wrong, and because many people know so. "Begging the Question" is used incorrectly _so frequently_ that even dictionaries have come to accept the incorrect usage as an alternative. It's now correct-ish just because it's popular. So if Node.js has that many more hits than nodejs, it's not surprising that some people see it as ca…
Re: Why isn't there a universal data format for résumés?
#250There is! https://jsonresume.org/ But nobody really uses it for data interchange. I use it to render my resume in new layouts now and then. Although, it does let style dictate content sometimes (some templates force you to have dates down to the day for job start and end dates, etc.)
Why should resumes in Vietnam or China be using English, after all.