Your Hebrew CV, Readable by Every Israeli Screening System
We check the right-to-left file, the Hebrew and English keywords, and the structure that actually arrives on the recruiter's screen.
Why a perfectly good Hebrew CV comes out scrambled
Right-to-left text isn't stored as a picture of a page. It's stored as characters plus direction rules, and the software that opens your file has to rebuild the order. Export from an editor that doesn't embed Hebrew fonts, or build your layout from text boxes and tables, and the extractor can pull your letters out backwards, split words across lines, or skip whole sections. You never see it. The system does.
Then there's the bilingual problem. You work as a QA automation engineer and write the role in Hebrew, while the hiring manager searches the database for Selenium, Cypress and CI/CD. Or the opposite: an English-only CV lands with a local recruiter who filters on the Hebrew title. Both versions of a term deserve a place on the page, and there's a natural way to do it without your CV reading like a keyword dump.
The Israeli format itself is fine. One to two pages, no photo, no ID number, no date of birth: keep all of that. What usually needs work is the plumbing underneath. Contact details stranded in the page header get dropped. A two-column sidebar interleaves with the main text. Icons stand in for the word "Email". Clean that up and the same content suddenly parses.
Built for the Israeli stack
Three things a generic CV checker misses
The file, not just the words
We extract your CV the way a screening system would and show you the text that actually survives.
Hebrew and English, one keyword map
Your role is matched in both languages, so a title in one doesn't cost you the search in the other.
Local application forms in mind
Structured so employer systems prefill your name, title and experience correctly instead of leaving gaps.
What the analysis hands back
Right-to-left text that holds its order
See exactly where Hebrew lines reverse, break or vanish on extraction, and how to export so they don't.
Job titles written the way recruiters search
Your local title and its English equivalent, placed where both a human and a database will find them.
Tech terms kept in English on purpose
Frameworks, tools and certifications stay untranslated, because that's how they're typed into the search box.
Headings a parser can actually label
Experience, education, skills and military service mapped to sections the software recognises.
A fix list in order of damage
Start with what's costing you interviews this week, not a wall of forty suggestions.
Same content, two very different readings
| What gets read | A typical exported CV | After an HRLens cleanup |
|---|---|---|
| Hebrew body text | Letters arrive reversed, merged or missing | Extracts in the right order, line by line |
| Job title | Written one way, searched another | Local title plus the English equivalent |
| Layout | Two columns, text boxes, an icon sidebar | Single column with labelled sections |
| Contact details | Sitting in the page header, often skipped | First block in the body, plain text |
| Tech terms | Translated into Hebrew and invisible to search | Left in English exactly as recruiters type them |
| The file itself | A scan or an image export with no real text | A text PDF named with your name and the role |
Find out what the scanner sees before you apply again
Upload your CV and get the extracted text, a structure score and an ordered fix list in both languages.
Questions Israeli job seekers ask us
Should my CV be in Hebrew or English?
Apply in the language of the job ad. Hi-tech roles at international companies usually expect English, while the public sector, retail, healthcare and plenty of local firms read Hebrew first. Keep tool names, frameworks and certifications in English in both versions, since that's how recruiters search. Two clean versions beat one mixed file.
Why does my Hebrew PDF come out reversed when it's parsed?
Right-to-left text is stored as characters plus direction rules, not as a fixed image. If the PDF was exported without embedded Hebrew fonts, or the layout sits inside text boxes and tables, the extractor can rebuild the letters in the wrong order or drop them. Export from a tool that embeds fonts, stay in one column, then test the extraction.
Does an Israeli CV still need a photo?
No. The local convention is a clean one to two page document with no headshot, no ID number and no date of birth. A photo eats space, tells a recruiter nothing they can act on, and adds an image that some parsers treat as noise. Use the room for measurable results and the tools you work with.
How do I apply through Comeet, AllJobs or Drushim without losing formatting?
Send a single-column PDF with real, selectable text rather than a scan or an image export. These forms often re-read your file to prefill name, title and experience, so check every prefilled field before you submit and repair anything blank or garbled. Keep the filename plain: your name plus the role.
How should I handle mixed Hebrew and English job titles?
Write the title the employer used in the ad, then put the other language version next to it once, in brackets or in the first line of the role description. That covers both search paths without turning your CV into a keyword list. Company names, product names and technologies stay in their original form.
What exactly does HRLens check on a Hebrew CV?
It extracts your file the way a screening system would, so you can read the text that actually comes through. Then it scores structure, section headings, dates and contact details, matches role keywords in Hebrew and English, and returns an ordered fix list. The analysis is free and takes a few minutes.