571–580 of 771 posts
Earlier quoted context omitted.
I had a recruiter say "XML and UML are basically the same, right?". There's almost a dangerous level of knowledge among some recruiters where they think they know enough to do crap like this.
That's when you reply: no, "UML" was 3 versions before "XML"
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…
> Now that is why if I ever have to send my CV to someone it will only be a PDF version. This doesn't always help either though. I have only ever sent PDFs to recruiters for this reason. Yet I have still had a recruiter completely rewrite my resume and add false information. I generally keep a resume on me when I go to an interview just in case an interviewer had not seen it. I'm glad I do that.
Turns out it was a different resume that the recruiters would send us. They were garbage in quality and I hate them.
Fuck recruiters.
Earlier quoted context omitted.
Some companies want resumes submitted as text or .DOC, for easier keyword searching perhaps. Or to avoid viruses? So the recruiter may OCR the PDF, then "improve" on it.
Why bother? Apparently everyone keeps forgetting that PDFs are editable.
Certain tools, such as Word and LibreOffice, make it a bit easier as most of the source text is in the document, others like LaTeX end up looking like garbage through machine processing.
This reminds me of an anecdote I read once, maybe in Liars Poker, about how lots of people applying to this hedge fund put "Chess" on their resume somewhere thinking it made them seem like a deep or strategic thinker. As it happened, at this hedge fund there worked a former Soviet master or grandmaster ranked player. And so, whenever interviewing any candidate who claimed great proficiency with chess on their resume,…
Earlier quoted context omitted.
C# and Java the language are similar enough; the ecosystems are very different. A C# developer would mostly be expecting to develop Windows programs or possibly Windows server / IIS applications. A Java developer could be working on all kinds of different things.
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.
Where there’s time for new developers to get up to speed with a new tech stack, I completely agree with you.
Earlier quoted context omitted.
> I've been to plenty of interviews where my CV hasn't been given more than a glance. I do technical interviews and I never look at CVs before doing the interview. I do this to avoid bias. I want to treat them the same no matter if they went to Stanford or were not working for 10 years or if this is their first job. Also, people are adaptable, and soft skills matter a lot. So the error bars for recruiting even based…
What if there is something interesting on their CV worth exploring?
This reminds me of an anecdote I read once, maybe in Liars Poker, about how lots of people applying to this hedge fund put "Chess" on their resume somewhere thinking it made them seem like a deep or strategic thinker. As it happened, at this hedge fund there worked a former Soviet master or grandmaster ranked player. And so, whenever interviewing any candidate who claimed great proficiency with chess on their resume,…
"Knows (most of) the rules of chess" would be an accurate description of my level.
Earlier quoted context omitted.
I had a recruiter say "XML and UML are basically the same, right?". There's almost a dangerous level of knowledge among some recruiters where they think they know enough to do crap like this.
That's something I've noticed over the last 10 years or so as job descriptions get longer. All those new terms like React, Vue, SaaS, Azure, AWS etc. They don't really know what they mean. I was asked if I could code in Azure. This led to a weird conversation where I was trying to explain what Azure was, whilst he wouldn't listen to me and was adamant that it was a programming language.