Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The new hire who showed up is not the same person we interviewed

askamanager.org

Post reply on HN
Print view View original

441–450 of 623 posts

Re: The new hire who showed up is not the same person we interviewed

#441

Post by von_lohengramm »

wildzzz wrote: post #101
simmanian wrote: post #5

Practices like this are hilariously common in the industry. Right out of college I accepted a job offer at a small consulting company on the east coast. They promised they would give me free housing at their luxury apartment for the first few months and give me all the training I need to excel in areas of my interest. I flew across the country and found out the whole thing is not as advertised. Their luxury apartment…

An offer like that would seem incredibly suspicious to me. You want to pay all of this money to train me right out of school? Why not just hire someone with the right experience? Maybe it's my imposter syndrome speaking but it all feels off. I'm passively looking for new jobs but I always keep my eye out for things that sound too good to be true. If I'm not paying for training or education, then someone else is footi…

TSMC recently tried to poach me & offered paid on-site training in Taiwan before heading back to the States for the actual position. I reckon it's the modern job-hop game that killed this phenomenon outside of "lifer" companies.

Re: The new hire who showed up is not the same person we interviewed

#442

Post by worik »

smm11 wrote: post #377
skeaker wrote: post #321

Earlier quoted context omitted.

I've encountered this myself as someone who maintains small open source games. Engineers with vastly more experience than I do have approached me with contributions, but needed me to walk them through installing and using git. You could tell they were good engineers because they were so eager and happy to learn it. I can't speak for how big of a demographic these types of engineers are but they certainly exist.

Uh, git is how old? "Engineers with vastly more experience" might be how old? Hate to tell you, but these engineers probably wrote code pre-Google, or pre-WWW, and actually got stuff done. Amazing, that.

Heaps of us.

A stack of manuals several feet thick...

Re: The new hire who showed up is not the same person we interviewed

#443

Post by rasfincher »

sci_prog wrote: post #426
rasfincher wrote: post #424

My company hired a senior developer for an Angular project we were working on. They did great in the interviews and on our take home coding challenge. When it got down to time to work, I was walking them through the codebase and it very quickly became apparent they not only didn't know Angular, they didn't even know much at all about web development in general. They were let go three days later. I'd heard of things l…

Were the interviews not technical in nature?

I wasn’t a part of the interview process, but I was told some of the details. The interview was remote and they did well on the video interview and on the take home challenge. My best guess is they were being given help.

Re: The new hire who showed up is not the same person we interviewed

#444

Post by anothernewdude »

rootusrootus wrote: post #74
PragmaticPulp wrote: post #40

I've been a hiring manager for remote positions for a long time. If your recruiting channels are good, most of your candidates are going to be honest and good intentioned. But interview enough people, and you'll start encountering people trying to abuse remote work. They're not interested in contributing to your company. They're only interested in collecting paychecks while they do as little work as possible for as l…

> Always makes me wonder how many dysfunctional companies are out there letting deadbeat remote employees collect paychecks and do as little work as possible because nobody cares enough to press the issue. I'll take a stab at it, and predict... all of them. Or nearly so. There seems to be an ever-present fraction of employees at any large corporation that are essentially worthless. Just along for the ride, raking in…

As long as it pays more to half-ass your current job and take on a second, then people will prefer doing that. 100% effort is rewarded correctly almost nowhere.

Re: The new hire who showed up is not the same person we interviewed

#445

Post by jakelazaroff »

lazide wrote: post #242
jakelazaroff wrote: post #194

Earlier quoted context omitted.

Dear lord, that sounds horrible. I understand the reasoning, but corresponding with people — especially in formal settings — makes me anxious, and I end up composing and re-composing (and sometimes re-re-composing) a lot of my messages. The end result isn't bad, but if I were being watched and graded in real time I'm pretty sure I'd fail.

Sounds like that type of job might not be a good fit for you? You’d always be anxious!

It would not, and I wouldn’t apply in the first place! But I could do it if I had to.

Re: The new hire who showed up is not the same person we interviewed

#446

Post by Spooky23 »

worik wrote: post #442
smm11 wrote: post #377

Earlier quoted context omitted.

Uh, git is how old? "Engineers with vastly more experience" might be how old? Hate to tell you, but these engineers probably wrote code pre-Google, or pre-WWW, and actually got stuff done. Amazing, that.

Heaps of us. A stack of manuals several feet thick...

I started at the end of this era, working on a monitoring team that supported mainframes, network and data center systems. My second week on the job, my delivery of books arrived. About 30 linear feet of documentation. Iirc, it was part of our ELA.

I kept a couple of the references that I spent a lot of time in, along with my Perl books. Good times.

Re: The new hire who showed up is not the same person we interviewed

#447

Post by passivate »

ethbr0 wrote: post #371
no1lives4ever wrote: post #358

Earlier quoted context omitted.

Maybe it is time to get a new job. These days there is a big shortage of tech talent and deserving candidates can get very good pay in India. The typical trick is to apply for and interview to as many companies as you can. Get a good offer and put in your papers. Given that most companies have a 2-3 month notice period, once you are on notice, you can continue applying for jobs and shop around. The funded startups in…

2-3 month notice?! Holy shit, is this really standard? In the US, it's univerally 2 weeks .

To add - The 'notice' is a nicety. AFAIK, most employer-employee contracts in the US are at-will where either party can cancel the contract and part ways at any time for any reason.

Re: The new hire who showed up is not the same person we interviewed

#448

Post by hraedon »

908B64B197 wrote: post #435
hraedon wrote: post #408

Earlier quoted context omitted.

I guess it depends on your definition of "corrupt" and where you draw the line between corrupt and not corrupt. Would it be the tech recruiter's fault if there were, for instance, a pipeline problem that sharply limited the diversity of their candidate pool? I don't think so, but that wouldn't change the reality that the pool itself is a reflection of corruption elsewhere in the system. I don't know how you could pos…

These legacy admissions are also the reason most Ivies can afford to do need-blind admissions.

Even granting that the current admissions truly are need-blind (which I think it is reasonable to dispute), the smallest Ivy endowment is still over $4 billion. We’re not talking about a state university using full freight foreign students to subsidize in-state students because they have no other choice.

There’s no reason sticker price tuition at Brown needs to be almost $60k a year, and it is scandalous that Harvard, Princeton, and Yale charge tuition at all.

Re: The new hire who showed up is not the same person we interviewed

#449

Post by com2kid »

eternityforest wrote: post #431
nradov wrote: post #227

Earlier quoted context omitted.

Quoted post unavailable.

I can believe they don't have an extensive GitHub... but if they can't use Git they must have either only had a few jobs that all used something else(That's fine, just uncommon), or be in a specialist industry that doesn't use Git(Also not common), or they don't know VCS at all.

Plenty of companies use source control other than git. AAA gaming studios are famous for not using git due to git's poor handling of large binary assets w/o workarounds.

I've used other source control systems and they do have benefits over Git to be sure. Access control is a huge one, you can have a large repository and have fine grained access control over who can access what paths in the repository. Heck with some source control systems this access control may even integrate with Active Directory, so there is only 1 account to maintain!

The way to do that with git is to have a lot of tiny repos, with all the advantages and disadvantages that brings.

Don't get me wrong, git's ability to easily branch is huge. I am totally over working in source control systems that required an admin to approve creating a branch, or where merging branches was a huge deal that could take a very long time to do, but git isn't the end all be all of source control systems, and there are certainly features from other systems that I miss when using git.

Re: The new hire who showed up is not the same person we interviewed

#450

Post by ojbyrne »

I’ve had the experience (at a FAANG) where I showed up for an site and all the interviews had info on a completely different person. So my initial thought was there 2 Johns and somewhere between interview and offer they got switched. New John is going to graciously accept the offer, old John got ghosted.
Post reply on HN