4 ms·
FWIW, as a hiring manager, if someone has a portfolio I definitely judge them on it, and if it's good it allows me to bypass huge swaths of technical/coding int
by chucky_z 6y ago
FWIW, as a hiring manager, if someone has a portfolio I definitely judge them on it, and if it's good it allows me to bypass huge swaths of technical/coding interview stuff and dig much deeper into where/what I want. I always take it as a positive, even if it's old stuff.
- RangerScience 6y agoWhat do you find makes a portfolio better or worse for these purposes? Not so much "more likely to get them the job", more... I felt like my projects weren't actually suitable to take the place of coding interviews, largely because I couldn't actually drop in and work on them in the way that coding interviews show me actually doing work.
- chucky_z 6y agoLiterally anything. If I see someone with a lot of relevant forked repos, even if they're old, I take that as interest and something I can bring up. If I see a repo of rcfiles I know they care about working efficiently. If I see abandoned stuff with more than 1 commit that's OK, that's something that was cared about at one point. These are just two super generic examples. Almost everything is a positive. The only thing I don't like to see is repos with 1 commit, and nothing other than a README with the repo title in it. Not really negative, more of a 'cmon gimme more.'