531–540 of 771 posts
Earlier quoted context omitted.
> If a language can't be found, they'll probably figure out that it's trap. If you're a qualified dev, you'd more likely conclude that it's a mistake on the part of whoever wrote the listing. I've seen skills listed like "Microsoft UML" or "Python, PHD, Nodes", so wouldn't think much of seeing "MOVA".
Job listing at old company once required COBALT experience.
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.
Arguably, I'm more valuable because I have the capacity to eventually figure this out, rather than having already memorized it. But if this were a crisis rather than a minor bug, it would be much, much better to have somebody who'd already spent that decade learning all of the many, many, many incantations that Spring Boot requires.
(I'd also argue that Spring Boot in particular is much, much, much too dependent on incantations, and the main lessons I've learned could be put on my resume as "Expert in Spring, and you can be too in one lesson: Don't.")
That really applies to all ecosystems. Hiring somebody smart is better. But there really is something to be said for having somebody with X years experience, who can therefore do some things in 10 minutes because they've already done the painful part on somebody else's dime.
Earlier quoted context omitted.
> Now that is why if I ever have to send my CV to someone it will only be a PDF version. Make sure it's digitally signed and locked. I've had recruiters do hacky edits to plain pdfs before.
Are you sure recruiters won't also circumvent this when they engage in such shady practices? Print and scan is an easy way to get around this.
Earlier quoted context omitted.
I scored fairly well on the SAT. I can’t think of anything short of a court order that would cause me to put it on my resume.
If someone had bad education credentials (bad school, dropout, etc) but they put a high SAT score on a resume that would be a pretty concise way of communicating "it wasn't because I'm dumb"
Earlier quoted context omitted.
would digitally signing and marking as no changes possible after signing work?
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.
Apparently everyone keeps forgetting that PDFs are editable.
> 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…
I keep remembering everyone that thinks PDFs are magically safer than Word.
Earlier quoted context omitted.
"The whole recruitment process seems broken " The IT market is pretty good compared to other fields but in the and, the market might have collapsed already. ""The Market for Lemons: Quality Uncertainty and the Market Mechanism" is a well-known[1][2] 1970 paper by economist George Akerlof which examines how the quality of goods traded in a market can degrade in the presence of information asymmetry between buyers and…
Probably some of that, plus the factors mentioned in Joel's old blog post: In an over-simplified world of Good Developers and Bad Developers, the Good Developers generally don't get fired or quit much, and if they do, can usually get another job through references they made at their last one. If they happen to not have any references who can get them a new job and enter the general recruiting market, they usually get…
Earlier quoted context omitted.
The recruiter was in idiot but not to consider c# dev for Java job is quite silly too.
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.
On top of that comes SQL backends, Web and occasional C++ for some native libraries to plug on.
At previous jobs the employer followed similar development approach.
I never got the Developer X mantra.
Earlier quoted context omitted.
they get paid a recruitment fee equal to a 1 month salary of their recruit It can go a lot higher than that, 3-4 months salary for more senior hires. The good news is this means the recruiter is incentivised to help you negotiate higher pay
Just like the real estate agent is incentivised to get you a higher price for your home? No, the increase they get is marginal, compared to just 'closing the deal'. Especially when the company is a repeat customer their incentives are to get decent candidates quickly into a role without causing any issues.