I want to get into a company like Intel or NVidia.
Any tips? My resume links to my website where a full resume is posted with all my bullshit on it.
I posted on /sci/ but as someone pointed out there, you guys more than likely have a better understanding of the hiring process.
I'll keep it simple - that resume isn't much use without seeing the job description you're applying for. It might get you an interview for a niche job at Intel for one posting, but it might go straight to the trash for another job posting.
The person (or computer) doing the initial screening is someone in HR who probably doesn't know a whole lot about the technical side, so think - what would they want to see, and can they understand your writing (or at least, the significance of it)?
not enough sadly.
the only way to get a job at a huge meme company like that is to know someone or be exceptionally qualified.
you had two internships but apparently didn't do much. you shouldn't need to list the courses you took to fill up your resume. they're looking for a succinct summary of your practical, industry experience in a resume; courses/focus is something you mention at the interview.
you can still try to get in through networking. i got an offer with an even more underwhelming resume at Cisco.
Those courses are on standby depending on the position. The point I'm making with those is demonstrating tangible results with a quantified success factor.
After all I am a recent grad, they can't expect me to have an overwhelming work history.
I feel like you should put more emphasis on the "System Integration Specialist". The other bullshit just seems like filler talking points, and overall it looks weak. All it says is "i have a little experience and went to school".
And a lot is dependent on your schools rank, the size of the company you worked for, and your GPA.
>MBA right after undergrad
you should have lots of experience though.
you really shouldn't have rushed the masters man, it's useless without experience. jobs that require masters will be more technical and therefore require more from you in terms of experience. you could go for an entry level positions that bachelors qualify for, but you'd be overqualified and probably underpaid.
and you also shouldn't have interned at the same place repeatedly unless you planned on taking a position there. the point if internships is to test the water in different fields and get a breadth of experience.
>you really shouldn't have rushed the masters man, it's useless without experience. jobs that require masters will be more technical and therefore require more from you in terms of experience. you could go for an entry level positions that bachelors qualify for, but you'd be overqualified and probably underpaid.
That is part of my plan. I'm going to be doing the Masters and taking semesters off to get more work term. It has a course component that I can be flexible with.
Put it this way. Right now I'm applying for everything I can. If you were a hiring manager someone who is undergoing a Masters and actively seeking to better his education looks a lot more attractive than someone who has been job hunting for 6 months.
It's a mix of a fall back and something that I want to do.
No debt. My work terms covered tuition.
whoa sorry man didn't see the "current", i assumed you'd finished it.
forget everything I said then, you're doing great.
since you're still in school, your resume looks good enough. again, make sure to get more diverse internships next summer.
you should also make sure to use your professors. most engineering professors have lots of industry connections, and a lot of big tech companies have " university relations " staff at universities to scope out the fresh talent. i know Intel had a huge presence when i was studying. networking is just as crucial in tech as it is for finance or any other job.
1) Get rid of the objective -it's too generic
2) Bullet point out list of skills at the top- if I didn't read carefully through the resume how would I know that you know the ELK stack?
3)Your internships should be like 80% of the experience space (flesh them out). Putting down class projects really won't get you anywhere with a recruiter. You can speak to it when you talk with them over the phone but it doesn't go in your resume.
4) Make sure that you are listing accomplishments rather than responsibilities in your experience: that's what will set you apart to a recruiter
5)References go in a separate sheet that you only give if asked. It's considered amateurish to put your references into the resume body these days (don't ask me why.)
Honestly, you have a lot of crap on there that most won't care about. For someone like you, I'd immediately go to their Git and see what their code is ACTUALLY like, not go by some grades or anything. The resume is a good intro, but if you don't have a git for a position like that, most won't even look at you.
Silicon Valley employee here.
its the individual and collective projects that you've been a part of that the employers (meme-tier) really care about. Its an old standard that is still prevalent because there isn't really a new platform of displaying employable skills (programming skills) accumulatively.
I have plenty of stuff I've made in my spare time, I just don't post it on Git because I don't really care about releasing it/ not obsessed with open source stuff. Is this really that big of a deal?