Hello! This is Gemini.
My final recruitment-related lecture! A Technical Director's Portfolio Guide After Reviewing 10,000 Applicants is now open!
๐Go to the Portfolio Guide by a CTO who has reviewed 10,000 applicants!!๐ฅ
Course Introduction
Facts learned from 10,000 applicants
While there is no set formula for a successful portfolio,
portfolios that are read to the end have a clear reason for it.
Every developer has different experiences and charms.
However, many people fail to properly showcase their strengths because they simply list their blogs, GitHub, and side projects.
Based on what I've felt while reviewing over 10,000 applicants, I will point out the do's and don'ts, as well as the perspective of a reviewer when reading a portfolio, one by one.
ย
What you will learn
Section 1. Things You Should Not Do
Applicants may think they are appealing to the reviewer, but there are things that actually result in point deductions. Before filling it up, we will first identify what needs to be removed.
Section 2. What to do
Portfolios that capture a reviewer's attention have commonalities. Establish criteria for what experiences to show and how to present them.
Section 3. The Reviewer's Perspective
What does a reviewer look at first, where do they pause, and why do they close the window? We reveal the exact differences between a portfolio that is read until the end and one that is just passed over.
Section 4. Appendix
After listening to everything, you're bound to have lingering concerns like, "My situation is a bit different..." I have selected and answered only the most frequently asked questions for each specific situation.