Hacker News new | ask | show | jobs
by mgkimsal 4194 days ago
A lot of software companies seem to have a set of conflicting beliefs.

1 Iterative/agile software development. YAGNI. Build the bare minimum, then iterate when you learn more.

2. Hire slow, fire fast.

A really agile org would be hiring fast too. Now... I know a lot of this has to do with labor laws - hiring an actual employee brings extra baggage. And in the US at least, more people may want to be employees for reasons like health insurance.

Even with those considerations, companies should be bringing on more short term contractors, and the ones that work out stay longer. The ones that don't, for whatever reason, move on.

The same teams that will say "YAGNI, just build XYZ, ship it, etc" - iow, just get stuff out the door - will hem and haw and take forever looking for a perfect candidate that, in reality, doesn't even exist.

It's early in the morning, this sort of makes sense in my head, but I may not quite be making sense. But it's still a seeming conflict that bugs me.

2 comments

I think this is something that would mostly be taken up by people trying in the early stages of their career. The revealed preference of more senior people is to not push for these kinds of contracts.

A shorter trial period makes a lot of sense, especially as more and more people with weaker tech backgrounds are drawn into software development by the strong job market. That said, internships fulfill this role for a lot of companies. Especially at the larger tech companies, internships seem like primarily an extended job interview.

I agree with this sentiment

More to the point, they think employees have zero flexibility. That if the employee is hasn't worked with a certain technology (like Hibernate, but has Java experience) this doesn't matter.

This. Above all else, this has driven me absolutely insane. I've immersed myself in and learned dozens of technologies in my past but because I didn't use one lousy framework I don't qualify? Something I could pick up in a week or -- at most -- a month?

This is especially true of startups. They feel like they're under pressure to produce yesterday and don't have time for someone to get "up to speed".

Worst is when they say "Well you don't have any Ruby experience. Maybe you could do a Ruby coding assignment for us." Then you spend the whole weekend cranking out a Ruby application only for them to say "This is great. Well done. But we really need someone with Ruby experience."

desk smash

Do you find this to be true of the hiring manager, or just the HR department that filters?