Any resume, reformatted into your client's template.
Give it the candidate's PDF or DOCX and pick the client format. Every fact is copied as the candidate wrote it and placed into the client's own Word layout, with tables, bullets and fonts intact.
Verbatim facts
Employers, dates and bullets are copied, not rewritten. Checks refuse a document with leftover or unsupported content.
Exact client layout
The output is the client's own DOCX filled in, so two-column skill tables, bold labels and tab-aligned dates survive.
Fits the page limit
When a client caps pages, lower-priority lines are trimmed after render until the document fits. Summary and skills stay whole.
How it works
Same candidate, the client's template
A relayout, not a rewrite. The facts stay exactly as the candidate wrote them; only the presentation moves to your client's format.
- 1
The resume and the client format
Give it the candidate's resume and pick a published client format: a JSON fill spec paired with the client's own DOCX, tagged where content goes. File type and magic bytes are both checked before anything is parsed.
- 2
The format is checked before any AI runs
Every tag in the client DOCX must match a field in the spec, and every field must have a tag. A format that doesn't line up is refused at upload, not discovered in a broken document.
- 3
The resume fills the spec, word for word
Employers, dates, bullets and skills are copied from the resume into the spec's fields, following the client's fill rules. Nothing is summarised or invented.
- 4
The client's own DOCX is filled in
Loops clone the client's real rows and bullets, so fonts, tables, bold labels and tab-aligned dates are the client's own. Lines with no data disappear instead of leaving an empty label.
- 5
Page count and checks run
If the client caps pages, the lowest-priority lines are trimmed after render until it fits. Structural checks and leftover-tag checks run before the file is delivered.
What you get
- Client-styled DOCX
- Unchanged candidate facts