The 12 CV Mistakes That Get You Filtered Out by Israeli Tech Recruiters

A recruiter at a mid-sized Israeli tech company spends 8-15 seconds on a CV before making a stay-or-skip call. Eight seconds. That number is consistent across studies and consistent with what every Israeli recruiter I know has told me directly.

Eight seconds means most of your CV doesn't get read. The recruiter scans the top third, glances at the company names, skims dates, and decides. Mistakes that put critical information outside that scan zone, or that signal the wrong things during it, are why most CVs get filtered.

Here are the twelve I see most often, with before/after fixes for each.

1. Burying your stack below the fold

The mistake: technologies are listed in a "Skills" section near the bottom, or scattered across job descriptions where they're hard to extract.

Why it kills you: Israeli ATS systems (Comeet, Greenhouse, Workable, Lever) parse your CV looking for keyword density. The recruiter scanning afterwards needs to confirm the stack signal in the first 5 seconds. If your "Go" is in the bullet under your second-to-last job, both the ATS and the human miss it.

Fix: a one-line tech stack at the top of the CV, immediately after your name and contact:

Tech: Go, Python, PostgreSQL, Kafka, AWS · 8 yrs experience

Keep it to 5-8 technologies that are actually relevant. Don't list every framework you've ever touched.

2. Generic objective statements

The mistake: opening with "Highly motivated software engineer seeking challenging opportunities to grow in a dynamic environment."

Why it kills you: every other CV says this. It signals nothing concrete and consumes the most valuable real estate on your CV.

Fix: replace with a 1-2 line professional summary that names the specific work and scale:

Backend engineer specializing in payment systems. Built fraud-detection pipeline processing 4M transactions/day at Riskified.

Specific. Concrete. Scale-anchored. This is what the recruiter wants to see in seconds 1-2.

3. No quantification

The mistake: "Improved performance," "Led migration," "Optimized database queries."

Why it kills you: numbers are how recruiters separate "I touched this" from "I owned this." Without numbers, every accomplishment sounds the same.

Fix: every bullet should have at least one quantification — time, scale, count, percent, currency.

4. Mismatched dates between Hebrew and English CV

The mistake: the EN CV says "2019-2022" and the HE CV says "2018-2022" because you forgot to update one of them.

Why it kills you: Israeli recruiters often hold both versions side by side. Date mismatches signal carelessness at best, dishonesty at worst.

Fix: maintain one source of truth and regenerate both versions when anything changes. Better yet: use the resume builder which keeps both languages in sync automatically.

5. Missing or vague military service section

The mistake (Israeli candidates): listing "IDF, 2014-2017" with no unit, no role, no rank.

Why it kills you: military experience is signal in Israel. 8200 alumni, Mamram alumni, Talpiot alumni, technological units alumni — these tell hiring managers something specific about technical training and culture. A bare "IDF" says you'd rather not discuss it, which raises questions.

Fix: name the unit (or its general type if classified), your role, and one specific accomplishment:

IDF · Unit 8200, Technical Lead, 2014-2017 · Built signal-processing tooling used by three intelligence teams.

If your service is sensitive, you can omit specifics, but at minimum say "technological unit" and your rank.

We've got a full guide on the military service section.

6. Listing every technology you've ever touched

The mistake: a "Skills" section with 47 technologies including jQuery, PHP 5.3, AngularJS 1.x, SVN, Subversion, FoxPro, COBOL.

Why it kills you: it dilutes the signal. The recruiter is looking for proof you can do this job. A list with 47 things tells them you're either lying or unfocused.

Fix: 5-10 technologies you'd actively use today. Group them: Languages / Backend / Frontend / Infra / Tools. Old things that aren't relevant to what you do now: cut them.

7. Job descriptions instead of accomplishments

The mistake: "Responsible for maintaining the backend microservices infrastructure" — describes what you were assigned, not what you achieved.

Why it kills you: every job description matches every other person who held that job. Accomplishments differentiate you.

Fix: rewrite as accomplishments. The pattern is: action verb + specific thing + measurable outcome.

Designed and shipped a queue-priority system that reduced order-processing time from 12 minutes to 90 seconds for the top 5% of merchants.

Not "responsible for." Not "involved in." Not "helped with." You did or you didn't.

8. The wall of text

The mistake: 4-5 bullets per role, each 2-3 lines long, no whitespace.

Why it kills you: nobody reads it. Eight seconds isn't enough to parse a wall of text.

Fix: 3-4 short, scannable bullets per role. Each bullet is one sentence, ideally one line. The accomplishment should be the first 6 words.

9. Education section in the wrong place

The mistake: education at the top of the CV after 8 years of work experience.

Why it kills you: by year 5+, your work matters more than your degree. Education-on-top is a signal that says "I'm a recent grad" — and if you're not, it confuses the reader.

Fix: education goes below experience for anyone with 3+ years post-graduation. Single line, no GPA (Israeli recruiters don't read GPA the way American ones do), no honors unless they're prestigious within Israel (Talpiot, university scholarship, etc.).

10. Outdated contact info or no LinkedIn

The mistake: an old gmail address (yourname1985@gmail.com), a Skype handle, no LinkedIn, or a LinkedIn URL with a custom suffix nobody can type.

Why it kills you: recruiters Google you and check LinkedIn within the first 30 seconds of reaching out. If they can't find you, you're filtered.

Fix: clean professional email. Phone with country code (+972). Custom LinkedIn URL (linkedin.com/in/yourname). Optionally GitHub for engineers. That's it.

11. Photo on the CV

The mistake: including a passport-style photo at the top.

Why it kills you: it's a cultural mismatch. Israeli tech CVs do not include photos. International CVs (especially American) explicitly avoid them for legal reasons. A photo signals "I haven't researched the convention."

Fix: remove it. Your LinkedIn is your photo.

12. The wrong language at the wrong company

The mistake: sending a Hebrew CV to a multinational R&D center where the working language is English, or sending an English CV to a deeply Israeli traditional company where the recruiter prefers Hebrew.

Why it kills you: it signals you didn't bother to research the company's working culture.

Fix: default to English for international R&D centers (Microsoft Israel, Google Israel, Meta, Amazon, Apple), unicorns with international hiring (Wix, Monday, Mobileye, Wiz, Lightricks, Riskified, JFrog, Tabula), and multinational subsidiaries. Default to Hebrew for Israeli-traditional companies — banks (Hapoalim, Leumi, Discount), defense contractors, government-adjacent, and many smaller traditional Israeli software houses.

If unsure, send English. It's the safer default for Israeli tech in 2026.

We've got a fuller decision framework on language choice.

How to use this list

Don't try to fix all twelve at once. Pick the three biggest hits — usually #1 (stack at the top), #3 (quantification), and #7 (accomplishments not descriptions) — and rewrite your CV for those. Run it through the match analyzer against three of your target jobs. Iterate.

The eight-second rule isn't your enemy. It's a constraint. Constraints reward people who optimize for them. Most candidates are still optimizing for "what would I want to read," not "what can a recruiter scan in 8 seconds while drinking coffee on their second of 100 CVs that morning."

Be in the second group.