A resume, not a form
Talk about it.
Get the resume.
Resumical writes your resume with you, from what you say about your work, never from a template. Then it checks the PDF the way a recruiter's software will, before it calls it done.
- Never invents a fact — every date, title and number is yours, and it asks when one is missing.
- Read the way an ATS reads it — the text is pulled back out of the PDF, in order, before you see "done".
- The look is yours — colour, type, a photo where the market expects one. Single column, real text.
How it works
From a sentence to a PDF you can send
One conversation, end to end. It writes, you push back, it writes again.
Say what you're going for
Drop your old resume, or a photo of it, or nothing at all. Paste the posting, or link it. Then talk about your work.
It writes, and asks
It writes the page from the facts you've given it. When one is missing, it asks you. It never fills the gap.
It checks before it says done
The real PDF is rendered, read the way a tracking system reads it, and looked at. Done is refused until it passes.
The resume is two files, resume.htmlandresume.css, rendered to a PDF. That is why it can be checked, kept in versions, and changed by pointing at a line.
Who it's for
Anyone with a job to apply for
You need an email address and something to say about your work. That is the whole setup.
Applying now
Tailor to each posting in a sentence, not an afternoon. Every fact stays true; the emphasis moves.
Changing fields
Say what you actually did. It finds the lines that carry over, and says them in the new field's words.
Applying abroad
The form they read there, on the paper they use there, in the language you'll be read in.
The checks
Checked like code, because it is code
A resume that a tracking system cannot read is rejected before anyone sees it. So the checks run the same operation a recruiter's software does, and the agent is not allowed to say done while one fails.
Every write
Broken markup is never saved
A file that does not parse is not written. The error goes back to the agent, which fixes it and writes again.
The page
It fits its target
One page, two, or no limit at all. The target is yours to set. Over is a failure, and nothing is cut off at the edge.
The text layer
It reads in order
The text is extracted from the PDF the way an applicant tracking system extracts it. Every heading, every line, in reading order, or it fails.
A second look
Someone looks at the page
A vision pass judges the printed page for what is broken, a cramped masthead, a heading stranded at the foot. Never for what is dated.
The extracted text is also a panel you can read yourself: what a tracking system will see, word for word.
Two rules
The resume is your livelihood
So it holds itself to two rules, and only two. Everything else is yours to decide.
Rule one
Never invent a fact.
Dates, titles, employers and numbers come from what you have told it. It may rewrite how a fact is said, which is the job. It may never change what a fact claims. You have to defend every line of this in an interview.
Rule two
Never ship what cannot be read.
One column, real text, within the page target. A beautiful resume that a tracking system parses as garbage has failed, so it is never allowed out.
Those are the only rules. Colour, type, a rule under the masthead, a tinted heading, a photo — a navy heading extracts the same as a black one, so none of it is ours to forbid. Restraint is the default when you have said nothing. It is never a decree.
Whose form it is
A resume is not one thing
What goes on it, what it is called, whether it carries a photo, a birth date, a signature: all of that is set by where you are applying. Resumical writes the form that is read there, on the paper used there, and asks for what that form needs before it writes.
A one-page resume
United States, Canada
A CV with a photo and a birth date
Germany, much of Europe
A rirekisho, in its fixed form
Japan
An academic CV with no page limit
Universities, medicine, research
Paper
Set from where you are applying. The PDF, the preview and the page count follow it.
Scripts the faces cover
The typefaces are embedded in the renderer, so what you see is what prints, and a name in another script is set in a face that has it.
What you can hand it
Attach anything, and say what it is for
The file type does not know what you want. Your sentence does, and the agent reads the attachment with your sentence beside it.
Your old resume
A PDF, or a photo of one. The facts come out of it, into your own words, and get saved so you never type them again.
A page whose look you like
The design is fair to borrow. The facts on it are not yours, and it knows the difference.
The posting
Pasted or linked. It shapes what leads and what gets cut. It is never saved as a fact about you.
The console
Built to be argued with
The first draft is rarely the one you send. The workspace is made for the second, the fifth, and the one you come back to tomorrow.
Point at a line
Click a line in the preview and say "cut this". It knows which line you mean.
Say more while it works
The box stays open. A word said mid-run is heard before the next step, not after the run.
Watch it think
The reasoning streams as it happens. A long think looks like a think, not a hang.
Live, and the PDF
A live preview as it types, and the PDF you will actually send. Only the PDF gets to say done.
Every version kept
A version on every finish. Say "the way it was" and it goes back. A restore is checked like any change.
Close the tab
The run keeps going on the server. Open it tomorrow and it is where you left it.
What are you going for?
Drop your old resume, or start from nothing. Say the job. Read what comes back.
An email address is all it takes. Nothing to install.