4 ms·
When I first graduated (with a BSEE from some shitty local uni), the only CS project I had on my resume was some ML research I published as an undergrad. I did
by Frotag 4y ago
When I first graduated (with a BSEE from some shitty local uni), the only CS project I had on my resume was some ML research I published as an undergrad. I did do a lot of hobby projects in Python / some JS, but nothing was presentable in the slightest.
When applying for jobs in a medium-sized but not-very-techy-city, I found the hardest part to be just getting an interview offer. But the interview itself usually ranged from braindead easy to a straightforward take-home exam. So I guess the takeaway is to fluff up your resume and accomplishments as much as possible. It turns out to be much easier to impress someone in an interview than with your resume. And at least for entry-level positions, you aren't really grilled on trivia for whatever you list, maybe just a general "how-does-it-work" question.
Sadly I didn't realize this until my second go-around with job-hunting. The first time I only really got responses for intern positions (was applying for both frontend / backend / fullstack). Luckily I was offered a full-time frontend position after interviewing for an internship and crushing the take-home exam.