|
|
|
|
|
by rinchik
2654 days ago
|
|
When interviewing devs, I always check GH profile. If its empty it's usually a read flag (meaning that I will have to do more work during the interview). Coding samples, contributions graph, personal projects can push a candidate forward very fast. Worth to note: GitHub itself does NOT matter, the contents your profile and you contributions do. Prefer GitLab? awesome! Just don't forget to put it in your resume. |
|
Isn’t that your job as a hiring manager? Also how do you know that their github projects actually work in production? Do you do a through code analysis to evaluate performance bottlenecks or do you do a build-deploy-test do figure that out? IMO if you want to evaluate candidates on complete end to end projects you should give them assignments based your your evaluation parameters and ask them to explain their code/solution