Over the last couple of years, I was privileged to work with many juniors. I have mentored, helped, hired, fired, consulted, read CVs, advised frie...
For further actions, you may consider blocking this person and/or reporting abuse
Great post! I loved it. I have a question regarding the recommendation of donating your time as a junior developer to open sources. Is it something that catches an eye of a recruiter or a team leader or just a myth? Also do you recommend to put a list of significant projects with some explanations in the CV or just refer to the general GitHub account?
I like this post, too, since I am looking for a junior role right now.
Regarding you question about a list of significant projects in the CV: I have made my CV as a single HTML file and hosted on GitHub pages. So, I can easily share the link, plus, updates I make after sharing the link are still propagated.
I decided to include a detailed list of my projects to make them stand out.
I've noticed that interviewers look at my CV during the interview as a reference to ask questions and discuss my experience. So, I'd definitely make projects stand out somehow. 👍
Here's the link to my CV
christiankozalla.github.io/CV
Thanks @christiankozalla !
I really like your CV and the fact that you made it as a github-pages gives you more points, imho.
Asking questions about past experience (the projects that a candidate worked on, even if they are personal projects) is a great way to understand the experience of that candidate, how much "copy&paste" they did and how well they actually understand what they are doing.
Good like finding your next job!
nice cv
I really like the online CV. It's very clean and pleasant to look at. Also has some great information on there. I might have been inspired to make one for myself! :)
Awesome! Glad to hear you like it 😀
It helps you stand out for sure. It shows that you can work inside a codebase that isn't your own. It also shows that you have a grasp of how to contribute code, one of the first things I have to teach Jr's out of college is how to use Git, Github and the PR process.
Thanks @mayaliberman1 !
Definitely something that a good recruiter will take into consideration, however keep in mind that it's the candidate's responsibility to make sure this information is emphasized enough.
If there is only a link to the github account - no one can promise that the recruiter will actually check it/understand that it's important. I would suggest the candidate to emphasize the fact that they contribute to open-source project - for example, add a link to the issues/prs that they contributed.
And most importantly, be honest about your skills. Don't put every single language and technology on your CV just because you tried it out. Even though interviews for Junior positions aren't that rough, the Senior Engineers interviewing you will find out.
I completely agree with you here!
Hi,
@dekel
I'm a Business student but trying hard to become a web-developer...It would be much helpfull if you suggest me if i should build a portfolio now or should i concentrat on Learning for now?
my github link...github.com/coder-mahfuz
these are just some THE ODINE PROJECT assignments
thanks
You should definitely focus on learning, however building a portfolio can be part of it. Take the time to build your own portfolio, and you can show there what you know.
thanks a lot dekel
Excellent article!!! And the conclusion was straight to the point .. I had not found an answer of which one was the one .. :) Now I know that it goes beyond proving to be the best, but learning how to guide us ...
Any tips on hiring juniors? Do you think I missed some tips on how to make sure you stand-out? Please share. I would love to hear it!
Hiring juniors can work really well if a team has strong mentors among their seniors.
Strong mentors can help and provide good guidance to juniors, and if some junior ask me for an advice to decide between two companies, usually I'm trying to understand which company will provide a better mentoring and guidance.
Great post.
beautifully written.
Good summary! 👍
Thank you @mgiannopoulos !
Great advice, thanks for sharing!
Thanks @codecustard !
If you have some tips or things you would like to read more about - please share :-)
Thank you Denkel😉 It very helpful for me. And I was wandering, is that good way to show on GitHub all your history of learning, or it’s better to save just a most amazing project?
You can share the history. There are multiple ways to do this - either with one repository or multiple and have one with links (in
README.md) to the others.a great read 🙂
Thanks @rishitkhandelwal ! Appreciate your reply here.
Awesome. This will surely help me stand out!
Thanks @timocmd2 !
Thank you for this post.
Well written.
Thanks @oryam !
Loved it!!
Thanks @saimhafeez20 ! Appreciate your help reply.
Nice post! Very helpful for both juniors and seniors
Thanks @buntyrathod !
Great points!
oh hi