Interviews, Not Jobs

A resume is an invitation, not a biography

A resume is a short, scannable summary whose single job is to convince a reviewer that talking to you is worth their time. It is not a complete record of everything you have done, and it does not need to win the job on its own; the interviews do that. A portfolio (GitHub profile, project repositories, a personal site) supports the resume with evidence a reviewer can inspect: code, READMEs, live demos and write-ups. Keeping this purpose in mind makes many decisions easier: include what makes a reviewer want to ask you more, cut what does not, and never claim anything you could not comfortably discuss in an interview.

Documents that earn a conversation

A resume and portfolio exist to get you an interview; the interview is where you get the job.

What each piece does

A quick map of the job-search documents.

Document            Main job                                  Typical reader time
------------------  ----------------------------------------  ---------------------
Resume              Earn a first conversation                 A quick scan, then a closer read if promising
GitHub profile      Show real code and how you work            Opened from a resume link
Project README      Explain one project and prove it runs      Read by curious reviewers and interviewers
LinkedIn            Be findable; confirm the resume story      Searched and skimmed
Personal site       Optional home for projects and writing     Visited by interested readers

Rule: everything on these pages should be true and explainable in an interview.

A movie trailer

A resume is a trailer, not the film: it shows the best real scenes so the viewer wants to watch the whole thing, and it must not show scenes that are not in the movie.

Quick check: What is the main job of a software engineering resume?

• To replace the interview process
• To list every task you have ever done
• To earn an interview by showing you are worth talking to
• To include as many keywords as possible