Earlier quoted context omitted.
Why do they offer that?
It demonstrates that the client actually read the contract.
Brown M&M's clause, I like it.
We created a fake language to root out resume liars
171–180 of 771 posts
Re: We created a fake language to root out resume liars
#172Earlier quoted context omitted.
Jeez louise, imagine working somewhere where coworkers are regularly abused to tears. I really hope that that's an isolated case.
My sister worked at a recruitment company for a while and basically described the same. They set targets for everyone that were basically not achievable ever, and managers were expected to basically personally berate you for not meeting them and place you on warning to get you to work harder and more hours. She wasn't in a position to lose a job at the time, and felt she had no other choice but to begin lying about n…
"She wasn't in a position to lose a job at the time, and felt she had no other choice but to begin lying about numbers to meet the targets "
But what have they done to deserve the truth?
More or less this is how we get thinga like Chernobyl, when the entire chain is lying because the cost of tellong the truth is too high and there is no incentive to do so.
Re: We created a fake language to root out resume liars
#173Earlier quoted context omitted.
This is why some recruiters demand a DOCX of a resume, not just a PDF. They edit them before submitting them to postings. Sometimes they're honest edits to improve your chances, but mostly it's lying to get you in the door.
I’ve been using latex for my CV for years. If they ask for an editable version I just send them the .tex file. I’ve never come across any edited versions at interview.
Years ago, I recall someone musing about sending dvi files to an administrator, when asked for Word/Wordperfect files.
Re: We created a fake language to root out resume liars
#174Somewhat orthogonal but reminds me of the old map makers who used to insert made up islands / villages on their maps in order to prevent plagiarism. More here: [ https://en.wikipedia.org/wiki/Fictitious_entry ]
Hah, even more orthogonally but - I run a small statistics site for a specific esports title, and very often large companies (who host tournaments with hundreds of thousands of dollars in production and prize money) just use data from the site in their production without even crediting it. I added a bunch of very innocuous and subtle changes to some data somewhat akin to trap streets - specific values rounding in key…
You could probably monetize that service with a public API. Then screw over companies that take advantage of your services by providing them data that makes them liable, e.g. if they use it in gambling and they award the wrong prizes.
Re: We created a fake language to root out resume liars
#175Serious question: if you're applying for positions you're not totally confident in your experience and skillset, do you inflate your resume? My thinking goes that if I slip in by being dishonest, I'll be nervous of being found out, feel an intruder. So being honest and taking a longer time looking for match would get more comfort later on.
I've only ever increased the amount of experience I have with a technology and only when I am already proficient in it. No sense not applying to a job demanding 2 years of xp when I have 1 year but can use the tools proficiently, especially given the X years metric is usually pulled out of thin air by a recruiter.
Re: We created a fake language to root out resume liars
#176Serious question: if you're applying for positions you're not totally confident in your experience and skillset, do you inflate your resume? My thinking goes that if I slip in by being dishonest, I'll be nervous of being found out, feel an intruder. So being honest and taking a longer time looking for match would get more comfort later on.
I've interviewed on occasion (IT related). By far, the worst experience was about someone I approved and later discovered he clearly cheated/lied in the interview. Like, I set too high expectations and slowly but consistently realizing that "this guy just lied to me" in so many levels. I learnt from that so yes, for me, lying in an interview is the worst thing you can do.
Yup. I've had something similar where the interviewee was giving answers that felt very practiced. The recruiter was present in the room as well, taking notes (probably to prep applicants for the interview). We didn't hire the guy, and we no longer allowed the recruiter in the same room because of that.
Re: We created a fake language to root out resume liars
#177Long 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
I've heard about two companies who hired specifically in Scala because it would filter out mediocre Java developers.
I mean they got an unmaintainable, over-engineered and elitist Scala codebase as a result but hey, at least hiring was a bit easier.
Re: We created a fake language to root out resume liars
#178> 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…
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 will save someone's a fair bit of frustration.
Re: We created a fake language to root out resume liars
#179Serious question: if you're applying for positions you're not totally confident in your experience and skillset, do you inflate your resume? My thinking goes that if I slip in by being dishonest, I'll be nervous of being found out, feel an intruder. So being honest and taking a longer time looking for match would get more comfort later on.
When hiring, we filter applications on what they claim on the CV but also actually dig into the required skills on interview.
If we find a mismatch, it invalidates the candidate as a whole. If someone claims 8 years of MOVA but doesn't know basic stuff about MOVA semantics, they were either lying, they are incompetent, or they have been coasting.
Re: We created a fake language to root out resume liars
#180Earlier quoted context omitted.
Honestly, the thing I hate the most about IT is how bad it is while no one admits to it. These are problems I've encountered at several companies: * No budget for tooling. Be that software outside the ide or be it for hardware. * Cargo cult is so much bigger than anyone will ever admit. * The lack of caring about other departments. We're a team and we need to work as a team so the company can make money to pay our sa…
In my experience proficiency in UML almost always indicates that someone is not what I would regard as an "expert engineer".
In my experience if someone can't read UML and know how to write a decorator pattern something is up. Honestly, I've never used it in depth but for design patterns I expect people who are "seniors" to understand it. And I expect any expert to be able to look at UML and get the gist of it.
On a side note about design patterns, once as a junior I was at a digital agency and they were doing an in-house tech talk where one of the leads was giving an explaination and he was showing the singleton pattern but what they had allowed for two instances and when I tried to make it clearer to the intern that normally there is only one instance per singleton. The two leads were "Yea but it's still a valid singleton" - it was not but I wasn't point that out directly but continued to make it clear that most people would expect a single instance when talking about a Singleton.