621–630 of 771 posts
So, let me get this straight - you lie about your job requirements, but get all bent out of shape when the candidates lie right back at you? Brilliant. I can’t think of a better example of why hiring is broken; of how unequal the power dynamic is between employers and employees.
> That way, when candidates were pitched to us with "X years of MOVA experience", we knew that somebody was full of it. I'd put my money on the recruiter. I once had an excruciatingly awkward interview at a company on an industrial estate in the middle of nowhereland with no train station nearby that took me bloody ages to get to… which was actually going well until they asked me about my long experience with Exchang…
I've often wondered about how other's approach listing "skills" on resumes and interviews. Most of the tools we work with require working with it exclusively to become an expert.
Earlier quoted context omitted.
Had the almost exact same experience, but with Java. I'm a C# developer and although I have some experience with Java, I don't have enough to list it as a skill on my CV. Anyways, in this interview I was being asked about Java and I answered every question by saying I don't really know Java. The interviewers were obviously getting annoyed. So I asked "Sorry, I thought this was a C# job?". No, it was a Java job and ma…
just ask the interviewer the sha of the CV pdf first ;)
Earlier quoted context omitted.
If someone can't learn a new ecosystem, I have bad news for them in this industry. Also, rejecting someone because they can't rote memorize ecosystem specific incantations is... a pretty big red flag.
The trick isn't memorizing them. The trick is discovering them. I've been emitting various versions of Wingardium Leviosa at Spring Boot for days now, with no effect. Once I've learned the incantation I'll have it and can repeat it in ten seconds, but until I have it I'm producing no actual work. Arguably, I'm more valuable because I have the capacity to eventually figure this out, rather than having already memorize…
That is, unless I use Spring. The stupid Spring-related errors only appear at runtime.
Ok, honestly, after a year, using Spring is more convenient than not using it. (Basically, there are two or three types of stupid errors I usually do, and I learned how to decipher the intimidating error messages.) But the first experience is quite a shock. You write something with algorithmic complexity of Hello World, then you run the program, it throws a screenful of error messages, and you want to scream.
It reminds me of my childhood experience with Turbo Pascal, where you had to wait until the compiler told you that you missed a semicolon... and then it pointed at the wrong place -- not the place where the semicolon should have been, but usually the beginning of the next line. After some time, it becomes obvious, but the first time it's definitely not.
> That way, when candidates were pitched to us with "X years of MOVA experience", we knew that somebody was full of it. I'd put my money on the recruiter. I once had an excruciatingly awkward interview at a company on an industrial estate in the middle of nowhereland with no train station nearby that took me bloody ages to get to… which was actually going well until they asked me about my long experience with Exchang…
Had the almost exact same experience, but with Java. I'm a C# developer and although I have some experience with Java, I don't have enough to list it as a skill on my CV. Anyways, in this interview I was being asked about Java and I answered every question by saying I don't really know Java. The interviewers were obviously getting annoyed. So I asked "Sorry, I thought this was a C# job?". No, it was a Java job and ma…
While it was extremely unethical for him to change your CV, Java and C# are indeed very similar, to the point that most organizations use devs with that background interchangeably.
If that company really ruled you out because you had 7 years of C# experience, and not 7 years of Java experience, you likely dodged a bullet.
Long long time ago in a galaxy far far away I used requirement in job postings “10 years of Java experience” (when Java was about 7 years old) as a filter: people who wrote me complaining about unrealistic requirement got interviews; people who sent resumes with 15 years of Java went into /dev/null
Earlier quoted context omitted.
In the spirit of Hacker News I'd like to respond to this decidedly human problem with a technical question: which file format did you use for your CV? Was it an easily-edited .docx file, or a PDF? The PDF format is somewhat awkward to edit. I've never put much stock in the idea that this is one of its virtues, but for this specific kind of manipulation I can see it might be effective.
Just a note to anyone considering using PDFs for their CVs. Plenty of companies use Applicant Tracking Software (ATS) to manage recruitment process. Most often keywords are extracted from the CVs. PDFs are harder to extract from meaning you might not even be considered (or even ever seen) by a recruiter due to a far from perfect implementation. Of course the case here is different all together but maybe this insight…