You do not need a new CV for every job
Keep one honest master CV. For each application, move two experiences up. Do not rebuild the document from scratch.

Rewriting the CV from scratch for every posting turns the search into a night shift. After three versions the dates slip, an old title is still in there, and the core story has been sanded off so each file can look “tailored.”
Have one master document. What you change per application should be a thin slice of it.
What the master CV is for
The master is the honest record of the work. No invented metrics. No “excellent communication.” What you ran, what you shipped, at what scale, in which years.
Photo, home address, and marital status still show up in Turkish templates. Drop them from the master if you are applying internationally. If a local corporate role wants that format, make a separate copy. Do not contaminate the source. English and Turkish masters are normal. A third language per posting is not.
Length: at 3–8 years, two pages is plenty, one page can be enough, three pages rarely adds a fact. The test is whether each bullet claims something, not how far the file scrolls.
File names are part of the job. CV_final_FINAL_v7.pdf tells neither you nor them anything. name-surname-backend.pdf is enough. Keep the tailored copy as name-surname-backend-company.pdf. Do not overwrite the master. Uploading the wrong PDF at midnight wipes the twenty minutes you just spent.
What you actually move
After you read the posting, ask: which two experiences do I put first for this role?
It is often not the current job. A project from three years ago, or an internal tool that looked like a side quest. Pulling that next to the top role is not a rewrite. It is order, verbs, one number.
If the posting is about APIs and external integrations, “did various backend work” does nothing. The line with a service name, a volume, and an integration stays; the rest shortens. If they want some team direction, the mentoring sentence moves up and pure execution moves down.
Do not:
- Add a tool you did not use because it is in the req
- Paste the posting’s phrases in order
- Tell the same job under three titles
Lies get interviews. Interviews take them apart. Keyword stuffing for an ATS is the same door: a parser might pass, a person will not.
How much tailoring is enough
Put a clock on it. If a CV pass takes more than 20 minutes, either the role is not a fit or the master is a mess. If it is a mess, fix the master on one evening. If it is not a fit, do not apply.
Cover letters are unread in a lot of engineering processes. Where they are read, four sentences will do: why this team, which two proofs, whether location and working pattern even work. Not a biography.
The “paste your CV” box on application forms will wreck the PDF care you just took. Upload the PDF when you can. If a form is mandatory, paste from the master. Do not write literature into that box.
What JobInbox does with a CV
JobInbox reads the CV to fill a profile: role, stack, experience, location preferences. That is not the same as rewriting the document for every job. Matching narrows discovery toward the story you already have. Which two bullets to promote is still the application’s job.
A CV is a sales doc. It is not a discovery tool. Keep those jobs apart and the night shift gets shorter.