Portfolio & career guides

Most hiring teams now use some form of AI or ATS screening before a human ever sees your resume. Here's what these systems actually check for, and how software engineers can pass them without gaming them.

Most portfolio case study advice is written for designers. Here's a template built specifically for software engineers, with the sections recruiters and hiring managers actually read.

Recruiters glance at the green squares, but the contribution graph measures activity, not skill — and a growing number of developers are gaming it. Here's what to show instead.

You don't need all three to be perfect, but you do need to know what each one is actually for. Here's how GitHub, a portfolio, and LinkedIn work together in a technical recruiter's process.

Resumes are easier to fake than ever. Here's what 'proof of work' means for software engineers, why recruiters are asking for it, and how to show yours in minutes.

'Improved performance' says nothing. Here's a formula and real before/after examples for quantifying impact on a software engineer resume, plus what to do when you genuinely don't have exact numbers.

You don't need to scaffold a site, set up a deploy pipeline, or maintain hosting to have a credible developer portfolio. Here are the real options, and when each one makes sense.

A practical checklist of what actually belongs in a software engineer's portfolio in 2026 — and what to leave out, so recruiters can evaluate you in under two minutes.