You made aliyah. Boxes are mostly unpacked, the Misrad HaPnim line was shorter than your friends warned you about, and now you need a job. Specifically, an Israeli tech job — because that's where the salaries are, the hiring is happening in English at a lot of companies, and your prior experience actually transfers.
This is the guide I wish someone had handed olim landing in Tel Aviv or Herzliya their first week. I've watched dozens of immigrants stumble through this — most of them on things that have nothing to do with Hebrew.
Reality calibration first
The biggest myth: "I need fluent Hebrew before anyone will hire me."
Most international R&D centers in Israel — Mobileye, Wiz, Microsoft Israel, Google TLV, NVIDIA, Meta Israel, Intel Israel — operate primarily in English. Code reviews, design docs, sprint planning, Slack — all English. Hebrew is preferred but not required for individual contributor roles.
Many Israeli unicorns are the same. Wix and Monday hire English-only ICs and run engineering in English. JFrog, Lightricks, Riskified, Tabula — same story for most R&D positions. AppsFlyer and ironSource lean a bit more Hebrew but still hire English-comfortable engineers regularly.
Where Hebrew genuinely matters: senior leadership roles where you're managing Israeli reports, customer-facing positions for the Israeli market, traditional finance, defense, and government tech. If you're an IC engineer, data scientist, PM, or designer — you're fine starting at A2-B1.
What olim actually struggle with
It's almost never the Hebrew. The actual friction points:
1. The Israeli CV is structurally different. No photo. Tech stack at the top, not buried at the bottom. Reverse chronological. Compact — Israeli recruiters expect one to two pages, three is rude. There's also a military service section, and yes, you write something there even if you didn't serve. Standard phrasing: "International candidate — did not serve in IDF." That single line saves recruiters from wondering why the section is missing. I wrote a whole piece on the military service section — read it, it's specifically for non-Israelis explaining their international service or lack of it.
2. Israeli directness reads as rude until you adjust. Your interviewer pushes back hard during system design. Interrupts your answer. Says "no, that's wrong" without softening. This is engagement, not disrespect. Anglo immigrants — especially from US corporate backgrounds — sometimes shut down or get defensive. Don't. Push back yourself. The interviewer is testing whether you can defend your reasoning under pressure, which is exactly what they need on the team.
3. The miluim conversation. Your colleagues will mention reserve duty constantly. Miluim is mandatory reserve service — most Israelis aged 21 to 45 with combat or specialist designations can be called up for 3 to 30 days, sometimes longer in active periods. Your tech lead might disappear for two weeks. Sprint planning accounts for it. Don't be the oleh who looks confused every time someone says "I'm in miluim next month." Know what it is, schedule around it, and don't be precious about deadlines slipping when half the team is in uniform.
4. Salary expectations get translated wrong. Olim from the US often under-ask because they convert their American comp expectation to shekels and panic. Israeli base salaries are lower in absolute ₪ than US equivalents — but cost-of-living-adjusted comp at international R&D centers is competitive, and equity packages at Israeli unicorns are real. The ranges shift fast. I keep a running market state for 2026 — read it before you negotiate. And do not accept the first offer. Israeli salary negotiation is direct and expected. Asking for more is not rude.
5. Recruiter pattern-matching. Israeli recruiters scan CVs fast and pattern-match on Israeli formatting cues — bagrut, IDF unit, tzava designations. Your CV won't have any of those. That's fine, but it means your CV needs to be unambiguously legible in the other ways. The 12 mistakes Israeli recruiters reject CVs for covers this. The ATS filter post is also worth reading — what actually parses your CV before a human sees it.
The six-month timeline
A realistic order of operations.
Months 1-2 — Foundation. Start ulpan if you have time, Duolingo plus weekly conversation tutor if you don't. Translate your CV to both English and Hebrew — yes, both, even if your Hebrew is shaky, because some companies require a Hebrew version even when interviews are English. Update LinkedIn: location says Tel Aviv, Herzliya, Ramat Gan, or Haifa, depending on where you actually live. Get an Israeli phone number on the CV. Recruiters do not call international numbers.
Months 2-3 — Networking and first applications. Israeli tech runs on personal intros. Cold applications work, but a warm intro converts at maybe 5x the rate. Set up coffee chats with anyone in your industry — olim networks on LinkedIn are dense and people respond. Start applications at the international R&D centers first. Mobileye, Microsoft, Google, Meta, NVIDIA, Wiz — these have the lowest Hebrew bar and the most experience with foreign hires. Don't waste your first month applying to companies that will reject you for Hebrew level when you could be getting interviews at companies that won't.
Months 3-4 — Interviews. Practice technical interviews in English first. They're easier when you're still settling in and your Hebrew vocabulary for "concurrency" is two weeks old. Once your Hebrew level allows, layer in Hebrew interview practice — but don't force it before you're ready. The 90-minute Israeli technical interview breakdown walks through what to expect. Before you submit applications, run your CV through the match analyzer against the actual job description — it catches the gap between what the listing wants and what your CV says, which is where most olim applications die.
Months 4-6 — Offers and negotiation. This is where you stop being polite. Israeli offer negotiation is direct. Ask for more base. Ask for more equity. Ask for sign-on. The recruiter expects it. Saying yes to the first offer signals inexperience and leaves money on the table. If you want a template, the cover letter Israelis actually read post has the tone calibration that works during these conversations too.
What olim don't need to worry about
Hebrew fluency. A2-B1 is enough for most R&D roles. B2 helps. Native is overkill for IC work. Don't postpone applications waiting to "be ready."
Military service. Most companies don't filter for it for international candidates. The cyber companies that do — Wiz, Check Point, parts of Riskified — are explicit about it in the listing, and the requirement is usually a specific clearance, not just "served in the IDF." If the listing doesn't mention it, it's not a hidden filter.
Network thinness. Olim worry their network is too small. It's fine. The English-language Israeli tech scene on LinkedIn is dense and welcoming — people respond to cold messages from olim more than from sabras, in my experience, because the community is small and supportive of new arrivals.
Where to apply first
Triage your applications by Hebrew expectation.
English-friendly — start here: Mobileye, Microsoft Israel, Google TLV, Meta Israel, NVIDIA, Wix engineering, Monday engineering, Wiz, JFrog, Lightricks, Riskified, Check Point R&D.
English-acceptable, Hebrew-preferred — apply with a strong CV: AppsFlyer, ironSource, Tabula, smaller B2B SaaS with Israeli HQs but international customer bases.
Hebrew-first — skip until you're at B2+: Israeli traditional banking and insurance, defense companies on the security-cleared side, government tech, Hebrew-market consumer apps.
Your aliyah-specific advantage
Frame this explicitly. Olim with relevant prior experience bring perspective Israeli companies actually need. US market knowledge for SaaS targeting US customers. EU regulatory familiarity for fintech selling into Europe. APAC market experience for companies expanding east. Native English writing skills for content, docs, and customer comms. These are real advantages, not just diversity-talk.
Put them in your cover letter. Put them in your CV summary. The recruiter at a TLV B2B SaaS company targeting US enterprise wants to know you understand the buyer they're chasing. Don't make them guess.
If you're not sure whether this guide is even aimed at you — the who Korotchaim is for post breaks down the audiences I built the tool for. Olim are explicitly one of them. The whole product was shaped by watching immigrants try to navigate a hiring market that nobody wrote a manual for.
You're not behind. You're just running a different playbook than the sabras around you. Run it well.