As well as a friend to many developers, I’ve seen both sides of the argument first hand and, to be quite honest, both sides have very compelling points. So, instead of defending one or the other, I want to try to present both arguments and then try to find common grounds. Think of it as a “Hegelian dialectics for programmers”.
The Case for the Young and Experienced
Profile In the past, I’ve worked both as phone number list a recruitment consultant and as part of the recruitment department of a middle-sized company. For those who aren’t aware, recruitment is more than reading resumes and prying on people’s private life with questions. The first step is understanding what your client (or company) is looking for in a recruit. To be quite frank, many companies begin their hiring process when it’s too late.
For example, they start
It when they realize a project is bigger and that’s not the only industry than they expected, or after someone has already turned in their resignation. This is like training a new firefighter when the city is already on fire. They want a recruit that can finish the interview and immediately sit on their workstation and get to coding. On average, people with experience acclimate to their jobs quicker and require less training.
It happens often enough
That decision-makers like to bet on thailand lists those odds. We as recruiters have to keep that in mind when we build the profile. On the other hand, IT is one of the biggest business trends, with thousands of new aspiring developers entering the market daily. For recruiters, this is quickly scaling to become an insurmountable challenge. Not only is the landslide of resumes massive, but the skill levels between candidates vary wildly.