3 ms·

I have recently begun searching for software development jobs as a self-taught programmer. So I too would love to gain some insight on where to look not only fo

I have recently begun searching for software development jobs as a self-taught programmer. So I too would love to gain some insight on where to look not only for a job, but also for advice on the application process (e.g. my resume and personal website).

nicoburns 4y ago
Do you have any decently complex open source projects that you can show off to potential employers? If you do you’ll likely not have any trouble finding a job.
- longjmp 4y ago
  Thank you for the kind words. I suppose my answer depends on our definitions of decently complex. My primary two projects are a multi-user painting program via the internet, and what is effectively a network KVM switch, sans video.
  - fn-mote 4y ago
    > I suppose my answer depends on our definitions of decently complex. Write them up like you believe they are important. Put the code on your GitHub. Advertise. Get pics of the KVM up and write something like a blog post about it. Remember - your competition doesn't have the self-motivation to be creative like this.
jacob_rezi 4y ago
https://www.rezi.ai/rezi-ai-resume-editor https://www.rezi.ai/rezi-ai-resume-editor
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.

nicoburns 4y ago

Do you have any decently complex open source projects that you can show off to potential employers? If you do you’ll likely not have any trouble finding a job.

longjmp 4y ago
Thank you for the kind words. I suppose my answer depends on our definitions of decently complex. My primary two projects are a multi-user painting program via the internet, and what is effectively a network KVM switch, sans video.
- fn-mote 4y ago
  > I suppose my answer depends on our definitions of decently complex. Write them up like you believe they are important. Put the code on your GitHub. Advertise. Get pics of the KVM up and write something like a blog post about it. Remember - your competition doesn't have the self-motivation to be creative like this.

jacob_rezi 4y ago

https://www.rezi.ai/rezi-ai-resume-editor https://www.rezi.ai/rezi-ai-resume-editor

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.