The military section is the most-misunderstood block on an Israeli CV. People treat it like a formality — three lines stuck at the bottom in 9pt font, just enough to confirm "yes, I served." That misses what's actually happening on the recruiter side. In Israeli tech, the military section is a search field. It's a signal density check. And — depending on the company — it's sometimes the first thing the hiring manager reads.

I'm Pavel. Backend engineer, eight years in. I sent 217 applications and got 3 interviews before I figured out which parts of my CV were doing work and which parts were dead weight. The military line was dead weight for the first 80 applications. Once I rewrote it, recruiters started bringing it up unprompted on intro calls. Same service, same dates — just legible.

Here's what's going on, and how to fix yours tonight.

Why it matters more than you think

Israeli hiring managers read the military section. Not "glance at." Read. For cybersecurity-adjacent companies — Wiz, Check Point, Palo Alto Networks Israel, Cyberark, Sentra, Aqua, Snyk — the unit name is a hard filter. Recruiters at these companies will literally search their ATS for "8200" or "Mamram" or "Ofek" before they look at your work history. If the string isn't there, you don't surface in their search. You're not rejected — you're invisible, which is worse.

This isn't a stereotype. It's how the funnel works. A Wiz recruiter screening 800 applications for a security research role isn't reading every CV cover-to-cover. They're filtering. The unit name is the cheapest signal in the stack — one token tells them years of context (technical depth, security clearance handled, who the candidate worked alongside). For more on how those filters operate at the parser level, see how Israeli ATS filters actually work.

Outside of cyber, it's softer but still real. Mobileye, Intel Israel, AppsFlyer, Lightricks, Monday, Wix — none of them gate on unit, but every Israeli hiring manager I've spoken to admitted they form an opinion within 5 seconds of reading the line. Whether that opinion is fair is a separate conversation. The line is being read.

What recruiters actually scan for

Four things, in this order:

Unit name. Specific, spelled out, searchable. "8200" not "Intelligence Corps." "Mamram" not "Computer Service Directorate." If you served in a named unit — Talpiot, Atuda, Ofek, Matzpen, C4I, Egoz, Sayeret Matkal — name it.
Role. Technical or combat or logistics or instructor. One phrase, no buzzword inflation.
Dates. How many years. This signals maturity and — for officers — leadership track time.
One concrete output. A project, a system, a team size, an artifact. Just one. Anonymized to whatever level your security debrief allows.

That's it. Three or four lines total. The recruiter spends maybe 8 seconds here. Make it count.

The four common mistakes

Mistake 1: writing "IDF, Intelligence Corps" and stopping there. Useless. The Intelligence Corps has dozens of units doing wildly different work — from analyst roles to signals intelligence to research engineering. Without the unit name, the line carries zero information. If you served in 8200, write 8200. If you can't write the unit name for clearance reasons, write the function explicitly: "Signals intelligence — technical role, software development." Don't make the recruiter guess.

Mistake 2: tech-washing a non-technical role. I've seen combat soldiers write things like "led 12-person engineering team in mission-critical operational environment." This trips two alarms: the ATS parser flags the keyword density as inflated for the role, and any Israeli hiring manager reading it knows immediately what you actually did. They don't penalize the combat service — they penalize the dishonesty. If you were a tank commander, write tank commander. Leadership of 4 soldiers under stress is a real signal. Don't rewrite it as engineering management.

Mistake 3: burying the section. I've seen candidates put military service in 7pt font at the bottom of page two, like they're embarrassed by it. Israelis read CVs assuming the military section is there. When they have to hunt for it, they wonder why. Put it on page one if you served somewhere relevant to the role. Standard placement is after Education, before or after Work Experience depending on how recent your discharge is.

Mistake 4: international candidates omitting foreign service. If you served in the US Army, French military, IDF lone soldier program, or anywhere else — that's signal. Israeli hiring managers absolutely count it, especially for senior roles. The function translates: "Signal Corps Team Lead, US Army (2014-2018) — managed deployment of tactical communication systems, 8-person team." That reads cleanly to anyone in Israeli tech. For more on how international candidates position themselves, olim breaking into Israeli tech covers the broader playbook.

The right structure

Three lines. Maximum four.

Unit 8200, Israel Defense Forces — 2015–2019
Software Engineer, signals intelligence research group
Built and maintained internal data pipeline (Python, Kafka) used by 40+ analysts daily

That's the template. Unit on line one with dates. Role on line two with scope. One concrete artifact on line three.

For Atuda candidates, name the combo explicitly:

Atuda — Tel Aviv University (CS) + Mamram, IDF — 2013–2021
Backend developer, military software development unit
Led 3-engineer team building HR system used across IDF Manpower Directorate

For combat or non-technical roles, keep it brief and honest:

Givati Brigade, IDF — 2014–2017
Squad commander, infantry — responsible for 8 soldiers in operational deployments
Completed officers' course; received unit commendation

If you're writing your CV in our resume builder, the military block is its own structured section — fill the four fields and the formatting handles itself.

Hebrew CV vs English CV

In Hebrew, name the unit plainly. Israeli recruiters reading Hebrew CVs expect the unit name as a noun, not a description. ‏8200, ‏ממר"ם, ‏אופק — these are search tokens. Use them.

In English, you have a choice. If you're applying to an Israeli company, keep the unit name in English transliteration — "Unit 8200," "Mamram," "Talpiot." Israeli recruiters reading English CVs still know these. If you're applying to a multinational where the hiring manager is in Mountain View or Berlin, translate the function alongside the unit name: "Unit 8200 (military intelligence, signals research) — Software Engineer." The unit name still hits the ATS for any Israeli sub-recruiter; the translation gives the foreign reader something to anchor on.

The miluim conversation

Every Israeli candidate gets asked about miluim (reserve duty) at some point in the process — sometimes on the first call, almost always before offer. After October 2023 the conversation became more pointed: companies want to know cadence, role, and recent call-up history. Don't hide it. A short note at the bottom of the military section — "Active reservist, ~30 days/year, [unit]" — heads off the awkward "so, about your miluim..." moment in week three. For non-Israelis who don't have miluim obligations, it's worth one line ("No reserve duty obligations") because hiring managers will assume otherwise.

Note that miluim cadence is a real planning question for hiring managers, not a hostile one. They need to staff projects. Being upfront about your typical reserve days makes you easier to plan around, not harder.

Tonight's checklist

Pull up your CV. Check each:

Unit name spelled out explicitly. If you served in 8200, the string "8200" appears. If Mamram, "Mamram" appears. No "Intelligence Corps" placeholders.
Role is one phrase, accurate, no buzzword inflation.
Dates included — full years, not just "2015-present."
One concrete output — project, system, team size, artifact. One.
Section is on page one if relevant, in readable font size (10-11pt minimum).
Foreign military service translated and included if applicable.
Miluim status noted if you're an active reservist.

That's the whole job. Three lines, eight seconds of recruiter attention, and the difference between surfacing in a Wiz security search and being invisible. For the broader CV teardown — the other 11 mistakes that make Israeli recruiters reject — see 12 CV mistakes Israeli tech recruiters reject.

Fix this section tonight. It's the lowest-effort, highest-leverage change on the document.