Which repositories are worth listing, how to describe one in two lines, and what to fix in a repo before anyone opens it.
Three illustrative resumes — junior, mid-level and senior — with the reasoning behind each line, and the same project written three ways.
What a skills section is for, how to group it so it can be scanned, and why naming forty technologies says less than naming twelve.
What goes where experience would normally be, how to use coursework and projects honestly, and the claims that cost you credibility.