i curse all those that lie on their resume about their experience!

[brainhulk]

2 straight fakers that we hired...I also blame my supervisor for not asking tough questions.

Now I'm stuck bringing up to speed another noob that I'm not really in the mood for.

 

[JSt0rm]

It's just opening beers. How long can it take to learn!?

 

[-Slacker-]

Hmm ... getting a job so I can make a living, or making sure I don't inconvenience the wise and all important brainhulk. Tough choice.

 

[BarkingGhostar]

It's just opening beers. How long can it take to learn!?

For some worthless people, you can give them a year of causing outages and they'll not learn. For other worthless folks, you can train them repeatedly on the easiest task and they'll still fail.

Naturally these were former vendor employees--cream of their crop. But I do place the majority of blame on folks that hire without conducting technical interviews. My complaint is as a team environment, my bonus is based on team performance--which is averaged low because of these worthless people.

 

[FelixDeCat]

I agree with you OP. Call me the last person in the world who is honest about their experience, but lying is a bad policy and leads to a short career. :thumbsdown:

 

[Bignate603]

Hmm ... getting a job so I can make a living, or making sure I don't inconvenience the wise and all important brainhulk. Tough choice.

Hiring someone that has lied about their experience can lead to things quite a bit worse than just an "inconvenience". It can cause pricey mistakes and cost you customers.

 

[Rage187]

HR let's them slip through but I gobble them up.

You type 100wpm? Get in this room and here is your typing test.
Built and maintain multiple websites with integrated shopping carts? Here is my laptop, show me your work including logging into the admin sites.
This is your code sample? (Deletes all the comments) Now, tell me what this code does.

anybody worth their salt is more than happy to show off any of the above and I can see the smile on their faces when I make the above requests. You know the liars as their eyes instantly glaze over and they start studdering.

I used to get pissed at liars but now I find it overly entertaining to catch them in the lies.

I've also volunteered to run the tech portion of other team's interviews. Unless it is someone specifically for my team, I can now skip the "tell me about yourself" portion and just get called in when it is time talk technology.

 

[Rage187]

I want to mention one of the best people I've interviewed.


We were interviewing for a mid career Tier 3 support job. He aced everything and the last part is some homework using the Adventureworks DB. Show us you know unions, outer joins, temp tables, etc.

The applicant comes back the next morning with the standard answers in a text file. However, he had taken the data and created a web dashboard with KPIs and built in analytics. This is stuff he built and was hosting, not Tableu, although he used some of the Google graphs.

I was totally blown away. He got the job and we also enrolled him in our management training courses. He took over his team 6 months later and eventually went to manage one of our professional services teams.

I thought about throwing water at him, hoping he would multiply.

 

[Gibson486]

There is a difference between telling a lie and selling yourself....some people do not know the difference, and quite frankly, some employers do not know the difference.

if you can back up what you say, then you are good. However, if you make a claim like, "I know Python", and all you have done was looked over a tutorial, then you have crossed the line.

It's a two way street, however. I went to an interview and the employer started plugging away about my previous job. My previous job title had the words "controls" in it. So, the guy interviewing me had this idea that if my job had "controls" in it, then it meant I knew about controls in sense of making classical control circuits. That of course is not the case. When we got to the tech, questions, he asked me this question about suppressing the transients on an inductive load. I got the question wrong. He just went, "well, as a controls engineer, you should know why a diode is needed to suppress a transients on an inductive load...". He flat out called me a liar in a nice way and ended the interview right there.

 

[Rage187]

My previous job title had the words "controls" in it. So, the guy interviewing me had this idea that if my job had "controls" in it, then it meant I knew about controls in sense of making classical control circuits. That of course is not the case. When we got to the tech, questions, he asked me this question about suppressing the transients on an inductive load. I got the question wrong. He just went, "well, as a controls engineer, you should know why a diode is needed to suppress a transients on an inductive load...". He flat out called me a liar in a nice way and ended the interview right there.

That sucks. But why did you even attempt to answer the question? You should have told him right then what your previous job really entailed.

I stopped looking at titles once the word Engineer started showing up in everyone's title. I now focus on what you say you know under Skills, Experience and Technologies.

 

[shortylickens]

2 straight fakers that we hired...I also blame my supervisor for not asking tough questions.

Now I'm stuck bringing up to speed another noob that I'm not really in the mood for.

Ask HR if he can be fired for not knowing the job he claimed to know on his resume.

 

[brainhulk]

Ask HR if he can be fired for not knowing the job he claimed to know on his resume.

Its a she. I'm just going to recommend she go back to day shift for more training. They fast tracked her training with me for just 3 days and then solo. People are going to be pissed because she was hired to fill holes as soon as possible.

I don't have the heart to try to get her fired, she's trying hard.

 

[sdifox]

err, there are probation periods no?

 

[brainhulk]

if you can back up what you say, then you are good. However, if you make a claim like, "I know Python", and all you have done was looked over a tutorial, then you have crossed the line.

It's a two way street, however. I went to an interview and the employer started plugging away about my previous job. My previous job title had the words "controls" in it. So, the guy interviewing me had this idea that if my job had "controls" in it, then it meant I knew about controls in sense of making classical control circuits. That of course is not the case. When we got to the tech, questions, he asked me this question about suppressing the transients on an inductive load. I got the question wrong. He just went, "well, as a controls engineer, you should know why a diode is needed to suppress a transients on an inductive load...". He flat out called me a liar in a nice way and ended the in

That's what pissed me off, she claimed she did the job by herself at the other hospital. So I was expecting to just be a passive observer and answer questions about policy. But when she didn't know simple things that one should know for this position, I knew I was in for a long 3 days...

 

[glenn1]

2 straight fakers that we hired...I also blame my supervisor for not asking tough questions.

Now I'm stuck bringing up to speed another noob that I'm not really in the mood for.

And you're probably one of those hiring managers who can't write a job posting for shit, completely misrepresenting the job duties, actual skill sets needed, and expecting an MBA and 100 years management experience for your $7/hour call center job.

Fakers work both ways, cannot count the number of times I've interviewed with someone who had no clue about interviewing, relevant questions to ask, or simply made hiring decisions on "gut feeling". And besides, as the manager, isn't your fucking job to ensure your employees can do their job?

 

[brainhulk]

And you're probably one of those hiring managers who can't write a job posting for shit, completely misrepresenting the job duties, actual skill sets needed, and expecting an MBA and 100 years management experience for your $7/hour call center job.

Fakers work both ways, cannot count the number of times I've interviewed with someone who had no clue about interviewing, relevant questions to ask, or simply made hiring decisions on "gut feeling". And besides, as the manager, isn't your fucking job to ensure your employees can do their job?

I'm not a manager, I'm just staff

 

[shortylickens]

Also something to keep in mind:

The way the workforce is right now its almost impossible to find someone who knows the job exactly. No one person can possibly have a wide enough variety in experience, unless they have a habit of only working 3 months at a time and then leaving and immediately finding something new.
And of course employers are wary to hire such people, so they actually dont get hired frequently and get lots of experience.

My point is that anyone you get will require some training. Often folks are picked cuz theres a deadline to get the position filled and they were the best of whats available, not necessarily the best. I got out of the Navy and couldnt find a job in Ridgecrest, so I ended up taking factory work in Eugene. A couple weeks there and all of a sudden I start getting phone calls from California asking me to do when I'm really good at. Since I didnt wanna fuck over my current employer and really didnt feel like making another move I told them no thanks.
Of course that was 2006 and I didnt know about the impending recession.

Had I known, I would have taken the job I was more qualified for and probably kept it all this time. As such, I wasnt a great microchip guy and was one of the first to be let go when the company was in trouble.

 

[shortylickens]

Oh, and Glenn, everything you just said reeks of ignorance.

 

[glenn1]

I'm not a manager, I'm just staff

Have you read the job description, and is it accurate? Also, the rate of pay being offered might mean no one competent bothers saying yes. Or that your manager has decided it's easier and cheaper to let you do onboard training than pay someone with more experience and higher salary expectations; or is doing this just to keep you busy babysitting the n00bs.

 

[JulesMaximus]

Everyone exaggerates a little on their resume. Outright lying though? Not cool.

 

[brainhulk]

Everyone exaggerates a little on their resume. Outright lying though? Not cool.

yeah, she flat out lied she did this job all by herself. She would not be asking me simple questions if she did

 

[ixelion]

I completely fabricated my experience for a job once, luckily I learned really fast and even exceeded targets on a regular basis.

 

[shortylickens]

Everyone exaggerates a little on their resume. Outright lying though? Not cool.

The whole point of a resume is just to get you an interview. No one should ever be hired without an interview. And if the boss does their job properly they should know if somebody is appropriate for hire by asking good questions.

 

[skim milk]

If people flat out lied about their experience, then that's an issue.

But I don't see any problems with spinning your story to match the job that you're applying for. It's just the nature of the game and if you don't do that, expect to be unemployed for a long time.

 

[-Slacker-]

Hiring someone that has lied about their experience can lead to things quite a bit worse than just an "inconvenience". It can cause pricey mistakes and cost you customers.

I was speaking as an employee, not as an employer.