That distinction matters, because it changes what you’re actually optimising for. You’re not trying to trick a robot. You’re making sure the robot can read what’s already true about you.<\/p>\n\n\n\n
What an ATS-Friendly CV Actually Means<\/strong><\/h2>\n\n\n\nAt its core, being ATS-friendly means your CV parses the way you intended it to \u2014 the software extracts your name as your name, your job titles as job titles, and your skills as skills, in the right order, attached to the right dates.<\/p>\n\n\n\n
Most modern applicant tracking systems are genuinely decent at this for straightforward layouts. The problem isn’t that ATS software is dumb \u2014 it’s that a lot of \u201ccreative\u201d CV formatting was never designed with parsing in mind, because it was designed to look good to a human eye first.<\/p>\n\n\n\n
According to Jobscan’s research on ATS formatting<\/a>, which draws on a survey of hundreds of recruiters, the vast majority of recruiters now use some form of ATS to manage applications \u2014 which is exactly why this is worth thirty minutes of your time rather than something to panic about.<\/p>\n\n\n\nThe layout choices that actually cause problems<\/strong><\/h2>\n\n\n\nThis is the part most advice gets vague on, so here’s what specifically trips up parsing, based on how these systems are built to read a document from top to bottom, left to right:<\/p>\n\n\n\n
Multi-column layouts.<\/strong> If your CV has two columns \u2014 say, a skills sidebar next to your main experience \u2014 an ATS often reads straight across the page rather than down one column at a time. Line one of your left column gets glued to line one of your right column. Your neat two-column design becomes a garbled sentence in the system’s database.<\/p>\n\n\n\nText boxes.<\/strong> Many parsers skip content inside text boxes and floating design elements entirely \u2014 which is a real problem if your name or contact details live inside one, because that’s exactly where CVs commonly put them for visual effect.<\/p>\n\n\n\nHeaders and footers.<\/strong> The same applies here: content placed in a document header or footer (again, often contact information) is frequently invisible to the parser, even though it’s the first thing a human eye sees.<\/p>\n\n\n\nIcons instead of text.<\/strong> A little phone icon next to your number looks clean. To an ATS, it’s often just an image \u2014 the number next to it is fine, but if your section headings (\u201cSkills,\u201d \u201cExperience\u201d) are represented as icons or graphics rather than actual text, the system may not recognise them as headings at all.<\/p>\n\n\n\nUnusual fonts.<\/strong> If a font isn’t standard or properly embedded, parsers can substitute the wrong characters for it \u2014 turning readable text into garbled symbols.<\/p>\n\n\n\nTables used for layout.<\/strong> Tables built to visually organise a CV (rather than genuinely tabular data) tend to confuse reading order the same way columns do.<\/p>\n\n\n\nInconsistent date formats.<\/strong> Dates like \u201cJan ’21\u2013Mar ’23\u201d can trip up systems trying to calculate your total experience automatically. Full, consistent formats (e.g. \u201cJanuary 2021 \u2013 March 2023\u201d) parse far more reliably.<\/p>\n\n\n\nThe image below shows the practical difference: the same information, laid out two ways, and what actually reaches the ATS database in each case.<\/p>\n\n\n\n![\"Diagram](\"https:\/\/cvprowrite.co.uk\/blog\/wp-content\/uploads\/2026\/09\/image.jpg\")
<\/figure>\n\n\n\nHow to check if your own CV is ATS-friendly<\/strong><\/h2>\n\n\n\nYou don’t need special software for the first pass \u2014 a few honest checks will tell you most of what you need to know.<\/p>\n\n\n\n
1. The copy-paste test.<\/strong> Select all the text in your CV and paste it into a plain text editor (Notepad, TextEdit, or even a blank email). If your section headings, job titles, and dates still appear in a sensible order \u2014 great sign. If everything runs together in a jumbled block, that’s roughly what an ATS is seeing too.<\/p>\n\n\n\n2. Check where your contact details actually live.<\/strong> Open your CV and check: is your name and phone number typed directly into the body of the document, or sitting inside a header, footer, or a separate text box or design element? If it’s the latter, move it into the main body.<\/p>\n\n\n\n3. Count your columns.<\/strong> If your CV uses a sidebar or multi-column layout for anything beyond a simple footer, consider whether that content would survive being read straight across the page rather than down each column.<\/p>\n\n\n\n4. Look for icon-only headings.<\/strong> If \u201cSkills\u201d or \u201cExperience\u201d appears only as a small graphic rather than as typed text, add the word itself alongside it, even in a small font.<\/p>\n\n\n\n5. Save it as a text-based PDF (not a scanned image), or a plain .docx.<\/strong> Both are generally safe formats, provided the layout inside follows the rules above \u2014 the file type matters far less than what’s actually inside it.<\/p>\n\n\n\nIf you’d rather not run these checks yourself, this is exactly the kind of thing we build in from the start when writing a CV \u2014 every CV we produce is checked against parsing behaviour before a client ever sees the final draft, alongside the human judgement of what actually reads well to a hiring manager. You can see how that process works on our CV writing services page (\/cv-writing-services<\/a>), or, if you already have a CV and just want the formatting reviewed and cleaned up, our CV formatting service (\/cv-formatting-services<\/a>) is built specifically for that.<\/p>\n\n\n\nThe quick checklist<\/strong><\/h2>\n\n\n\n\u2610 Single-column layout (or a sidebar limited to non-essential content)<\/p>\n\n\n\n
\u2610 Name, phone number, and email typed directly in the body \u2014 not in a header, footer, or text box<\/p>\n\n\n\n
\u2610 Section headings are real text, not icons or images<\/p>\n\n\n\n
\u2610 Standard font (Arial, Calibri, Georgia \u2014 nothing decorative)<\/p>\n\n\n\n
\u2610 Dates written in full and consistently<\/p>\n\n\n\n
\u2610 Saved as a text-based PDF or .docx, not a scanned image<\/p>\n\n\n\n
\u2610 Passed the copy-paste test above<\/p>\n\n\n\n
A few honest FAQs<\/strong><\/h2>\n\n\n\nDoes a \u201cpretty\u201d CV design always fail ATS checks?<\/strong><\/p>\n\n\n\nNot necessarily \u2014 plenty of well-designed CVs use a single-column layout with tasteful use of colour and typography, and parse just fine. It’s specifically columns, text boxes, headers\/footers, and icon-only labels that cause the real problems, not visual polish itself.<\/p>\n\n\n\n
Will an ATS auto-reject me if my formatting is imperfect?<\/strong><\/p>\n\n\n\nUsually not automatically. What typically happens is your information is captured incompletely or in the wrong fields \u2014 which means a recruiter searching their database later may not find you, even though you were a genuinely strong match. The damage is usually invisible rather than dramatic.<\/p>\n\n\n\n
Should I use the exact keywords from the job description?<\/strong><\/p>\n\n\n\nWhere they’re honestly true of your experience, yes \u2014 both for search-ability in the ATS and because it’s simply good practice to mirror the language of the role you’re applying for. It’s not a trick; it’s making sure your real experience is described in the same terms the recruiter is searching for.<\/p>\n\n\n\n
If you want a second pair of eyes on your current CV \u2014 formatting, keywords, and the actual writing \u2014 our team has been doing exactly this for over 15 years and 6,000+ CVs a year. Take a look at our CV writing packages (\/packages<\/a>) to see where to start.<\/p>\n","protected":false},"excerpt":{"rendered":"If you’ve been job hunting for more than a week, you’ve heard it: “make sure you have an ATS-friendly CV, or a…<\/p>\n","protected":false},"author":1,"featured_media":93,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-67","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cv-writing-tips"],"_links":{"self":[{"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/posts\/67","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/comments?post=67"}],"version-history":[{"count":3,"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/posts\/67\/revisions"}],"predecessor-version":[{"id":94,"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/posts\/67\/revisions\/94"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/media\/93"}],"wp:attachment":[{"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/media?parent=67"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/categories?post=67"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/tags?post=67"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
The layout choices that actually cause problems<\/strong><\/h2>\n\n\n\nThis is the part most advice gets vague on, so here’s what specifically trips up parsing, based on how these systems are built to read a document from top to bottom, left to right:<\/p>\n\n\n\n
Multi-column layouts.<\/strong> If your CV has two columns \u2014 say, a skills sidebar next to your main experience \u2014 an ATS often reads straight across the page rather than down one column at a time. Line one of your left column gets glued to line one of your right column. Your neat two-column design becomes a garbled sentence in the system’s database.<\/p>\n\n\n\nText boxes.<\/strong> Many parsers skip content inside text boxes and floating design elements entirely \u2014 which is a real problem if your name or contact details live inside one, because that’s exactly where CVs commonly put them for visual effect.<\/p>\n\n\n\nHeaders and footers.<\/strong> The same applies here: content placed in a document header or footer (again, often contact information) is frequently invisible to the parser, even though it’s the first thing a human eye sees.<\/p>\n\n\n\nIcons instead of text.<\/strong> A little phone icon next to your number looks clean. To an ATS, it’s often just an image \u2014 the number next to it is fine, but if your section headings (\u201cSkills,\u201d \u201cExperience\u201d) are represented as icons or graphics rather than actual text, the system may not recognise them as headings at all.<\/p>\n\n\n\nUnusual fonts.<\/strong> If a font isn’t standard or properly embedded, parsers can substitute the wrong characters for it \u2014 turning readable text into garbled symbols.<\/p>\n\n\n\nTables used for layout.<\/strong> Tables built to visually organise a CV (rather than genuinely tabular data) tend to confuse reading order the same way columns do.<\/p>\n\n\n\nInconsistent date formats.<\/strong> Dates like \u201cJan ’21\u2013Mar ’23\u201d can trip up systems trying to calculate your total experience automatically. Full, consistent formats (e.g. \u201cJanuary 2021 \u2013 March 2023\u201d) parse far more reliably.<\/p>\n\n\n\nThe image below shows the practical difference: the same information, laid out two ways, and what actually reaches the ATS database in each case.<\/p>\n\n\n\n<\/figure>\n\n\n\nHow to check if your own CV is ATS-friendly<\/strong><\/h2>\n\n\n\nYou don’t need special software for the first pass \u2014 a few honest checks will tell you most of what you need to know.<\/p>\n\n\n\n
1. The copy-paste test.<\/strong> Select all the text in your CV and paste it into a plain text editor (Notepad, TextEdit, or even a blank email). If your section headings, job titles, and dates still appear in a sensible order \u2014 great sign. If everything runs together in a jumbled block, that’s roughly what an ATS is seeing too.<\/p>\n\n\n\n2. Check where your contact details actually live.<\/strong> Open your CV and check: is your name and phone number typed directly into the body of the document, or sitting inside a header, footer, or a separate text box or design element? If it’s the latter, move it into the main body.<\/p>\n\n\n\n3. Count your columns.<\/strong> If your CV uses a sidebar or multi-column layout for anything beyond a simple footer, consider whether that content would survive being read straight across the page rather than down each column.<\/p>\n\n\n\n4. Look for icon-only headings.<\/strong> If \u201cSkills\u201d or \u201cExperience\u201d appears only as a small graphic rather than as typed text, add the word itself alongside it, even in a small font.<\/p>\n\n\n\n5. Save it as a text-based PDF (not a scanned image), or a plain .docx.<\/strong> Both are generally safe formats, provided the layout inside follows the rules above \u2014 the file type matters far less than what’s actually inside it.<\/p>\n\n\n\nIf you’d rather not run these checks yourself, this is exactly the kind of thing we build in from the start when writing a CV \u2014 every CV we produce is checked against parsing behaviour before a client ever sees the final draft, alongside the human judgement of what actually reads well to a hiring manager. You can see how that process works on our CV writing services page (\/cv-writing-services<\/a>), or, if you already have a CV and just want the formatting reviewed and cleaned up, our CV formatting service (\/cv-formatting-services<\/a>) is built specifically for that.<\/p>\n\n\n\nThe quick checklist<\/strong><\/h2>\n\n\n\n\u2610 Single-column layout (or a sidebar limited to non-essential content)<\/p>\n\n\n\n
\u2610 Name, phone number, and email typed directly in the body \u2014 not in a header, footer, or text box<\/p>\n\n\n\n
\u2610 Section headings are real text, not icons or images<\/p>\n\n\n\n
\u2610 Standard font (Arial, Calibri, Georgia \u2014 nothing decorative)<\/p>\n\n\n\n
\u2610 Dates written in full and consistently<\/p>\n\n\n\n
\u2610 Saved as a text-based PDF or .docx, not a scanned image<\/p>\n\n\n\n
\u2610 Passed the copy-paste test above<\/p>\n\n\n\n
A few honest FAQs<\/strong><\/h2>\n\n\n\nDoes a \u201cpretty\u201d CV design always fail ATS checks?<\/strong><\/p>\n\n\n\nNot necessarily \u2014 plenty of well-designed CVs use a single-column layout with tasteful use of colour and typography, and parse just fine. It’s specifically columns, text boxes, headers\/footers, and icon-only labels that cause the real problems, not visual polish itself.<\/p>\n\n\n\n
Will an ATS auto-reject me if my formatting is imperfect?<\/strong><\/p>\n\n\n\nUsually not automatically. What typically happens is your information is captured incompletely or in the wrong fields \u2014 which means a recruiter searching their database later may not find you, even though you were a genuinely strong match. The damage is usually invisible rather than dramatic.<\/p>\n\n\n\n
Should I use the exact keywords from the job description?<\/strong><\/p>\n\n\n\nWhere they’re honestly true of your experience, yes \u2014 both for search-ability in the ATS and because it’s simply good practice to mirror the language of the role you’re applying for. It’s not a trick; it’s making sure your real experience is described in the same terms the recruiter is searching for.<\/p>\n\n\n\n
If you want a second pair of eyes on your current CV \u2014 formatting, keywords, and the actual writing \u2014 our team has been doing exactly this for over 15 years and 6,000+ CVs a year. Take a look at our CV writing packages (\/packages<\/a>) to see where to start.<\/p>\n","protected":false},"excerpt":{"rendered":"If you’ve been job hunting for more than a week, you’ve heard it: “make sure you have an ATS-friendly CV, or a…<\/p>\n","protected":false},"author":1,"featured_media":93,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-67","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cv-writing-tips"],"_links":{"self":[{"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/posts\/67","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/comments?post=67"}],"version-history":[{"count":3,"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/posts\/67\/revisions"}],"predecessor-version":[{"id":94,"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/posts\/67\/revisions\/94"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/media\/93"}],"wp:attachment":[{"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/media?parent=67"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/categories?post=67"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/tags?post=67"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
Text boxes.<\/strong> Many parsers skip content inside text boxes and floating design elements entirely \u2014 which is a real problem if your name or contact details live inside one, because that’s exactly where CVs commonly put them for visual effect.<\/p>\n\n\n\n Headers and footers.<\/strong> The same applies here: content placed in a document header or footer (again, often contact information) is frequently invisible to the parser, even though it’s the first thing a human eye sees.<\/p>\n\n\n\n Icons instead of text.<\/strong> A little phone icon next to your number looks clean. To an ATS, it’s often just an image \u2014 the number next to it is fine, but if your section headings (\u201cSkills,\u201d \u201cExperience\u201d) are represented as icons or graphics rather than actual text, the system may not recognise them as headings at all.<\/p>\n\n\n\n Unusual fonts.<\/strong> If a font isn’t standard or properly embedded, parsers can substitute the wrong characters for it \u2014 turning readable text into garbled symbols.<\/p>\n\n\n\n Tables used for layout.<\/strong> Tables built to visually organise a CV (rather than genuinely tabular data) tend to confuse reading order the same way columns do.<\/p>\n\n\n\n Inconsistent date formats.<\/strong> Dates like \u201cJan ’21\u2013Mar ’23\u201d can trip up systems trying to calculate your total experience automatically. Full, consistent formats (e.g. \u201cJanuary 2021 \u2013 March 2023\u201d) parse far more reliably.<\/p>\n\n\n\n The image below shows the practical difference: the same information, laid out two ways, and what actually reaches the ATS database in each case.<\/p>\n\n\n\n You don’t need special software for the first pass \u2014 a few honest checks will tell you most of what you need to know.<\/p>\n\n\n\n 1. The copy-paste test.<\/strong> Select all the text in your CV and paste it into a plain text editor (Notepad, TextEdit, or even a blank email). If your section headings, job titles, and dates still appear in a sensible order \u2014 great sign. If everything runs together in a jumbled block, that’s roughly what an ATS is seeing too.<\/p>\n\n\n\n 2. Check where your contact details actually live.<\/strong> Open your CV and check: is your name and phone number typed directly into the body of the document, or sitting inside a header, footer, or a separate text box or design element? If it’s the latter, move it into the main body.<\/p>\n\n\n\n 3. Count your columns.<\/strong> If your CV uses a sidebar or multi-column layout for anything beyond a simple footer, consider whether that content would survive being read straight across the page rather than down each column.<\/p>\n\n\n\n 4. Look for icon-only headings.<\/strong> If \u201cSkills\u201d or \u201cExperience\u201d appears only as a small graphic rather than as typed text, add the word itself alongside it, even in a small font.<\/p>\n\n\n\n 5. Save it as a text-based PDF (not a scanned image), or a plain .docx.<\/strong> Both are generally safe formats, provided the layout inside follows the rules above \u2014 the file type matters far less than what’s actually inside it.<\/p>\n\n\n\n If you’d rather not run these checks yourself, this is exactly the kind of thing we build in from the start when writing a CV \u2014 every CV we produce is checked against parsing behaviour before a client ever sees the final draft, alongside the human judgement of what actually reads well to a hiring manager. You can see how that process works on our CV writing services page (\/cv-writing-services<\/a>), or, if you already have a CV and just want the formatting reviewed and cleaned up, our CV formatting service (\/cv-formatting-services<\/a>) is built specifically for that.<\/p>\n\n\n\n \u2610 Single-column layout (or a sidebar limited to non-essential content)<\/p>\n\n\n\n \u2610 Name, phone number, and email typed directly in the body \u2014 not in a header, footer, or text box<\/p>\n\n\n\n \u2610 Section headings are real text, not icons or images<\/p>\n\n\n\n \u2610 Standard font (Arial, Calibri, Georgia \u2014 nothing decorative)<\/p>\n\n\n\n \u2610 Dates written in full and consistently<\/p>\n\n\n\n \u2610 Saved as a text-based PDF or .docx, not a scanned image<\/p>\n\n\n\n \u2610 Passed the copy-paste test above<\/p>\n\n\n\n Does a \u201cpretty\u201d CV design always fail ATS checks?<\/strong><\/p>\n\n\n\n Not necessarily \u2014 plenty of well-designed CVs use a single-column layout with tasteful use of colour and typography, and parse just fine. It’s specifically columns, text boxes, headers\/footers, and icon-only labels that cause the real problems, not visual polish itself.<\/p>\n\n\n\n Will an ATS auto-reject me if my formatting is imperfect?<\/strong><\/p>\n\n\n\n Usually not automatically. What typically happens is your information is captured incompletely or in the wrong fields \u2014 which means a recruiter searching their database later may not find you, even though you were a genuinely strong match. The damage is usually invisible rather than dramatic.<\/p>\n\n\n\n Should I use the exact keywords from the job description?<\/strong><\/p>\n\n\n\n Where they’re honestly true of your experience, yes \u2014 both for search-ability in the ATS and because it’s simply good practice to mirror the language of the role you’re applying for. It’s not a trick; it’s making sure your real experience is described in the same terms the recruiter is searching for.<\/p>\n\n\n\n If you want a second pair of eyes on your current CV \u2014 formatting, keywords, and the actual writing \u2014 our team has been doing exactly this for over 15 years and 6,000+ CVs a year. Take a look at our CV writing packages (\/packages<\/a>) to see where to start.<\/p>\n","protected":false},"excerpt":{"rendered":" If you’ve been job hunting for more than a week, you’ve heard it: “make sure you have an ATS-friendly CV, or a…<\/p>\n","protected":false},"author":1,"featured_media":93,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-67","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cv-writing-tips"],"_links":{"self":[{"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/posts\/67","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/comments?post=67"}],"version-history":[{"count":3,"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/posts\/67\/revisions"}],"predecessor-version":[{"id":94,"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/posts\/67\/revisions\/94"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/media\/93"}],"wp:attachment":[{"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/media?parent=67"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/categories?post=67"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cvprowrite.co.uk\/blog\/wp-json\/wp\/v2\/tags?post=67"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}<\/figure>\n\n\n\nHow to check if your own CV is ATS-friendly<\/strong><\/h2>\n\n\n\n
The quick checklist<\/strong><\/h2>\n\n\n\n
A few honest FAQs<\/strong><\/h2>\n\n\n\n