{"id":391,"date":"2026-08-29T18:10:52","date_gmt":"2026-08-29T18:10:52","guid":{"rendered":"https:\/\/cvzilla.io\/blog\/?p=391"},"modified":"2026-08-29T18:10:52","modified_gmt":"2026-08-29T18:10:52","slug":"start-with-the-profile-how-to-optimize-a-cv-for-one-vacancy-in-cvzilla","status":"publish","type":"post","link":"https:\/\/cvzilla.io\/blog\/product-features\/start-with-the-profile-how-to-optimize-a-cv-for-one-vacancy-in-cvzilla\/","title":{"rendered":"From Profile to Tailored CV: How CVZilla Handles One Vacancy at a Time"},"content":{"rendered":"

If you already have a master profile in CVZilla, the next step is not to start improvising in a vacancy field like it\u2019s a blank napkin.<\/p>\n

The cleaner path is simpler: finish the profile, render the base CV, then start one tailoring run for one real vacancy. That order matters because the profile is the source record, and the tailored CV is the application-specific version built from it.<\/p>\n

This walkthrough follows the product the way it actually works, so you can see what to prepare, where the controls live, and how the final result stays tied to the original profile instead of drifting into wishful thinking.<\/p>\n

Finish the master profile first<\/h2>\n

The master record is the upstream source that feeds both the base CV and the tailoring workflow, so this is where the story starts. In CVZilla, the header fields include name, primary role, summary, contact details, and location, which gives the app enough structure to assemble a usable starting document. If you want to see that starting point in the interface, the Profile<\/a> area is the first stop.<\/p>\n

Experience-like sections add dated records, optional industry and country context, bullets, and AI-assisted bullet rewriting where shown. That matters because the profile is not just a storage box; it is the source material the rest of the workflow reads from.<\/p>\n

The useful rule is straightforward: keep the profile broad enough to hold your full background, but specific enough that each claim stands on its own. If a detail is only implied by a job title, it is still just implied. That is exactly why the profile exists before the vacancy does.<\/p>\n

\"The
The master Profile screen shows the source record and base CV preview before any tailoring begins<\/figcaption><\/figure>\n

Use the base CV preview as the baseline<\/h2>\n

Once the profile is in shape, CVZilla assembles the base CV from that current profile and lets you open the rendered preview. That is the first checkpoint where the source data becomes an actual CV view, instead of a pile of fields.<\/p>\n

This is also the right moment to compare the source record with the output. The profile remains editable in the background, while the preview shows what a recruiter would see if you stopped here and exported nothing else.<\/p>\n

A simple, self-contained layout helps more than a clever one. NIST advises readable, fully documented applications, and the ILO guidance favors clear ordering with more detail given to role-relevant experience. So the baseline should be easy to scan before any tailoring starts. A quick look now usually saves a longer sigh later.<\/p>\n

\"The
The optimization panel shows a live tailoring run with progress and step status visible<\/figcaption><\/figure>\n

Start tailoring from a real vacancy source<\/h2>\n

When you open Job Tailoring from a vacancy link or pasted description, CVZilla starts a run with supported vacancy input and builds a tailored result from the profile plus vacancy context. In practice, that means the vacancy becomes the organizing unit, not a random word cloud to chase.<\/p>\n

If you are deciding whether to use a link or paste the job text, the important thing is simply that the vacancy is real and specific. The product can start from supported input either way, but the reader should understand the role description is the brief the system is matching against.<\/p>\n\n