DEV Community

Discussion on: Is rejection for a job becoming more normal or...?

thinkslynk profile image
Stephen Dycus

Some issues I've seen over the past year or so.

  • Non-existent roles for junior / entry level devs - This is a big problem, and not just for people trying to get their foot in the door. Where I currently work, our devs would love to get more experience training and leading a team of more junior devs, so they can focus on solving more challenging problems. But management does not see a benefit in investing in entry level positions or having students intern with us. This leaves our developers feeling overtasked while our numerous "senior" developer job listings sit on the website for 6+ months.

  • Broken, and sometimes questionably legal interview processes - I remember interviewing with a company that had a 24 hour test that required you to interact with a very specific api. The api required you register to use it, but would not allow you to use any FREE email service such as gmail... I just HAPPENED to have a private paid email account, but I can imagine how many other devs took this test and just gave up. I'm not sure it's legal to require someone to PAY to get a job... Anyway, I didn't get the job because their back end java developer didn't like my Android code; someone who had no experience with Android, criticizing the work of someone who was a lead developer for 3 years on a very successful photo sharing app.... I then joined a company where I was awarded my first patent for a custom OCR solution and have now transitioned into a full time machine learning role. This isn't meant to brag, but to highlight that these hiring processes are often highly flawed.

  • Irrelevant coding challenges - "Solve this graph theory problem." ... "Isn't this a front end web development position?" You see this a LOT with larger employers, such as Google, Facebook, etc. They don't really care if you're good at your job, they only care about weeding out false positives. They'd rather turn away a few good developers, as long as they can "guarantee" that those that ARE hired are competent. Unfortunately, this means those of us who are self taught often get weeded out, because we often only attempt to learn new concepts when we feel we can immediately apply them in a project, where as a student fresh out of college who just learned this information can get the job, without having any real world coding experience.

  • Impossible or unnecessary job listing requirements - "Must have 5 years experience with this technology that has only been around for 3 years." Or "Must have 15 years experience with this one tech stack." I just out right ignore these listings, but they are plentiful, and make it that much more difficult to find a real job listing.

  • Fear of inadequacy - This may just be me, but as someone with a pretty severe case of imposter syndrome, I am often too paralyzed with fear to apply for roles that I feel I may be a little under qualified for. I hate wasting peoples time, and I hate the idea of having a company fly my out for an interview when I'm pretty sure they won't think I'm qualified.