Foundation
The Burn Window
A Hohmann transfer requires a precisely timed engine burn — too early, too late, or wrong angle and you end up in a worse orbit, not a better one. January 2026 to November 2027 is your burn window. This is how to aim it.
The frame
This is a hybrid program. You are not at HBS. That is not a limitation — it is a different set of constraints requiring a different allocation strategy. The six peak weeks in Tel Aviv are your highest-density periods. The online time between them is where most people drift. This guide is about not drifting.
Why the analogy
In orbital mechanics, a Hohmann transfer moves a spacecraft from a lower orbit to a higher one using two precisely timed engine burns. You can't just drift there — the physics don't allow it. The MBA is the same: the 22 months are the transfer arc, and they only work if you fire at the right moment.
The Window
Orient & Architect
Jan–Jun '26
Build Signal
Jul–Dec '26
Execute
Jan–Jun '27
Land
Jul–Nov '27
Orient & Architect
Jan–Jun '26
Build Signal
Jul–Dec '26
Execute
Jan–Jun '27
Land
Jul–Nov '27
The Four-Phase Architecture
Phase 1 · Orientation & Architecture
Path selection, ecosystem mapping, identity audit
Jan – Jun 2026
- ›Lock your primary path hypothesis — not final, but directional. Prevents drift.
- ›Map your network: who are your 20 warmest nodes? Where are the gaps by geography and sector?
- ›Map your cohort: know each member's domain, path direction, and primary network. Two hours of intentional conversation in the first peak week. The highest-ROI Phase 1 action that most people skip.
- ›Establish your LinkedIn signal baseline. Deep tech hiring is referral-heavy; your profile is your warm intro.
- ›Identify 2–3 knowledge gaps between where you are and where you want to be. Name them. Fill them on purpose.
- ›Use every peak week intensively — the in-person time is disproportionately valuable for serendipitous connection.
Phase 2 · Signal Building
Credibility creation, network expansion, early reps
Jul – Dec 2026
- ›Start producing visible output: one article, talk, or substantive post per quarter minimum.
- ›Have 20+ exploratory conversations with people in your target path. Not job asks — intelligence gathering.
- ›Apply for 1–2 stretch roles, accelerators, or competitions even if you're not ready. The reps are the point.
- ›Identify your 'unfair advantages' — your IDF background, technical domain, geographic positioning — and start naming them in conversations.
- ›Deepen 3–5 relationships from initial contact into genuine relationships. Quality beats volume.
Phase 3 · Execution
Active search, pitching, deal-making
Jan – Jun 2027
- ›The search or fundraise goes live. You should have warm connections in every target organization by now.
- ›Pitch yourself the way you'd pitch a company: thesis, traction, ask. The coffee chat has a structure.
- ›Most roles in this ecosystem are unlisted. Your network IS the job board.
- ›Negotiate from a position of multiple options. Run the process in parallel, not serial.
- ›Don't graduate into a job you settled for. The window is still open.
Phase 4 · Landing
Closing and first-90-days preparation
Jul – Nov 2027
- ›Close the role, offer, or round. Document the negotiation — you will negotiate again.
- ›Manage the notice and transition. Small ecosystems have long memories.
- ›Start the first-90-days preparation before Day 1.
- ›Begin giving back to the cohort network — the first class sets the ceiling.
What the top programs know that most students don't act on
Research from HBS, GSB, and Wharton on what actually drives MBA career outcomes. These findings hold regardless of program prestige.
The network is the return
Research on MBA career outcomes consistently shows that graduates' results correlate more strongly with the quality of their professional network than their GPA or coursework. The program is a trust factory. Treat it as one.
Every class is a live case
The best students treat every course, guest, and cohort conversation as primary research. You are surrounded by 15 other highly competent people with different professional views on the same ecosystem. Debrief them.
Internships > coursework in value per hour
At programs with 2-year formats, the summer internship (or equivalent) is the highest-leverage single event. In a hybrid program, your equivalent is the peak weeks and any structured project you can attach yourself to.
Career capital compounds
Research on career trajectories — including longitudinal studies at leading business schools — shows the advantages that compound hardest are: domain expertise, network density, and reputation for execution. All three take deliberate cultivation. None happen by accident.
You are negotiating all the time
Recruitment is a negotiation process that starts at the first coffee chat. How you show up in every conversation — your confidence, preparation, specificity — is being evaluated before any formal process begins.
Peak Weeks: The Disproportionate Asset
In a hybrid program, face-to-face time is rare and therefore undervalued. The research on professional network formation (Granovetter, 1973; Putnam, 2000) is clear: weak ties form most efficiently through in-person, unstructured interaction. The dinner after class, the coffee before it, the whiteboard session that ran late — these are where the relationships that will route you into unlisted roles get built.
Before the week
Identify 3 specific people you want to move from acquaintance to relationship. Have a reason to talk to each of them.
During the week
Eat every meal with someone different. Skip one social event; use the time to follow up on the morning's conversations while they're fresh.
After the week
Send 3 specific follow-ups within 48 hours. Not 'great to meet you' — reference something specific. One email ≠ a relationship. Two does.
If you're traveling in
Local cohort members can extend relationships built during the week naturally. You're on a plane home in 72 hours. Before the week: schedule at least one meeting outside program hours with someone in the Israeli ecosystem relevant to your path. During the week: days two and three are your highest-bandwidth periods — don't fill them with course prep you could have done remotely. After the week: the follow-up window for Israeli contacts is 48 hours. Send before the flight home.
What wastes the window
Over-optimizing GPA at the expense of relationship investment
Treating every path as equally viable past month 6 — optionality has a cost
Waiting until Phase 3 to start having exploratory conversations
Building a US network without a parallel Israel network, or vice versa — or building an Israel network without a clear view of where you actually want to land
Letting the online periods become passive consumption of course content
Applying for roles before your signal is legible to the audience that matters for that path
Treating the cohort as a study group — the relationships you don't build in the first 6 months don't get rebuilt in the last 6
Knowing what you want but not doing Phase 1 — path clarity and phase completion are not the same thing
Weekly operating rhythm
The architecture only works if it converts to weekly actions. These rhythms are minimal by design — small enough to be sustainable, significant enough to compound.
Peak week
When you're physically together
- ›3 intentional 1:1s with cohort members you don't know well yet
- ›Skip one scheduled social event — use it for a meaningful 1:1 instead
- ›Send follow-ups to everyone you had a substantive conversation with within 48 hours
- ›Attend the first dinner and last morning (see: Cohort traditions)
- ›One ask, one offer — before the week ends
Between peaks
The online weeks
- ›2 LinkedIn interactions per week — real comments, not likes
- ›1 exploratory conversation (video or voice) with someone in your target ecosystem
- ›30 minutes of ecosystem reading — one relevant article, annotated and shared if valuable
- ›One route per month: when you see something that fits a cohort member's path, send it to them directly
- ›One follow-up to close a loop from the previous peak week
These are floors, not ceilings. The people who outperform the architecture do more — but they do the basics first.