3 ms·
Any SWE should already have a professional portfolio ready to share with employers. Even an entry-level coder should have some class projects and hobbies to sho
by NoZebra120vClip 3y ago
Any SWE should already have a professional portfolio ready to share with employers. Even an entry-level coder should have some class projects and hobbies to show at that point.
If you don't go around with a portfolio, then yeah, you can expect employers to be skeptical, and subject you to coding on the whiteboard, or leetcode or something, which isn't really going to reflect your actual coding ability, but it's more geared toward weeding out fakers in interviews.
On the other hand, if you have a portfolio, especially a public one shared on GitHub or such, then you can directly point to it and take credit for a good, hopefully working project, and you can explain it at length, and your prospective employer should hopefully take this as a strong signal that your skills are commensurate with your CV.
- josephg 3y agoIf you run an opensource project on github, it’s remarkable how many times your repository will be forked into weird github accounts - that on closer inspection are just big lists of forked projects with nary an original patch to be found. I have no idea why people do this; but I suspect it might be to look good in interviews. No idea if it works - it’s pretty obvious if you look closer that they didn’t author any of the commits. But I wonder how many people are out there claiming credit for other people’s work to get hired.
- sokoloff 3y agoI do a fair amount of that in my own github account. If I have no commits in a forked repo, it was probably just a form of "bookmarking".
- StreetChief 3y agoYou can also fork to preserve a repo, although apparently GitHub can removed forked repos alongside the original during takedown action. (To avoid, do the fork manually).
- mvdtnz 3y agoI've spent my entire career behind the firewall. No I don't have a portfolio I can show you.