3 ms·
Honestly, I think the biggest problem is our own expectations. The way IT recruitment is just now, is not substainable and makes little sense. * There are more
by johnnyfaehell 6y ago
Honestly, I think the biggest problem is our own expectations. The way IT recruitment is just now, is not substainable and makes little sense.
* There are more developer jobs than developers
* We're constantly afraid of developers who can't code
* We decide to test every developer often with non-real-world scenarios and weird things they'll never do in their job and if they did do, you would be very concerned.
* Not only do we test them for things things they won't be doing, we also expect them to spend hours and sometimes days doing these tests.
* We reject people for weird random reasons. They don't understand one concept correctly, so clearly they can't do the job ever.
* We then hire recruiters, who realise how screwed out recruiting is and that it's often potluck. And realise this is a basic funnel, so they go and search out anyone who has a rough chance of doing being able job.
* We then blame the recruiters because people don't meet our weird standards.
For real, most companies need to realise they are not FAANG. They do not have an endless source of people wanting to work for them because of the reputation. Many of these companies that are acting like they can expect people to jump through hoop and hoop, have employee churn rates of 6-12 months and are competing with many other companies in their local area for the same talent. We continually act like like doing this job always requires the best. From what I see at most companies, you need one or two people who can archectect your system and explain the designs to people and after that you just need people who can follow the designs. We can say "But everyone should be able to do archectecture designs", if you want to spend your days discuss design plans and the benefits of this and that fair enough. But that's not what a company needs, a company needs people to write code they don't need 8 out of 10 to be designing code, they need 8 out of 10 to be "boilerplate" code so to speak. And if someone is able to take a code design and implement it without making it more complex then they're good enough for the job. Google is famous for making people jump through hoops and then have them do basic tasks, because doing basic tasks is what is important.
That's just my rant of the week on IT recruitment.
- maerF0x0 6y ago> a company needs people to write code Most of these companies would only need 1/2 - 1/4 as many "coders" if they'd get rid of their Not Invented Here syndrome and let the coders dictate how the product functions (technically). So many times I've had to build products that are arbitrarily designed by non-technical folks who don't realize that dictating their preferences, instead of flowing with the existing tech, quadruples the implementation time. That's just my rant of the week on stubborn folks who think their company is a snowflake that requires a bespoke software solution.
- deleted 6y ago[deleted]