Yikes. “It’s not JavaScript it’s Ecmascript! What a RED FLAG.”
https://www.reddit.com/r/javascript/comments/8d0bg2/oracle_o...
Not comparable.
Mine certainly isn't, it's like me. Worked out so far.
But then again, I wouldn't want to work for most companies.
Pecunia olet!
At least fixing stupid mistakes in your resume is well within your control, and (unlike cramming for their tests) doesn't take hours and hours of your time.
But my CV also shows part of my character, mainly the fun part. If that is deemed unprofessional by a company, I immediately know they are no good fit for me.
The thing is: As with every relationship, they are two way streets. I am not a beggar as a potential employee, neither am I king. We see eye to eye or not at all.
But to reject a candidate just because they're not the same kind of pedant that I am would be quite unreasonable IMHO. As long as the whole thing isn't littered with typos or formatting issues, that's just something I wouldn't pay too much attention to. Not everyone needs to be the person to dot every i and cross every t.
Also, I really want to see the HR department that can confidently reject or even mark down a candidate when most of the writing I've seen from most people in any company I've ever been (including from HR departments, PMs or executives) has been "meh" at best, and full of errors or at least awkward language more often than not. For better or worse, writing skills are not necessarily something we tend to select for in the industry.
Making such „mistakes“ actually shows quite a bit about the counterpart starting with correctness and precise communication.
Back then it drove me nuts when someone wrote „advanced in AngularJS 2“ - and it kept coming!
It really does require an eye for detail (in places where it matters) to a degree that comes epsilon close to being "pedantic" in the annoying sense -- without quite going over that line.
But whatever. It's your life. You do you, and I'll do me.
The only thing this filters for is people who have been looking for a job for a long time and/or are people focused on presentation instead of content, good luck with that.
We’ve hired incredible engineers across that have had typos and major resume mistakes many times and they had no communications problems on the job.
A resume is a background/interests check for the hiring manager. Giving them a spell check is about as useful as measuring the ratio of times the letter ‘a’ appears relative to ‘e’.
> critical business communications at least -- this level of correctness does matter, and it matters a lot.
This sounds like someone who is unable to contextualize when that would be relevant. Unless you’re writing user documentation there are zero times in an engineer’s day-to-day communications where writing nodejs instead of “Node.js” would have any impact at all.
I'll leave the matter of whether one should be expect resumes to be at least reasonably correct (in terms of spelling and grammar) or not - or what the threshold for "reasonably" should be on this front - to the side for now. It's obviously a question of taste, to a certain degree.
But sorry - what you're saying about the ratio of 'a' to 'e' makes no sense at all.
And on this front:
Unless you’re writing user documentation
I don't know what planet you live on -- but on my planet, good engineers write "user documentation" (in the sense of READMEs, docstrings, etc) and participate in mailing lists, do conference presentations, etc, all the time. And yes, while nobody is 100 percent perfect, consistently making a large number of gaffes (or more to the point: conveying an attitude that these things just don't matter; or that you're so hot that they shouldn't matter for you) in these contexts -- particularly when there there is plenty of time available to edit and review -- is definitely seen as a red flag, both in and outside the company.
For any company you'd want to work for, that is.
These days I think I work at the best team I ever worked on and it seems I'm in the top two in spelling, it is almost as if the rest if the team is mildly dyslexic or doesn't care.
But they are nice to work with, smart and they make good code.
I'll take them 49 times out of 50 over some perfect in code and writing but nasty in person ex colleagues.
Even if I really really really need a specialist on hight performance <whatever it was, I can't add a dead giveaway here> I'd still try to look elsewhere first.
Edit:
... and those two ex colleagues? Their code was good but it wasn't perfect either.
Sorry I confused you. Let me be clear, it’s not relevant at all to job performance. I would take someone with terrible spelling and punctuation who actually writes documentation over someone who writes half as much because they are obsessing over details like that.
> in the sense of READMEs, docstrings, et
These are generally for other developers. Developers do not get confused when they see “NodeJs” instead of “Node.js”. Do you know what point you were trying to make?
> is definitely seen as a red flag, both in and outside the company.
> For any company you'd want to work for, that is.
Not sure what kind of company you’re talking about, but it’s definitely not a tech company. Maybe Wall Street or something a little slower paced?
I've seen my fair share of resumes and hired my fair share of people, and I've come to the conclusion that sloppy, error-ridden, CVs are a sign of a lack of attention to detail.
Here's a candidate with all the time in the world, and huge motivation, and they still can't complete this task correctly. It's not a good look.
I'm not saying a single error I'd a deal-breaker, but it puts the applicant on the back foot. No doubt many of my rejects are quality engineers, but engineering, and software development are all about details.
You are woefully out of touch with the job market. And I’m saying this as someone who worked as a hiring manager at one of the most applied to tech companies in the world.
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.
Oh, really!? I'll be very glad NOT to work at a company that throws aways candidates because of such triviliaties.
It is never advice toward hiring manager. It was always criticized as not smart and leading to many false rejects.
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.
It’s ego.
What is the résumé’s job? To convey experience and work in a positive light. A small typo that may incidentally be the correct spelling shouldn’t derail that if the goal is to hire the most talented people.
To my defense, I was going by my Bayesian prior for certain language names for which one could be 100 percent sure there was no alternate accepted spelling or capitalization.
So if one put JAVA or PERL on their resume, that would generate a definite "pass" signal.
Or even if it's just 1 or 2. It's infinitely better to hire someone who is in fact really solid at what they say they know, than someone who tries to spam you with every random keyword they've been exposed to in the hope that you won't drill down and ask them any hard questions about most of them.
That, and skill listings that don't pass the "apples and orange" test. For example:
Programming languages: Java, Perl, PHP, XML, HTML, CSS, Bootstrap
The former 3 are full-scale programming languages, but the ones that come after obviously are not.Know yourself, and know your audience.
In some software, say, nuclear warhead tracking software, you want those people.
- resume keyword scan (automated or otherwise)
- leetcode interviews
The former I think you’re spot-on. If you’re serious about hiring, some qualified to do so needs to be reading resumes.
The latter is complicated. I tend to agree that the industry has over-pivoted to “dynamic programming whiteboard puzzle” as the LSAT of high-paying software work. But while most seem to agree that leetcode interviews suck in tons of ways, something that is unambiguously superior seems to be an open problem.
And some algorithms and data structure testing is important for hard software work. Even choosing the right library requires some basics. Is every SWE at Amazon implementing CS papers every month? No, clearly not. But unless machine resources are free in your domain, brute-force doesn’t always work.
FANG people do in fact get elitist about their CMU educations. But there’s another crowd that throws the baby out with the bath water: “I solve business problems, not reverse linked lists.” Well, what kind of business problems don’t involve some computation?
It’s a balance that our industry seems to still be trying to find.
on edit: before people come in with not wanting to work for a company that would make such a stupid mistake, first off I believe mistakes sometimes happen, and second Henry Thompson leader of the XML Schema working group, had the subtitle of his LinkedIn page saying something like he was an expert in XLM for at least a year (I should really have taken a screen shot) so I mean I think it would just as silly to not work someplace because they made a mistake as it would for them to screen you out for making a mistake.
And for people who want to work in startup land, it’s an ideal.
Once a company gets past 40 or so people, though, ATS adoption increases. And 150+ employees without an ATS are rare. It’s just that the volume of candidates and interview processes that need to be managed require there be some software to manage the workflow.
Best example of someone I wouldn't want to work for ever
perfect filter, both ways
Two ways of three. Some innocent person may accidentally put Node.js in their resume and get hired.
So if Node.js has that many more hits than nodejs, it's not surprising that some people see it as canonical.
Hearing the context of this conversation, though, I can see that "nodejs" in your resume is a signal to senior peers within that community--others who are "in the know". That may be a useful filter.
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.
There was even one time they forgot to give me the resume... that was probably the funniest interview ever. They got the job too.
Bullshit. There are many things person may care about and many things they may not. If this position is unrelated to professional writing, it's just irrelevant. Are you questioning their abstract ability to "care" and trying to translate spelling care to job care? Bad news, it doesn't translate (aside from the fact that ideal perfectionists can't get shit done ever; your best candidate still figures out the ideal form of his resume and is too anxious to click "publish").
Literally every time I have submitted an (academic) paper at least one US reviewer had to point out I made several spelling mistakes when I actually used the British spelling (consistently) instead of the US spelling.
Sorry my man but it is called "English", I think I am allowed to spell things like they do in England.
Agree. And yet, they are still the ones that mix up "your" and "you're", "then" and "them" and "than"
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).
Of course, it is also reasonable to be forgiving on resume errors. It depends on the culture and team you're trying to build.
From my experience, however, it's the native English speakers who spel the worse.
Besides, I've noticed that ESL speakers make different kinds of mistakes than sloppy native speakers do.
All of the lines below have red squiggly lines under them in my browser's text area:
- Qt Quick
- Datalog
- Datomic
- TensorFlow
> I've noticed that ESL speakers make different kinds of mistakes than sloppy native speakers do.
I've never seen a non-native speaker writing "would of" or using "they're" instead of "their". On the other hand I can't count how many times I've skipped an article or used a wrong one somewhere (since my native language doesn't use them at all).
She has internal word concepts. When the English words fit cleanly into her existing concepts it's easy. When two English words map into one word concept it's considerably harder, it took her a long time to correctly separate turn on from open (and turn off from close), but at least any given thing always goes the same way. In situations where that doesn't even work she will make frequent errors even to this day--do not trust her use of gender words.
Edit: oh, and also US state governments. there's a reason they're known for being incompetent, people job hop within months and get keywords on their resumes and nothing ever gets done
Haha and then they scream about labour shortage )
This isn't the "real world" you're referring to here -- it's the fin-de-big-tech bubble world where everyone and their dog is not only sold, smack-down drunk on the idea that Algorithms and Data are the Solution to Your Problems. They aren't of course -- it's just a giant hornswoggle. This "world" needs to end, and it needs to end soon.
My belief is that it will. But until it does, companies that run crappy ATSs (like there's any other kind) deserve the buzzword-gurgling, keyword-dropping candidate pool get. And developers who get "rejected" by these companies should be grateful for the sublime gift of this rejection -- and for the opportunity to laser focus on companies and teams that use their heads to hire, rather than a fleet of bots.
Snark aside - hiring managers that actually read resumes (and yes, actually at least skim each and every one -- really it ain't that hard) are golden to work for (other factors being equal). Really, you don't want to waste your time with companies that have drunken the ATS kool-aid. Really you don't.
That said, however:
HR is looking for "node.js" but you wrote it like "nodejs"? Though luck pal, bye.
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.
That's what resumes used to be, after all -- a kind of a take-home test where you really do have enough time (and perfect knowledge) to get everything 100 percent right. And also a test of your awareness of the fact that, yes, in critical business communications at least -- this level of correctness does matter, and it matters a lot.