Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I’ve never experienced it before now - how common is this? Is it a west coast thing? This was my first interview with a west coast shop. I don’t need an essay on why they thought it wasn’t a good fit, but radio silence seems eminently unprofessional.


Not sure how common but this has happened to me as well. Coding challenge complete, follow-up interview scheduled... then cancelled. Rescheduled... then ghosted.

It was a cheap way of figuring out I shouldn’t even consider working there.


> It was a cheap way of figuring out I shouldn’t even consider working there.

I mean - all you're experiencing is the HR/recruitment side of the pipeline at that point. You can't really say that an entire company is shit just because some subset of its HR/recruiters do shitty things. How many CTO's actually give a shit about IC interviewing experience and dig into the entire methodology that recruiters use when interacting with candidates? (And actually keep track of what their recruiters do) I'm gonna give a wild guess and put 0 out there.


In my case, it was a small shop and entirely through direct communication with the manager making the hiring decision. He seemed like a genuine, nice guy, so I'm leaning toward it being evidence that the dude does destructive, avoidant behavior, which is an unsettling tendency in a manager.


Regardless of how many CTOs do care, 100% of them should care. The reason they don't is there's no real incentive for them to care. Outing companies who do things like ghost candidates or have shitty, arbitrary interview processes probably isn't going to be enough to get most of them to care. But, some might, which is why I think it should be a regular practice.


Yeah, you don't need 100% enforcement to enact behavior change. You just need occasional, disproportionate punishment.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: