First, what the system actually does with your CV
When you apply through a job portal or a company career site in Poland — Pracuj.pl, eRecruiter, Workday, Teamtailor — your CV is usually read by software before a person opens it. The applicant tracking system (ATS) parses your file into a structured record: name, contact details, employers, job titles, dates, skills, education.
Recruiters then work from that record, not from your carefully designed page. They search it ("SQL", "prawo jazdy kat. B", "English B2"), filter it by dates, and skim the extracted summary. The original file is still attached — but the parsed version decides whether you appear in a search at all.
You may have read that ATSs auto-reject most CVs. In practice, formatting rarely gets you rejected outright. What happens instead is quieter and worse: a section fails to parse, a date is misread, a skill never lands in the record — and you become harder to find, with no error message anywhere. An ATS-friendly CV is not about beating a robot. It is about making sure nothing is silently lost between your file and the record a human reads.
Here are the seven formatting rules that consistently survive parsing — and why.
1. One column, top to bottom
Parsers extract text in reading order, which for most layouts means straight down the page. A two-column design — skills in a left sidebar, experience on the right — often comes out interleaved: skill names spliced into job descriptions, dates separated from the roles they belong to.
A single column cannot be scrambled. It is also perfectly readable for humans, which is the point.
2. Real text, not graphics
Anything drawn rather than typed is invisible to a parser: text inside images, skill bars, icons standing in for words, logos. A skill shown as four-dots-out-of-five parses as nothing at all.
Quick test: open your exported PDF, select all, copy, and paste into a plain text editor. Whatever didn't survive the paste, the ATS won't see either.
3. Standard section headings
Parsers locate sections by matching heading keywords: "Work experience", "Education", "Skills" — or their Polish equivalents ("Doświadczenie zawodowe", "Wykształcenie", "Umiejętności"). A creative heading like "My journey so far" matches nothing, and everything under it can land in the wrong bucket or in none.
Save the personality for your summary and your bullet points. Keep headings boring.
4. Contact details in the body, not the page header
Word and many design tools place your name and email in the document header or footer. Some parsers skip header and footer regions entirely — which can produce a perfectly parsed CV with no email address attached to it.
Put your name, phone, email, city, and LinkedIn in the body of the first page, as normal text.
5. One date format, used everywhere
Your employment timeline is reconstructed from date ranges. Mixed formats — "03.2022" here, "March 2022" there, a bare "2022" somewhere else — make ranges harder to pair up, and a mispaired range can read as a gap or an overlap that isn't there.
Pick one format — "03.2022 – 06.2024" or "Mar 2022 – Jun 2024" — and use it for every role and every diploma. Write "present" (or "obecnie") for a current role, not a dash.
6. No tables, text boxes, or manual columns
Tables and text boxes are the classic parser breakers: content is extracted cell by cell or box by box, in an order you don't control. The same goes for columns faked with tabs or spaces. If you want visual alignment, let the template's typography do it — the underlying text should still read correctly top to bottom.
7. Export a text-based PDF
PDF keeps your layout identical everywhere, and modern parsers handle text-based PDFs well. Two caveats: if the job ad explicitly asks for DOCX, send DOCX. And never send a scanned or photographed document — a scan is one big image, and rule 2 applies in full.
Should a Polish CV have a photo?
A photo is still common on Polish CVs and still expected in some industries — but it is not required, and an employer cannot demand one. From the parser's side, a photo is at best ignored and at worst the anchor of a layout that breaks rule 1. If you're applying through an ATS-heavy pipeline — large companies, job portals — a CV without a photo loses nothing and risks less. If you keep one, place it so that removing it wouldn't change the text layout.
Do you still need the RODO clause?
A shorter one than you think. Under the current Polish rules, submitting your application is itself enough for the employer to process your data for that specific recruitment — the long consent paragraph copied from decade-old templates is not needed for it. A consent line only matters if you want to be considered for future recruitments. Many Polish recruiters still expect to see something, and one short line costs you nothing:
"Wyrażam zgodę na przetwarzanie moich danych osobowych zawartych w aplikacji na potrzeby przyszłych procesów rekrutacyjnych."
One line, at the bottom, small type. That's all.
Polish or English?
Match the language of the job ad. Keyword search happens in the language the recruiter types, and that follows the ad and the company's working language. Ad in Polish — CV in Polish. Ad in English, even from a Polish company — CV in English. If a listing is bilingual, choose the language of the team you'd join, and stay consistent: one language per document, not a mix section by section.
Pre-submit checklist
- Select-all copy test passed: text pastes out complete and in order
- One column; no tables, text boxes, or graphics carrying information
- Contact details in the body text, not the page header or footer
- Standard section headings
- One date format everywhere; current role marked "present" / "obecnie"
- CV language matches the ad's language
- Wording from the ad used where it is honestly true of you
- Photo decision made deliberately; RODO line short — or absent if you don't need it
- A file name you'd be happy to see in an inbox: name-surname-cv.pdf
Every template in NobelCV is single-column and text-based by design, so what you write is exactly what gets parsed. Build your CV free or import an existing PDF — no account needed to start, and exporting the finished file is a one-time €12, with no subscription attached.