How to choose a CV builder if you are job hunting in Israel

The five things that matter

None of these are about how the CV looks. They are about whether the file that leaves the tool does what you need it to do.

• Right-to-left in the exported file, not just the editor. These are two different pieces of code, and the second one is where Hebrew tends to break.
• Whether the PDF contains real text. If it does not, applicant tracking systems read an empty document and you look like an empty application.
• Per-job tailoring. One CV sent to forty postings is the most common reason a strong candidate hears nothing back.
• Whether Hebrew and English stay connected. Most people here need both, and keeping two separate documents in sync by hand fails within a month.
• What the free tier actually does. Free until you press export is not free.

Hebrew in the export, not the editor

A tool can show your Hebrew perfectly while you type and still produce a broken PDF. The editor is a web page, and the browser handles bidirectional text on its behalf. The export is a separate rendering path, and it is frequently an afterthought. This is where the first ten minutes belong.

• Punctuation at the end of a line. A full stop or comma that jumps to the wrong side is the classic sign that direction was forced rather than handled properly.
• Latin words inside Hebrew sentences. Technologies, product names and a former employer's English name should sit in the right place in the sentence, not drift to the end of it.
• Dates and numbers beside Hebrew text. Ranges like 2021–2024 flip more often than you would expect.
• Embedded Hebrew fonts. If the font is not embedded, the file can look right on your machine and arrive as empty boxes on the reader's.

Export a real CV with a genuine mix of Hebrew and English in it, open the PDF, and read the end of every line. Do not judge a builder by its own sample content — samples are chosen to look good.

The ten-second test that rules out half the field

An applicant tracking system extracts text before any person sees your CV. If the file is effectively a picture of a CV, the extraction returns nothing. Some builders rasterise the export outright; others render Hebrew as glyph outlines with no character codes behind them, which looks identical on screen and is just as unreadable to a parser.

The test works on any tool and takes ten seconds: export the PDF, open it, select all, copy, and paste into a plain text editor. If your name, dates and bullets come out as readable text in roughly the right order, a parser can read it. If nothing pastes at all, or the Hebrew arrives as gibberish, that tool is not usable for real applications no matter how good the preview looked.

One CV per job, not one CV

Volume is not the lever most people think it is. Ten applications whose bullets use the vocabulary of that specific posting will outperform forty identical sends, because the person reading is scanning for evidence that you read the job description at all. A builder that only holds one document quietly pushes you toward the forty.

• Can you keep one master CV and produce a version per application, without duplicating the file by hand?
• When you fix a typo in the master, does the correction reach versions you have already created?
• Can you see what a version changed relative to the master, so you know what you actually sent?

Two languages, one CV

Almost every job seeker in Israel needs both languages: Hebrew for local employers, English for multinationals and for any company whose HR team works in English. The obvious solution is two separate documents, and it decays almost immediately — you add a role to one, forget the other, and three months later send an English CV that is missing your most recent job.

The question to ask a tool is whether the two languages are one CV with two faces, or two unrelated files that happen to share an account. A translation feature that hands you a disconnected copy is the second thing wearing the first thing's clothes.

Reading the pricing honestly

Pricing in this category is unusually slippery, and the patterns repeat often enough to name them.

• Free until export. You fill in an hour of career history, press download, and meet a paywall. The sunk cost is the product.
• Trials that convert on their own. A cheap trial that becomes a recurring subscription, sometimes on a shorter cycle than it appeared to be.
• Whether you can get your data back out. If leaving means retyping everything, the number on the pricing page is not the real price.

Where SuitedCV stands on each

This guide is published by a CV builder, so it should be held to its own tests. Here is what SuitedCV does on all five.

• Right-to-left in the export. Every template renders Hebrew right-to-left in the exported PDF as well as in the editor, with Hebrew fonts embedded in the file itself.
• Real text. The export renders an actual document and prints it to PDF, so the copy-paste test passes, and the underlying reading order matches what a human reads on the page.
• Per-job tailoring. One master CV, and a version per application that stores only what it changed — so a correction to the master reaches every version that has not deliberately overridden that section.
• Two languages, connected. The master CV holds Hebrew and English together, and translating a version produces a linked twin rather than a detached copy.
• A free tier that does not expire. Free covers two AI-tailored versions a month, five saved versions, and ten PDF exports a day. Export is not behind the paywall.

Deliberately absent here: a comparison table. Making claims about someone else's product requires using it properly first, and a comparison with one wrong row is worse than no comparison at all. The tests above are the ones that decide the outcome, and they work on any tool — including this one.

Common questions