3 ms·
I know a lot of senior developers who were hired this way. I don't understand why that would make anyone feel ashamed.
by lexapro 5y ago
I know a lot of senior developers who were hired this way. I don't understand why that would make anyone feel ashamed.
- CodeWriter23 5y agoI think objectified is more likely the feeling than shame. I can think of no more certain way to let someone know they are being hired from the neck down than to offer them a job after 5-10 minutes.
- Loughla 5y agoIf the skills and abilities listed on your resume are what I'm looking for, you seem like a rational person who told the truth on your resume in the brief interview, and your references are clean, why would I waste anyone's time by stretching the process out? I thought HN hated convoluted hiring processes for the sake of making them convoluted?
- bmhin 5y agoYeah shame is a real weird thing to feel. I've been in plenty of positions where the ask is honestly "a body [who can code]". I fulfill that requirement so it's not a shock they'd want that and be interested and doesn't really say anything about me (or the person receiving the offer). My main feeling based on that would be pretty inline with the article: what's going on with this company/project where that's the bar and what will I be doing day to day for it? If I can choose to work somewhere that wants my skillset and not just someone who can code and lead other coders I will almost certainly enjoy, be more interested in, and grow more from the former. Then again, in absolute terms, starting from zero in something might be more of a learning opportunity in a way.
- nuerow 5y ago> I know a lot of senior developers who were hired this way. Knowing the hiring practices of some consultancy firms and how they routinely upsell their hotdog junior devs as prime rib senior developers, I have to say that I also know a few senior developers who were hired this way.