Senior devs spot red flags in junior portfolios in seconds, but we (almost) never explain them.
After reviewing hundreds (thousands?) of junior developer portfolios, I realized two things:
Junior devs do their best but don’t know the red flags senior developers spot immediately
Nobody tells them
So I built https://yourlead.dev to automate myself : it analyzes GitHub repositories and:
- flags the issues a lead developer would raise during a real code review
- explains why they matter
- gives concrete tips on how to fix them
- and even helps prepare for technical interviews
I spent a lot of time fine-tuning it based on my experience across different contexts (because expectations are very different in an early startup, a scale-up, or a bank).
btw, I'm giving free reviews in exchange for feedback ;)
Well, we sorely need something better than the current static code analysis tools, like sub-par products SonarQube and CodeQL that see massive overuse, because these tools do not understand that living and evolving code needs imperfections and that _most_ programmers have already thought through their code and made decisions that can't align with poor text book examples of "correct code".
I have been in software engineering for more than 13 years, have interviewed and hired many people in that time…
Never once did I look at any portfolio. Actually, no one had any they wanted to show!
After screening the CV, they got a 1 hour first round for cultural fit and technical foundations, a simple take home exercise (e.g. build a service that sends emails), in the second round they had to go through their code and justify their choices and in the second part the had to code review the bad submission of a former applicant and in the third part they had to draw up how they‘d extend and embed that service in a microservice landscape.
2 rounds. Never had a „mishire“. Hiring is that easy.
ok, I updated a few things. thanks for your feedback :
- a clear link in the landing to claim for a free review
- add that it's useful to review portfolio but also take home assignments and side projects.
6 comments
[ 3.0 ms ] story [ 17.0 ms ] threadAfter reviewing hundreds (thousands?) of junior developer portfolios, I realized two things:
Junior devs do their best but don’t know the red flags senior developers spot immediately Nobody tells them
So I built https://yourlead.dev to automate myself : it analyzes GitHub repositories and: - flags the issues a lead developer would raise during a real code review - explains why they matter - gives concrete tips on how to fix them - and even helps prepare for technical interviews
I spent a lot of time fine-tuning it based on my experience across different contexts (because expectations are very different in an early startup, a scale-up, or a bank).
btw, I'm giving free reviews in exchange for feedback ;)
Never once did I look at any portfolio. Actually, no one had any they wanted to show!
After screening the CV, they got a 1 hour first round for cultural fit and technical foundations, a simple take home exercise (e.g. build a service that sends emails), in the second round they had to go through their code and justify their choices and in the second part the had to code review the bad submission of a former applicant and in the third part they had to draw up how they‘d extend and embed that service in a microservice landscape.
2 rounds. Never had a „mishire“. Hiring is that easy.