Tech resume in Israel: what makes it different

A tech resume in Israel differs from a general Israeli CV in five ways: it is shorter (one page, two past a decade), it is usually in English, it carries a technologies section in exact product names, military service is written as a job rather than a unit name, and it includes one clickable link.

None of that is style. Each one exists because a specific person is looking for a specific string, usually in a search box inside an applicant tracking system.

What makes a tech resume in Israel different from a general Israeli CV

A general Israeli CV — the kind sent to an administrative role, to sales, or to a retail chain — is built around who you are: a photo, age, marital status, sometimes a full street address. In tech that is almost always redundant, and sometimes actively unhelpful.

Length. One page up to roughly ten years, two above it. Gotfriends, one of the larger recruitment agencies in Israeli tech, says one to two pages (published 22 August 2022, checked 2 September 2026), and Log-On, a hi-tech recruitment firm in Ramat Gan, says one page is the ideal (published 11 November 2025, checked 2 September 2026). Both pages are in Hebrew.
Language. In most Israeli tech roles the document is in English, even when the interview is in Hebrew.
A technologies section. Absent from a general CV, mandatory here.
Military service written as a role with scope, not as a unit name.
One clickable link — GitHub, a portfolio, or a LinkedIn profile that is actually maintained.
What comes out: photo, ID number, date of birth, marital status, full address, and "references available on request".

What all of it looks like assembled — we wrote out a full hi-tech resume, section by section, with the reason behind every choice.

What recruiters at Israeli tech companies say they look for

Worth saying first: there is no measurable survey of Israeli recruiters we could cite here, and we did not find one. What can be cited is what the agencies themselves publish in writing, with a date. That is a professional opinion from an interested party, not a research finding, and the difference is worth keeping.

Three points that recur across three separate sources:

A result with a number, not a job description. Log-On gives exactly this example (11 November 2025): instead of "works well in a team", write "led a team of four developers on Project X, including Agile task management".
A summary at the top. Gotfriends recommends opening with five or six bullets covering field, years of experience, stack and achievements (22 August 2022).
Words from the ad. Log-On writes that most tech companies run an ATS that scans the document and ranks candidates by keywords (11 November 2025). That is why the technologies section is written in names rather than categories.

The Coral Technologies guide (published 10 November 2024, checked 2 September 2026, in Hebrew) does something this page does not: it gives six examples for six different roles — full stack, DevOps, data, mobile, security and backend. If your role is one of the six, read it alongside this. Where it stops: it does not address the language question or military service at all.

Hebrew or English: which one to send

English is the default in Israeli tech, and it is what Gotfriends recommends (22 August 2022). Three situations change that:

The ad is in Hebrew and the company is entirely Israeli — Hebrew works, and sometimes fits better. But if the document might reach a manager who does not read Hebrew, English saves a round trip.
A multinational, or a development centre of a foreign company — English, always.
An ad written in English — English. In most cases the language of the ad is the answer to the question.

What does not work is translating the Hebrew file word for word. Job titles, degrees and institution names do not survive a literal translation, and an Israeli degree abbreviation means nothing to a reader abroad. We wrote separately about exactly what changes in the English version, including the job-title and degree tables.

If you keep both versions, keep them in sync. An English file a year behind the Hebrew one contradicts your LinkedIn profile, and that shows.

The technologies section, and why it is not a word list

The section exists so that a particular string can be found, which is why it is written in exact product names and not in categories. PostgreSQL, not "databases". Kubernetes, not "container orchestration".

Split it into short labelled lines — languages, infrastructure, data, tooling. Four labelled lines scan faster than one long comma run.
Order by depth, not alphabetically. What you use daily comes first. Gotfriends phrases this as detail for the tools you actually work with, then the secondary ones briefly (22 August 2022).
Do not list a technology you could not talk about for ten minutes. Log-On warns about this explicitly (11 November 2025), and the price is paid in the interview rather than in the screen.

What does not belong here: Office, Windows, "internet". And no five-star progress bars — they say nothing, and they are graphics inside a file that gets parsed.

Military service on a tech resume in Israel

For most Israeli candidates, army service is the first technical experience they had, and on a tech resume it is written like any other role: title, dates, what you did, at what scale.

For a reader who did not grow up with it: military service in Israel is compulsory, and several IDF units are technical organisations in their own right — 8200 is the signals-intelligence and technology unit, Mamram is the army's computing and systems centre, and Talpiot is a selective technology programme. Israeli recruiters recognise these names immediately, which is why candidates put them in. The limits are worth knowing:

A unit name on its own is a label, not experience. "8200" says where you were. "Built a data analysis tool in a team of six, in daily use by ~40 people" says what you can do. Write the second, with the first beside it.
If the role was technical, it belongs in the experience section, not in a separate line at the bottom. Three years of development are three years of development.
If it was not technical — infantry, an instructor, a medical corps officer — it still goes in, one line, with scope. Managing 30 people at twenty is information.
In a classified role, write the function, the scale and the tools without the content. "Built and maintained a distributed data pipeline in a classified environment; team of six, 24/7 operation" reveals nothing and says a lot.
If the service was a decade ago and is not relevant — one line at the end, not a section.

The Israeli hiring market treats this background as a category of its own: Gotfriends runs a dedicated team for graduates of IDF technology units (22 August 2022, checked 2 September 2026). That is a fact about how the market is organised, not a promise that the line opens a door.

For a resume read outside Israel this section works differently again, because the reader has no idea what a unit number is. That is in the separate post on the English version.

GitHub and portfolio links: when they help and when they hurt

One clickable link is among the few things on a resume that let someone check a claim instead of believing it. Gotfriends lists GitHub links, publications and personal projects as the "portfolio" worth attaching (22 August 2022).

It helps when there is something behind it: a project with a README explaining what it is, code written in the last two years, a contribution to an open-source project, a site that opens.

It hurts when the profile is empty, when the most recent commit is a 2019 course exercise, or when there are three repositories that are unmodified forks. An empty profile is evidence against, not neutral.

Two mechanical points: write the address as full text (github.com/dana-cohen) rather than as a linked word, because a hidden link disappears when the file is parsed as plain text. And keep the resume, LinkedIn and GitHub consistent — Log-On names consistency as a credibility signal (11 November 2025), and a date mismatch is the first question in the interview.

If you have no public code, do not manufacture some the night before. No link, no line.

A tech resume with no experience

With no employment history, the section that takes its place is projects, written to the same rules: what was built, in what, at what scale.

A course or bootcamp is written like a job — program name, hours, and what the final project actually produced.
Two or three projects with links, not seven without.
A student role, internship or course project with a real client is worth more than everything else combined.
Work outside tech is translated, not deleted. Support desk, waiting tables, a command role: working to a procedure, writing reports, handling a customer, staying calm. A line with scope, not a personality trait.

That is only half the problem. The other half is that junior roles collect hundreds of applications, and a better resume still lands in the same pile — a first hi-tech job with no experience.

One resume for everything, or one per job

One per job — and not because you rewrite it. The base file stays; what changes is the order of the lines, the words taken from the ad, and which piece of evidence moves up.

In tech this matters more than elsewhere, because two roles both called "Backend Engineer" can want two entirely different stacks, and the recruiter is searching for the string in her own ad. A resume that talks about Java will not surface in a search for Go, even if you wrote Go for two years.

We wrote about why that tailoring matters and why it still is not enough: it improves your position inside the pile rather than taking you out of it. What takes you out is someone inside passing the application along — and that is a request that can be declined, not a guarantee.

What to do now

Cut to one page. Under ten years of experience, whatever overflows is almost always job description rather than achievement.
Delete the photo, ID number, age, marital status and full address.
Build a technologies section in four labelled lines, in exact product names.
Rewrite the military service line as a role with scope.
Add one link — or add none at all.
Take the five jobs you want most and tailor the file to each. If it takes more than fifteen minutes per job, you are rewriting rather than reordering.

Step six is the one that comes back every week, and it is the step most people drop after the fourth job. That is why we built Tagishoti: it tailors the resume you already have to each job separately, out of what is written in it, and finds who inside the company could put you forward. It does not invent experience or achievements that were not there, nothing is sent without your approval, and finding people at a company needs a connected LinkedIn account.