>What is your suggestion for OP where their resume is immediately discard because of no education?
Eh, I don't have a degree. My own strategy? I just apply until I find a place where that isn't a hard requirement.
I personally don't mention my education at all. Let them assume what they like. I mean, if they ask, I'll tell them, (they ask like 20% of the time, and it has never been a problem at that phase, as far as I can tell. At least once, the interviewer acted super surprised and I got the job.)
Note, a lot of places claim to "require" degrees. Treat that requirement like any other "requirement" on the job description; in my experience, you need something like 3 out of 5 of the requirements to get a chance at an interview; the degree is just one more I've gotta make up for, no different than not knowing Java.
>Networking and meetups won’t get you passed HR filters and corporate requirements.
This hasn't been my experience. Someone on the inside with pull has a lot more influence than HR, in my experience. It's very rare that we technical people approve a person and HR blocks them; the only cases I know the details of in my own experience have to do with serious (and obvious) lies turned up by the background check.
I mean, certainly, there are jobs that will bin my resume right off... and I'm sure there are some jobs that will bin my resume even with a good internal recommendation, (I could tell stories there, but they all have to do with trying to get work outside of the USA.) but my experience is that most places? A good internal advocate is worth a thousand pieces of paper from the university.
The other thing to keep in mind is that a technician who misleads is about as useful as a salesperson who can't deceive without crossing that line in the way that good salespeople can. A lot of the startup advice is fine if you are management-track, but if you are looking for individual contributor work, being honest and straightforward in ways that don't really work when you are management/sales is the order of the day. I've seen a lot of technicians fired for lying about a screwup (or because management thought they lied about a screwup) - I haven't seen many technicians get fired for actually screwing up.
Eh, I don't have a degree. My own strategy? I just apply until I find a place where that isn't a hard requirement.
I personally don't mention my education at all. Let them assume what they like. I mean, if they ask, I'll tell them, (they ask like 20% of the time, and it has never been a problem at that phase, as far as I can tell. At least once, the interviewer acted super surprised and I got the job.)
Note, a lot of places claim to "require" degrees. Treat that requirement like any other "requirement" on the job description; in my experience, you need something like 3 out of 5 of the requirements to get a chance at an interview; the degree is just one more I've gotta make up for, no different than not knowing Java.
>Networking and meetups won’t get you passed HR filters and corporate requirements.
This hasn't been my experience. Someone on the inside with pull has a lot more influence than HR, in my experience. It's very rare that we technical people approve a person and HR blocks them; the only cases I know the details of in my own experience have to do with serious (and obvious) lies turned up by the background check.
I mean, certainly, there are jobs that will bin my resume right off... and I'm sure there are some jobs that will bin my resume even with a good internal recommendation, (I could tell stories there, but they all have to do with trying to get work outside of the USA.) but my experience is that most places? A good internal advocate is worth a thousand pieces of paper from the university.
The other thing to keep in mind is that a technician who misleads is about as useful as a salesperson who can't deceive without crossing that line in the way that good salespeople can. A lot of the startup advice is fine if you are management-track, but if you are looking for individual contributor work, being honest and straightforward in ways that don't really work when you are management/sales is the order of the day. I've seen a lot of technicians fired for lying about a screwup (or because management thought they lied about a screwup) - I haven't seen many technicians get fired for actually screwing up.