The job offer arrived as a PDF with three bullet points and a Calendly link. No formal start-date letter, no eight-page handbook, no pre-boarding portal with a countdown timer. "Come Sunday at 10," the People person wrote in a Slack DM, "we'll figure out the laptop thing then." That message is the first real piece of information about the company you're joining. The orientation has already started; you just don't know it yet.
What follows is the tactical playbook I wish someone had handed me before my third Israeli startup. It's not advice about how to be brilliant. It's about the small operational moves that compound over the first ninety days, and the cultural reading you have to do quietly while everyone else assumes you're already up to speed.
Day One: The Self-Service Orientation
You'll arrive at an open-plan office somewhere in Sarona, Yigal Alon, or Herzliya Pituach. Someone from People will hand you a MacBook still in its box, point at a desk, and walk you to the kitchen for the espresso machine tour. That's roughly the orientation. The unspoken expectation is that you will ramp yourself up. Nobody is going to schedule you a two-week shadowing program. Nobody is going to send you a "first 30 days" Notion doc unless you ask, and even then the doc will be from 2023 and half the links will be broken.
This is not negligence. It is a working assumption that you are senior enough to figure out who to talk to, what to read, and what matters. Treating this like a problem will make you look slow. Treating it like the actual job — because it is the actual job — sets the tone correctly.
By end of day one, do three things. Find the #general and #engineering (or #product, or #design) Slack channels and scroll back two weeks. Open the company Notion or Confluence and read the most recent all-hands deck. And introduce yourself by DM to the three people whose names came up most in your interview loop — not a meeting request, just "hey, joined today, would love to grab coffee this week."
Week One: Slack Is the Office
Israeli tech runs on Slack the way American tech used to run on email. Threads are where decisions happen, where designs get critiqued, where someone vetoes a feature with three sentences and a shrug emoji. If you treat Slack as "background noise to check between meetings," you will miss the company. Everything that matters — and most of what doesn't — flows through it.
Spend week one reading. Not posting. Read the engineering channels even if you're a PM. Read #random because that's where you'll see who jokes with whom, which is the org chart no one will draw for you. Read the postmortems channel; most companies have one, sometimes called #incidents or #lessons. Two hours scrolling through six months of postmortems will tell you more about how the company actually operates than any onboarding deck.
Meetings will feel chaotic. People interrupt. The agenda dissolves in the first three minutes. Two engineers will start arguing in Hebrew, then notice you and switch to English mid-sentence, then drift back to Hebrew when the technical detail gets specific. Don't take this personally and don't ask them to stay in English unless you genuinely can't follow. Most bilingual Israelis switch languages based on which one carries the concept faster, and the switch is not about you.
The Miluim Conversation
Sometime in your first two weeks, a colleague will mention they have miluim coming up. Reserve duty. They might be gone for two weeks, or three, or longer depending on the security situation. The right response is not concern, not curiosity about what unit, not a long question about whether they're okay. It's: "Got it — anything I should pick up while you're out?" That sentence does three things at once. It signals you understand miluim is normal, that you respect them enough not to make it a moment, and that you're useful. File this away: anyone in the org from late twenties through mid-forties may disappear on short notice. Build your dependencies accordingly.
Month One: Velocity and the Hidden Hierarchy
By week three you will notice something disorienting: the pace. Decisions that would take a six-week steering committee at a US company get made in a Slack thread before lunch. A staff engineer will ship a refactor on Tuesday that touches twelve services, and the review will be three comments long. PRDs are often a paragraph and a Loom. Performance here is judged on output, not on hours or process adherence.
This cuts both ways. You can ship faster than you ever have. You can also burn yourself out chasing a tempo that is partially theatrical — some of the speed is real urgency, and some of it is people performing speed because that's the cultural default. Learn to tell the difference. Watch which decisions get revisited two weeks later and which ones stick. The ones that stick are usually owned by someone specific, often someone who's been there since seed or Series A.
Identify those people. Every Israeli startup has a hidden hierarchy that doesn't match the org chart. There's the formal VP of Engineering, and then there's the principal engineer who joined when the company was eight people and whose Slack reactions function as silent vetoes. There are the founders' trusted ICs — usually two or three people the CEO or CTO will pull aside for a side conversation in Hebrew before any major decision. You will not see this on the wiki. You will see it in who gets tagged on architecture threads, whose PRs get merged with the fewest comments, and who walks into the founders' office without knocking.
Days Thirty to Sixty: Coffee Is Politics
Around the four-week mark, people will start asking if you want to grab coffee. Some of these are genuine. Most are reconnaissance. They want to know what you think of the team you joined, whether you're going to be useful to their roadmap, and whether you're someone they can pull into a future cross-functional fight as an ally.
Take all the coffees. Take them seriously. Prepare two questions for each one, both genuine, neither leading. Good defaults: "What's the thing about this company that surprised you most?" and "If you were me, what would you spend the next month learning?" People answer these honestly more often than you'd expect, and the answers compound. By coffee number ten you will have a clearer mental model of the company than the head of HR.
The coffee is never just coffee. It's also never a trap. It's a low-stakes ritual for figuring out whether the new person is someone worth knowing.
Reading Your Manager
Israeli managers, with notable exceptions, do not deliver effusive praise. If your manager says "yeah, looks fine" about a deliverable you spent two weeks on, that is a strong positive signal. If they say "tov me'od" — very good — you've done excellent work. If they say nothing at all and move on to the next topic, that is also fine. The American expectation of explicit positive reinforcement does not transfer here, and waiting for it will make you anxious for no reason.
The signals to actually watch: are you being added to threads you weren't on before? Are you being asked your opinion in meetings without prompting? Is your manager forwarding you Slack DMs from leadership and saying "thoughts?" Those are the real promotions, weeks before any title change. Conversely, if you notice you've been quietly removed from a recurring meeting, ask about it directly within forty-eight hours. Don't let it sit.
Days Sixty to Ninety: Ship One Visible Thing
The single biggest mistake mid-career hires make in their first ninety days is trying to fix everything. You will see five things that are obviously broken. Documentation is a mess. The deploy pipeline is held together with three bash scripts and a prayer. The metrics dashboard contradicts itself. The product analytics setup hasn't been audited since 2024. Every one of these is a real problem.
Pick one. Finish it. Ship it visibly enough that two people outside your team mention it.
This is the move. It does not have to be the most important problem; it has to be a problem you can fully close in four to six weeks, where the closure is legible. A migration completed. A new endpoint shipped. A dashboard that someone other than you actually opens. The trap is the "boil the ocean" project — the eight-week refactor that touches everything and ships nothing concrete by day ninety. You will be evaluated, formally or informally, around that mark, and "I'm halfway through restructuring our data layer" reads as zero progress to anyone who wasn't deep in the work with you.
If you spent your final interview rounds prepping with something like our interview simulator to talk about your last shipped project, the muscle is the same one. What's the artifact? What's the metric that moved? Who else can vouch for it without you in the room?
The Cultural Tells
A few notes that don't fit neatly anywhere but matter.
You can just say no. When a PM asks if you can take on a third project this sprint, and the answer is no, the answer is no. You don't need a paragraph of context. "Lo, ein li bandwidth ha-shavua" — no, I don't have bandwidth this week — is a complete sentence. Israelis respect a clear no far more than a hedged maybe. The hedge reads as evasiveness.
Directness is not rudeness. When a senior engineer tells you in a code review that your approach is wrong, full stop, no softening — that is engagement, not contempt. The opposite, polite vague feedback, is what you should worry about. Polite vague feedback usually means the person has decided you're not worth the energy of a real critique.
Chutzpah works both ways. The same culture that lets a junior engineer push back hard on a VP's architecture decision also lets that VP push back hard on yours. If you only enjoy the upside of this and resent the downside, you'll be miserable. The deal is symmetric.
"Habibi" is a tell. When someone — usually a salesperson, a recruiter, or a founder in a fundraising mood — calls you "habibi" or "achi" while pitching you something, your bullshit detector should activate. Real friendliness in Israeli tech is operational, not performative. The person who doesn't bother with terms of endearment but answers your DM at 11pm with a real technical answer is the one who actually likes you.
What Ninety Days Looks Like When It's Working
Concretely, by day ninety, the picture should look something like this.
- You have shipped one thing that has your name attached to it in at least three Slack threads outside your immediate team.
- You can name, without thinking, the three people whose buy-in you need for any cross-team change.
- You have at least one peer in another function — a designer if you're an engineer, a backend engineer if you're a PM — who DMs you directly instead of going through your manager.
- You've sat through at least one company-wide moment of stress (a customer outage, a board meeting week, a re-org rumor) without being a source of additional friction.
- You can follow a meeting that drops into Hebrew for two minutes without losing the thread, even if you don't speak it. Context recovery is the skill, not fluency.
- Your manager has stopped checking in on your work proactively. They trust you've got it.
None of these are about being loved. They're about being legible — readable as someone who has fit themselves into the operating system without anyone having to install drivers for you.
The Israeli startup ramp rewards a particular combination: high agency, low ego about process, and the patience to let the culture teach you instead of explaining itself. The companies that move fast move fast partly because they don't slow down to onboard you. That's the cost. The benefit is that ninety days in, if you've done it right, you are not "the new person" anymore. You're just someone on the team who happens to have started in the spring.