3 ms·
You need to do two important things: - Have projects you can list on your resume. There's no rule that says only jobs can be listed on a resume! - Have someon
by jey 16y ago
You need to do two important things:
- Have projects you can list on your resume. There's no rule that says only jobs can be listed on a resume!
- Have someone who works at the company submit your resume directly to the hiring manager or internal HR system. This is especially important for big companies, since they have armies of HR people who are completely non-technical but just scan the incoming flood of resumes based on simple filtering criteria like having a degree and the having the right buzzwords listed.
Also, apply to many jobs. Don't just spam listings where you clearly are unqualified, but just don't put your eggs all in one or a few baskets. You can also apply for jobs that don't exist if you think you have a skillset that fits a particular company and/or have an interest in their product.
FWIW, I quit college during my sophomore year and got several programming job offers using the above strategy.
- gamache 16y agoHave projects you can list on your resume. There's no rule that says only jobs can be listed on a resume! Seconded heartily. My resume's Projects section includes unpaid and paid creations. The Employment section then became mostly concerned with the roles and tasks I performed rather than the systems I created. Once I reorganized my resume in this way, the whole thing suddenly made much more sense. I think it really works for you to have the recruiter/employer see so clearly that you actually Make Shit.