A Chat Window Cannot Hand You a Resume Template
Ask a chat assistant for a resume template and what comes back is text: section labels, some square-bracket placeholders, maybe a row of dashes pretending to be a rule. That is not a template in the sense you meant. A template is a file with margins, fonts, spacing and a column structure, and a chat window has none of those things to give you. Treating the text sketch as a template is the mistake, and it costs you twice — once in formatting, and once in what you end up writing.
What actually comes back
The output has a recognisable shape. A name line in brackets. Contact details in brackets. Headings called Professional Summary, Professional Experience, Skills, Education. Under each role, three or four bullets that begin with a strong verb and contain a bracketed number: [X]% improvement, team of [Y].
Read that as what it is — a description of a conventional resume, written out longhand. It is a reasonable description. It is not a document, and the two differences that matter are invisible in the chat window:
There is no layout. No page size, no margins, no leading, no decision about whether dates sit right-aligned or after the employer name. Everything you can see on screen is the chat interface’s styling, not yours. Paste it into a document and it inherits whatever that document was set to.
There is no file. The formatting question — what a reader opens, what survives text extraction, what happens on a phone screen — is a property of the file you produce at the end, and nothing about it has been decided yet. Any claim that a text sketch is machine-friendly is empty, because being readable by software is a property of the finished document rather than the layout you started from.
The placeholder trap
The real damage is not formatting. It is that bracketed placeholders convert writing into form-filling.
Once [X]% improvement is on your screen, you have been handed a slot, and slots demand to be filled. The honest response to that slot is often “nothing, I never measured it” — but the slot does not offer that option, and the path of least resistance is to estimate. An estimate typed into a bracket looks exactly like a fact once the brackets come off, and you will not remember six weeks later which numbers you measured and which you approximated to complete a template. That is the mechanism by which a resume acquires figures its owner cannot source, and it is why every number on the page needs to be a claim you can actually back up.
The same applies to the structure. A template with a Professional Summary heading implies you need one; a template with a five-item skills row implies you have five worth listing. Neither is true of everybody, and you should decide those things about your own history rather than inheriting them from a sketch.
Two decisions, and the order to make them in
The word “template” gets used for two separate things, and asking a chatbot conflates them.
The content skeleton — which sections exist, in what order, and what goes in each. This is a genuine question with a fairly stable answer, and a chat assistant can describe the convention for you in one exchange. It is worth an exchange precisely because it is a five-minute question, not a design project.
The visual document — the file, the type, the spacing, the grid. This is done in a word processor or a layout tool, on the text you have already written.
Make them in that order and each is easy. Reverse the order — pick the look first, then write into it — and you get a document that is the shape of a template with your history compressed to fit. The compression is where the specifics go: the bullet that needed twenty-two words gets cut to eighteen because the box was that big.
What to write first instead
Open a plain text file. Write your roles with real dates and titles. Under each, write what you were responsible for and the specific things you did, in complete, ugly sentences. Do not think about length, order, or which of it is impressive. This is the same record of your own work that every other AI-assisted step depends on, and it is the input a template cannot supply.
Then, and only then, make formatting decisions on real content. You will find most of them answer themselves: you know how many roles you have, so you know whether one page is plausible; you know which role matters, so you know what belongs at the top.
What a chat assistant is honestly good for here
Three things, all small and all worth having.
Naming a section you forgot. Certifications, publications, languages, licences — depending on your field, one of these may belong on the page and not have occurred to you. Asking what sections are conventional for a particular kind of role is a fair question with a useful answer.
Telling you what a reader would expect to find and cannot. Paste your written-out content and ask what is missing that a reader would look for. This is the inverse of asking for a template, and it is much more useful, because it responds to your document rather than to an average one.
Turning your ugly sentences into bullets. With the strict instruction that it may not add anything — no numbers, no scope, no outcome you did not write. That is a real service, and it is a writing task, not a formatting one.
What it cannot do, and should not be asked
It cannot see your file. It cannot tell you whether your PDF converts cleanly to plain text, whether your two-column layout reads in the right order once extracted, or whether the font renders on someone else’s machine. Those are checks you run yourself by exporting, opening the export, and reading it.
And it cannot tell you what any particular employer prefers. Screening setups differ, reviewers differ, and nobody outside an organisation knows how it processes what arrives. Advice that names a preference confidently is guessing. The available strategy is the boring one: say true things in plain words, put them where a reader looks, keep the structure simple enough that both a person and a text extractor can follow it, and check the exported file yourself before you send it — the mechanics of which are covered in what a template can honestly do for a document’s readability.