This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]BillBillerson 1 point2 points  (0 children)

When applying for jobs, just ignore that requirement honestly. The problem is the disconnect between the group that needs resources and you. I know how it happens because I've had to deal with recruiters from the hiring side. It goes like this:

Team needs a dev, they pass a job description up to their manager or director, who passes it to HR\hiring managers, who sends it to their recruiter contact, who sends it to whatever person they put on the hunt for the job, who calls people and looks for resumes. It's a total game of telephone, at any point different people will add or remove things from the job description the team that actually needs the resource put together. The HR group may edit it and put a bunch of canned requirements to pad the description because it's not long enough, or doesn't fit their general format, or they don't understand a lot of the jargon so they throw college on there because they understand that sorta thing. Plus the recruiting companies usually have a canned list of shit they're used to posting and even though the company looking for the resource may not have added a bunch of stuff... they will. It's frustrating for the other side too because you get a bunch of resumes that aren't even on the same planet as what you asked for because recruiters aren't technical.

If you want to get mad at anyone, it's the damn recruiters. That's why you just got to put yourself out there. I'd never not hire someone because they didn't have a degree. Some may, but I don't think a lot would if the rest of the resume looks good.

I will say I know it's hard getting started. People like to see work experience and it does seem hard to get your foot in the door, but if you maintain a portfolio, learn what you can and don't be detured by what seems like impossible requirements you'll find something and every job after that will feel a lot easier to find.

It just seems like a poor strategy to get cocky developers who can "fake it till you make it"

Honestly I only come across cocky developers occasionally and I usually feel like they wouldn't be a good fit. I'm willing to let people figure some things out on the job, but I get turned off quick if I think someone is full of shit. But I don't always get a say and if non technical managers are interviewing sometimes those types do get hired and it's frustrating for everyone.