It says a little bit more than this.
I do a bit of recruitment myself, and when a solid portfolio is attached to the CV, it tells me that the applicant is motivated and that he's not only here because he saw some lights in, you know.
The downside is that your code must be clean. It's not a criteria, but I always go do some digging in random class of the projects, and if I don't like what I see I might ask you some related questions.
Also, on your portfolio, don't be stingy about context. Explain in a few words why you did it, and what the project is meant to do
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It says a little bit more than this.
I do a bit of recruitment myself, and when a solid portfolio is attached to the CV, it tells me that the applicant is motivated and that he's not only here because he saw some lights in, you know.
The downside is that your code must be clean. It's not a criteria, but I always go do some digging in random class of the projects, and if I don't like what I see I might ask you some related questions.
Also, on your portfolio, don't be stingy about context. Explain in a few words why you did it, and what the project is meant to do