Great article! I give a lot of the same advice to early career folks. The thing I struggle with them is how to help capture their confidence and expertise to really own it through the interview process. Perhaps it's just a skill that comes with practice and time?
I think a bit of practice and a bit of needing to believe it themselves. It helps to have an external source of validation that what they have accomplished is meaningful. With the abundance of Imposter Syndrome in this field, it's no surprise that those who have trouble getting hired experience it the most. I think if more employed developers speak out to how relatable their experiences were when starting out, it can really boost the confidence of some newer developers. I tried to cover this at least surface-level in this article when I stated, "You did not 'make a small website for a friend.' You 'exceeded a customer’s expectations by delivering an accessibility-compliant single-page-application and maintain it through an Issues tracker and a CI/CD pipeline.'"
Owning my accomplishments was something I personally struggled with, primarily due to the sheer number of companies who rejected me outright, saying that I could not possibly be good enough for the position without a degree. I began believing it and saw my accomplishments as close to worthless.
I am very passionate about helping others surpass this barrier, and I look forward to completing my planned subsequent articles and gathering more feedback such as yours. While I know the hurdles that I personally faced, it is great feedback to hear what others are going through so that their experiences are not ignored or left out of coverage.
Thanks for such a thorough response. I agree with how you describe your projects in the interviews really drives home your "hireability".
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.