The Cover Letter Israelis Actually Read

A recruiter at a Tel Aviv unicorn told me last month that she gets between 80 and 150 applications per open role, per week. She spends roughly 40 seconds on the cover letter — when she reads it at all. Most weeks she doesn't. Five paragraphs about your passion for the company's mission don't survive that math.

The Israeli tech cover letter that works is six sentences. Not six paragraphs — six sentences. It exists to do one job: get the recruiter to forward you to the hiring manager. Anything beyond that is friction.

Why long cover letters die here

Israeli hiring is faster and blunter than the US or European version. Recruiters at Wix, Monday, Riskified, JFrog, AppsFlyer — they're scanning for signal, not reading prose. The five-paragraph format borrowed from American career-services templates is optimised for a hiring culture that doesn't exist here. "I am writing to express my keen interest in the Senior Backend Engineer position at your esteemed company" is dead before the second comma.

The two-paragraph cover letter — really the six-sentence one — outperforms the five-paragraph version with Israeli recruiters every time I've seen it tested. It respects the reader's time, which is itself a signal that you'd be a reasonable colleague.

The six-sentence structure

1. Direct relevance line. Anchor the first sentence in something the JD literally asked for, and prove you've done it. "I built the order-matching pipeline at Tabula handling 2M events/day. Your JD mentions Kafka at scale — that's what we ran on." Specific, parallel, no warm-up.

2. One credibility detail. Just one. "Led the team of eight that owned the MongoDB-to-Postgres migration at Riskified — $4M ARR system, zero downtime." If you list three accomplishments here, the recruiter remembers none. One sticks.

3. Why this company specifically. Not "your innovative culture." A real reason tied to a real thing they're doing. "Your mid-2026 launch of the public API overlaps directly with the last 18 months of my work at Tabula. I'd want to bring that pattern to your stack."

4. A small disqualifier or nuance. This is the move most candidates won't make and Israelis respect when they see it. "I haven't worked in regulated environments before, so the SOC2 piece of the role is something I'd be ramping into." Admitting one limitation makes everything else you said more credible. Cover letters that claim total alignment with every bullet read false — because they are false.

5. What you'd actually do in the first months. "First three months I'd focus on the migration backlog. By six months, ship v3 of the API." Almost no candidate writes this. The ones who can articulate it stand out immediately because it shows you read the JD as a problem statement, not a checklist.

6. Concrete close. "Free for a call next Tuesday or Wednesday afternoon — I'm in TLV." Not "looking forward to hearing from you." Give them a date. They'll either take it or counter with their own.

That's the whole letter. 90 to 130 words.

Three examples

Senior Backend, Riskified

Hi Yael,

I built the fraud-decision pipeline at Tabula handling 1.8M transactions/day on Kafka + Postgres — your JD calls out exactly that stack at scale. Led the eight-person team through our MongoDB-to-Postgres migration last year, $4M ARR system, zero customer-visible downtime. Your move into LATAM merchant onboarding overlaps with the multi-region work I've been doing for the past year. I haven't worked with chargeback-flow domain logic specifically, so that's the part I'd ramp into. First three months I'd want to land in the decision-engine team and learn the rule DSL; by six months, contributing to the v4 latency goals you mentioned at DevCon. Free for a call Tue/Wed next week — I'm in Ramat Gan.

Product Manager, Wix

Hi Tomer,

Shipped the editor-templates revenue line at Lightricks from $0 to $1.2M ARR in 14 months — your Wix Studio templates roadmap is the closest analog I've seen in market. Owned the full PRD-to-launch loop with two designers and four engineers. I'm watching the Studio app-marketplace beta closely; the monetization split you announced at WeAreDevelopers is the exact problem I'd want to work on next. I haven't managed a team larger than six, so the staff-PM scope here would be a stretch I'd grow into. First quarter I'd focus on getting the marketplace pricing experiments running; by H2 I'd want to be driving the partner-developer KPIs. Available for a chat next week.

Security Engineer, Wiz

Hi Noa,

I led the cloud-detection rule engine at Check Point's CloudGuard team for two years — caught the Log4Shell variant family three days before public CVE. Your CNAPP correlation work is the cleanest take on the problem I've seen since I left CheckPoint. Mid-2026 you're expanding the runtime-detection product; that's the area where my AWS + GCP + Azure background applies cleanly. I haven't worked in startup pace before — that's the adjustment I'd make. First three months I'd ramp on your ruleset and ship a meaningful detection; by six months, owning a sub-area of the runtime engine. Free Tuesday or Thursday next week for a call.

What to never do

Don't open with "Dear Hiring Manager." Use the recruiter's first name if you have it. "Hi team" if not. Israeli convention is informal — "Dear" reads like you submitted the same letter to 40 companies, which you probably did but shouldn't broadcast.

Don't copy-paste. A cover letter you can send to two different companies isn't a cover letter, it's a self-summary. The whole point is sentence three: why this company specifically. If you can't write it, skip the letter.

Don't reference "your dynamic team," "your innovative culture," or "your mission." These are the three phrases that get cover letters skim-skipped within the first ten seconds. They signal that you didn't research and you're padding.

Don't close with "looking forward to hearing from you." Replace it with a date. "Free Tuesday afternoon" creates a small action. The vague close creates none.

I built Korotchaim's cover letter tool around exactly this six-sentence structure — paste the JD and your CV, get three drafts back in the right voice. It's the version I wish I'd had when I was applying.

When to skip the cover letter entirely

Some Israeli JDs say "resume only" or "no cover letter required." Take them at their word. Wiz historically — and a handful of other security-first shops — genuinely don't want one. Sending it anyway signals you didn't read the post, which is worse than sending nothing.

If the application form has a cover-letter field but it's optional, write the six sentences. If there's no field at all and the JD doesn't mention it, skip it. The CV is doing the work. For more on what the CV needs to survive the first filter, see 12 CV mistakes Israeli tech recruiters reject in 60 seconds and how Israeli ATS filters actually work.

The cover letter isn't dead in Israeli tech — it just shrunk. Six sentences, one credibility detail, one honest limitation, one concrete next step. That's the whole game.