A letter assembled from what you actually did
Four blocks, in the order a reader goes through them. Every sentence is one you wrote — the tool orders them, counts them, and tells you which requirements your own words support.
A letter assembled from what you actually did
Four blocks, in the order a reader goes through them. Every sentence in the letter is one you wrote — the tool orders them, counts them, and tells you which of the job's requirements your own words support.
What the export actually contains
One column, no header, no footer, no text box, no table. Those four constructs cause most of the extraction failures a cover letter can have, and this cannot emit them.
After the Word file is written it is read back and compared with what went in, block by block. If anything failed to come out, or came out in the wrong order, you are told before you send it rather than after.
The PDF is drawn with pdf-lib, loaded from a public code CDN the first time you export one. Nothing about you is sent with that request.
The letter is not a summary of the resume
The reader has the resume. What a letter adds is the part that does not fit on one: why this role, what you would do with it, and anything about your situation that is better said than guessed at.
A letter that restates the resume in prose is worse than no letter, because it costs the reader time and tells them nothing.
Name the role and point at a line
Recruiters handling six openings look for the title. And "I read the posting" is proved by quoting something from it, not by asserting enthusiasm.
Adjectives about yourself are unverifiable
Passionate, detail-oriented, hard-working, a team player — anyone can type these, so a reader discounts all of them. Replace each with the thing you did that makes it true. If nothing comes to mind, that is worth knowing.
Say the awkward thing plainly
A gap, a redundancy, a career change, a move: stating it in one sentence removes it as a question. Leaving it out does not — it just means somebody else decides what it means.