Prices shown are a USD base. Your local-market price is calculated at checkout in your own currency, plus any local sales tax.
What is inside
20 chapters, in the order the interviews tend to ask them:
The application artefact set and what each document is for
Page count, the one page rule and when to break it
Section order and section naming for a technical role
The achievement bullet and the formula that survives an interview
Quantifying impact honestly and what to write when you have no metric
The skills section, ATS keywords and the line against stuffing
Employment history, date formats and explaining a gap
The education section and what a degree does for a technical hire
Projects, portfolio and reading a GitHub profile as evidence
The academic CV and how it differs structurally
The US one page, the UK two page, the German Lebenslauf and Europass
Applicant tracking systems, parsing failures and screening decisions
PDF versus Word and accessible document structure
The cover letter as a paired artefact
The LinkedIn profile as a drafting base and its limits
References: requesting them and what to put on the page
The header block and the personal details to leave out
One master document and several tailored variants
Version control, export, file naming and sending
Getting a resume read honestly rather than politely
How the answers are built
Each chapter opens with the checklist the question is really testing. A few from this pack:
Each document in the packet answers a different question, and a document that answers no question the reader asked is just weight in an attachment list.
The one page convention exists because a first reader spends a fixed and short amount of time, so length only earns its place by raising the chance a relevant match is found.
Order sections by the sequence in which they resolve a reader's doubt, which for a technical hire is what you can do, where you did it, and how you are judged, not your date of birth.
The formula is context, action, result, in that order, and the most common failure is a bullet that supplies the action and none of the other two.
A number is worth writing only when you can state its source and period, because an unsourced figure is a claim you cannot defend.
List the things you could be asked about tomorrow, because a skill you cannot discuss for five minutes is a liability in a technical screen.
Questions this pack covers
Which documents does a single job application actually need?
What does a cover letter add that the resume cannot carry?
Where does the one page convention actually come from
How do you measure how much evidence fits on one page
What order should resume sections appear in for a technical hire?
Why does a summary section so often waste space?
What makes a resume bullet answerable under questioning?
How do you separate what you did from what the team did
Each one is answered in full in the pack, with the reasoning written out rather than a bullet list.
