Your Hebrew CV

Your Hebrew CV: When You Need One, and How to Get It Right

A badly translated Hebrew CV is worse than a clean English one. That's the counterintuitive thing most olim don't expect: a clumsy Hebrew document doesn't hide a weak grasp of the language — it advertises it, on the one page where you were trying to look polished. So before you spend a shekel on translation, the first question isn't "is my Hebrew good enough?" It's "who reads this CV, and in what language do they actually work?"

Get that question right and the rest of this is straightforward.

Do you even need one?

It depends entirely on the roles you're targeting, and the Israeli market splits fairly cleanly down the middle.

A strong English CV is usually fine for international tech companies, startups aiming at global markets, multinationals, academic and research roles at international institutions, and anything advertised as an "English-speaking environment." A chunk of Israel's economy — the part most olim from English-speaking countries gravitate to — runs in English, and a clean English CV is exactly right there.

A Hebrew CV is what gets you read most everywhere else: local companies without English-speaking management, customer-facing and healthcare roles, government and the public sector, traditional industries like construction, retail and local manufacturing, smaller and family businesses — and anywhere the posting itself asks for one.

The practical strategy that follows: target English-speaking roles while your Hebrew builds, and add a Hebrew CV as those other doors open. You don't need to solve the whole language question on day one.

Who should do the translating

Roughly in order of cost and reliability:

A professional service (Morfix Translation Services, One Hour Translation, a local agency) runs around ₪200–600 and gives you accurate terminology and native-level phrasing — worth it for senior or important applications where the Hebrew genuinely matters. A vetted freelancer on Fiverr or Upwork (₪150–400) can be excellent value for mid-range needs; check reviews, ask for samples, and confirm they know professional CV language and your industry's terms. A bilingual friend or colleague is fine for a first draft — but treat it as a draft to be reviewed, not the final article.

And AI — Google Translate, DeepL, ChatGPT — is a first-draft tool, full stop. It's genuinely useful for getting words on the page, but it routinely produces awkward phrasing and the wrong terminology in Hebrew. Never submit AI output without a native speaker's review. A clean English CV beats a clumsy Hebrew one every single time.

Right-to-left: rebuild, don't flip

This is where most home-made Hebrew CVs fall apart. Hebrew reads right-to-left, and that changes how the whole document is constructed — you can't just mirror your English layout and call it done. A flipped English CV reads wrong to an Israeli eye in a way that's hard to articulate but instantly noticeable.

Build it properly instead: use a Hebrew-enabled processor (Word with Hebrew support, or Google Docs), set the document language to Hebrew so the software handles the RTL flow, and restructure rather than translate-in-place. Hebrew text is right-aligned and sections read right to left, but numbers and dates can run left-to-right within the Hebrew, and English terms — company names, technologies, acronyms — stay in English (left-to-right) embedded inside it. Export to .docx or .pdf to lock the layout, then open the PDF on more than one device before you send it, because RTL rendering is exactly the thing that breaks silently between machines.

If you want both languages

Some applications benefit from having Hebrew and English ready — but package them as two separate one-page documents, not a single two-page bilingual CV trying to be both at once. The clean pair reads as professional; the mashed-together version reads as cluttered. Keep them perfectly consistent — identical dates, titles and achievements across both — and submit both when the posting itself appears in both languages. A small touch that works well: note in the header, in Hebrew, "English CV available on request" (or the reverse).

The mistakes that give you away

A few patterns separate a fluent-sounding CV from an obviously-translated one:

• Don't translate literally. "Responsible for" (אחראי על) often lands better as "managed" (ניהל) or "led" (הוביל), depending on context. Word-for-word translation of English phrasing sounds stiff in Hebrew.

• Keep tech terms in English. This is the one that surprises people: Israelis in tech use the English terms. Translating "machine learning" into Hebrew on a CV looks odder than leaving it alone. Python, JavaScript, AWS and the like all stay in English even on a Hebrew CV — translate the verbs and the achievements around the tooling, not the tooling itself.

• Use standard business vocabulary. "Human Resources," for instance, is משאבי אנוש (Mashabei Enosh) — use the term the industry actually uses, not a coined one.

• Mind the seams. Where English words sit inside Hebrew, watch the spacing and punctuation around them. Sloppy mixing is a tell.

• Add context for untranslatable titles. Some English job titles have no clean Hebrew equivalent — a short explanation in parentheses solves it.

The single fastest way to natural terminology isn't a dictionary — it's reading a dozen real Hebrew job postings for roles like yours and borrowing the exact words they use. That shows you how your industry actually talks, which no dictionary can.

A few finishing touches that read as fluent: keep sentences shorter than you would in English (Hebrew professional writing is more concise), use the Israeli date format (day.month.year), write modern Israeli Hebrew rather than anything biblical or overly formal, and have at least two native speakers — ideally one in your field — review the whole thing.

Your name

Worth a moment's thought if you're here long-term, though there's no single right answer. You can use a Hebrew version where one exists (Michael → מיכאל, Daniel → דניאל), adopt one that sounds close to your original, or keep your original name entirely if there's no good equivalent — all are perfectly accepted.

The safe, friendly default is to show both: "Jonathan (Yonatan) Smith." It gives an Israeli reader something easy to say while keeping the name your references and credentials sit under. You lose nothing and gain a little warmth.

The cover letter

Half a page, one page at most, and personalised. Israeli business culture is direct and informal — even in writing — so heavy formality reads as stiff. A simple five-part structure works: open by stating the role and where you saw it; give two or three qualifications that match the posting; show you've researched the company with a specific product, value or recent piece of news; mention your connection to Israel if it's relevant; and close with genuine enthusiasm and your availability to interview. Warm, direct and concise is the register — the same directness you'll meet in the interview itself.

The honest rule of thumb

The whole game is matching the language to the role and making sure whatever you send reads as fluent. So if your Hebrew isn't yet strong enough to judge a translation's quality, do one of two things: pay for a professional translation you can trust, or focus on English-speaking roles until your Hebrew catches up. Don't send something you can't vouch for.

If you'd like help deciding whether a particular role needs a Hebrew CV, finding a reliable translator, or sanity-checking the terminology in your field, that's exactly what Olim Advice is here for — free, for every oleh.