3 ms·
I did mean FAANG companies, yeah. At the same time I feel what s/he's saying is also right; in fact I am slowly building up repos on github while I work on my m
by devilmoon 8y ago
I did mean FAANG companies, yeah. At the same time I feel what s/he's saying is also right; in fact I am slowly building up repos on github while I work on my masters and hopefully I'll start contributing to librabries I use so that I can show all of that off to potential employers.
I also feel like having a website in your name works wonders, but I am not too sure companies are really interested in that.
- kamarg 8y agoI can't speak for the "big names" but as someone who has done tech hiring for multiple SMBs, having a website that shows off your abilities absolutely makes a difference. I don't care if you hand coded the website or it's a bunch of articles on Medium. Showing that you know what you're talking about and can explain it well in English (or the company's language of choice), puts you at the top of my list of people I want to bring in to talk to. It's also likely to make me skip the stupid first steps that most companies take to filter out candidates that have no business applying like fizzbuzz tests when I'm talking to you.
- devilmoon 8y agoThanks for your input, I definitely want to set it up asap so that I can start blogging about stuff I'm interested in or ramblings I want to go on about after tackling some of the bigger assignments.
- kamarg 8y agoAs a follow up to this I wanted to give some additional thoughts on how to make your site more valuable for getting hired as a software dev at the kind of SMBs that I've worked for. 1) Keep your personal items separate from your technical. If I'm looking to hire you to do something technical I really don't care about your kids t-ball game, the latest recipe you made, or pretty much anything that doesn't have to do with technology. Non-software related tech is fine as long as it's not most of the content. 2) There needs to be more than just code in your software related posts. If the post is 90% code I have no way to know if you actually know what it does or if you wrote it. 3) Provide links to working demos of the concepts if possible. Public repos with instructions for setting up and running it are almost as good. 4) Please no videocasts. Text is so much easier to consume and scan through. I'm not going to watch a bunch of 30min videos of you explaining a concept. I will read an in-depth article from beginning to end. 5) If you have side projects you work on in your spare time, please make it a prominent part of your site. Even more than in-depth articles, this is what shows me you can build working software which is the single most important thing I care about when hiring to fill software positions. Just a few items that might help you out depending on what sort of company you're looking to land a job with.