63. Moving from Iran into the International Ecosystem
63.1Working Remotely
The realistic picture, stated plainly: direct employment by US companies is generally blocked by sanctions on Iran (employer-side legal risk makes it rare-to-nonexistent), but the global market is far larger than one country. Remote-accessible demand: EU-based companies (sanctions regimes differ and are less total — country-specific, check current rules), async-first OSS-fluent teams, freelance/contract work on quantum software (complicated but possible via payment workarounds — see below), and the entire self-directed track (Parts XIV, XVII — research needs no employer). Payment rails are the practical bottleneck: Iranian bank isolation means crypto, intermediary services, or local-legal structures; each carries compliance burden — your responsibility to verify on both sides. The engineering framing: remote income is possible, fragile, and non-scalable; treat it as bridge income while building the 62.9 credibility that makes relocation offers come to you.
63.2International Open-Source Participation
The good news chapter: open source is your sanctions-resistant university. Contributing to Qiskit, Cirq, PennyLane, stim, PyZX et al. from Iran is technically open (public repos, public contribution guides) — GitHub access has been intermittent but generally available; GitLab similar; academic code on public institutional repos is public. Practical notes: some platforms restrict features by region (CI minutes, some services) — workarounds are legitimate (self-hosted runners, mirrors) where terms permit; never misrepresent location on platforms whose terms require it (your identity is the asset — Ch. 62.9; a deception-based profile is a time bomb). Strategy: your OSS record is deliberately the most portable asset you can build — it works from Iran, works during relocation, and works after; weight your 62.5 ladder accordingly.
63.3Academic Applications
Applying from Iran to international programs: mechanics are standard (applications, transcripts, recommendation letters) with Iran-specific frictions: document verification (WES-style credential evaluation, required by many programs), English testing (TOEFL/IELTS — test centers operate in Iran), and the recommendation-letter problem (letters from Iranian professors work fine; international-collaboration letters are gold — Ch. 62.7's correspondence converts to letter-writers). Your application's differentiator is the 62.9 verified-artifact stack — for master's and PhD admissions in quantum fields, a public reproduction portfolio plus OSS committership is genuinely unusual and admissions-committee-legible. Timing discipline: applications 12–15 months before intended start; the artifact stack takes 18–36 months — the sequencing of this part of the book is your timeline.
63.4Master's Programs
The most reliable structured path: a master's in quantum-relevant fields (quantum engineering, physics, CS, ECE) at international universities — with Europe the natural target (tuition-free/low-cost systems in Germany, Nordics; English-taught programs abundant; visa policies for Iranian students established if scrutinized). What a master's buys you: credential (the door-opener you can't build remotely), lab access (Ch. 63.8's objective, purchased with enrollment), location (in-country job applications become legal and normal), and time (two years to specialize under supervision). Admission reality from your position: strong quantitative record + the artifact portfolio + a coherent narrative (this book's trajectory, told honestly) is competitive at many good programs; top-5 programs are lotteries for everyone — apply in bands. The Germany/Netherlands/Finland/Denmark cluster hosts major quantum ecosystems (IQT, QuTech, IQM-adjacent) — choose programs inside ecosystems.
63.5PhD Programs
The research career's gate, and a different bargain: five-ish years of paid (modestly) research apprenticeship in exchange for the credentials and craft of independent research (Ch. 59.8's checklist, formally certified). For your position: admission with funding is the only meaningful offer (unfunded PhDs are debt traps); US programs face sanctions-related friction in paying Iranian students — historically resolved case-by-case but a real risk factor to weigh against Europe and Canada; Europe's structured-PhD model (positions are jobs, advertised openly) is cleaner. Your competitive edge in PhD applications is exactly Parts XIV's output — research artifacts — because that's what PhD admission actually predicts for; a reproduction portfolio is a stronger signal than coursework. Choose advisor over ranking (your PhD is an apprenticeship to a specific person — Ch. 62.7's correspondence is how you learn who's good to work for, not just good).
63.6Research Internships
The highest-conversion-per-effort channel: 3–6 month internships at quantum companies and labs (IBM Quantum, Google, Amazon, Microsoft, plus the startup ecosystem; national-lab programs; university research internships). Two properties make them ideal for your trajectory: they're evaluated on artifacts (the hiring bar is "can you actually do the work" — your 62.9 stack applies directly) and they convert to offers (internship-to-full-time rates at quantum companies are high — the industry is small and prefers known quantities). The Iran-specific reality: US-based internships for Iran-resident applicants face visa and sanctions obstacles that are often disqualifying; EU-based labs and programs (Quantum Flagship projects, national labs like IQOQI, university groups) are more attainable; remote research collaborations with international groups (arranged via 62.7 correspondence — "can I contribute to your repo for course credit/nothing") are the undersung version, building the same references.
63.7Scholarships
The funding layer that makes 63.4–63.5 viable: program-specific (German DAAD — historically open to Iranians with strong records; Swedish SI; Dutch NWO-adjacent; Canadian Vanier at doctoral level), university-specific (waivers+assistanthips, negotiated at offer time — always ask), foundation programs (some explicitly support STEM mobility from restricted regions), and the quantum-adjacent industry scholarships (company-funded, often with internship attachment — see 63.6). Iran-specific realities: some scholarships have nationality-based eligibility carve-outs — read current termsheets rather than relying on folklore (rules change year to year); application essays reward exactly the coherent-trajectory narrative this book's parts have been building; and the artifact portfolio functions as the evidence layer for "exceptional ability" claims. Timeline discipline: scholarship deadlines precede program deadlines by months — build the calendar backwards from both.
63.8Laboratory Access
The Part-XVII-thesis problem, stated as logistics: you need hours on real quantum hardware and in real labs, and from Iran the channels are: cloud quantum computers (fully accessible — IBM's open queues, AWS Braket and Azure Quantum's friction varies; see Ch. 64.7–64.9 — this is real hardware access now, no relocation needed); simulation infrastructure (unlimited, yours — Ch. 64); remote collaborations (63.6's arrangement — a group's calibration data, an instrument's remote interface); and physical labs (requires relocation via 63.4–63.6 or employment). Sequencing strategy: cloud-hardware fluency (now) → remote collaboration (months 6–18, via your OSS/correspondence record) → physical lab (relocation, years 2–4). Each stage produces artifacts that make the next stage attainable; the sequence is the plan, and it starts today on your laptop — which is why this chapter follows Part XVII's order in the book.
63.9Immigration Pathways
The options map, honestly: student visas (the standard entry — Germany, Canada, Australia and most of Europe process Iranian student visas routinely; US F-1 processing for Iranians involves extended administrative processing — plan years-not-months); skilled-worker routes (post-degree: Germany's EU Blue Card system, Canada's Express Entry — points-based, degree+age+language favorable to you, Netherlands' orientation year); job-offer sponsorship (quantum companies sponsor, especially for scarce profiles — Ch. 60.5's QEC engineers get sponsored); and extraordinary-ability categories (US EB-1A/O-1, UK Global Talent — artifact-portfolio-based, and Ch. 62.9's stack is literally designed for these criteria). Strategic note: the artifact-first strategy is immigration-hedged by construction — the same verified public work that gets you hired gets you visas under talent categories, independent of employer sponsorship. Build once, use everywhere.
63.10Sanctions and Export-Control Considerations
The design constraints, named precisely so you can plan: financial sanctions (banking isolation — payments to/from Iranian persons are restricted; the practical consequences: subscription services unavailable, cloud credits purchasable only via legal intermediaries or free tiers — IBM's free open access is deliberately this); export controls on technology (EAR/ITAR-style regimes restrict export of controlled items and services to sanctioned regions — the relevant practical consequence: some proprietary software, some cloud services, and some technical support/consulting services are export-restricted; publishable fundamental research and open-source public-domain software are generally excluded — which is exactly why this book's open tools work for you); entity-list risks (some Iranian institutions are listed — affiliation with them adds friction to future applications; know your institution's status). The compliance discipline that protects you: work in public, use open tools, verify current rules (they change; OFAC/EU/UN sources, not folklore), never route around restrictions deceptively — your career's core asset is a verifiable identity (Ch. 62.9), and compliance is part of verifiability. This is an engineering constraint set like any other: know it exactly, design within it exactly.
63.11Documenting Your Technical Work
The relocation-supporting documentation layer: everything you build should be evidence-grade — because your portfolio will be read by admissions committees, visa officers (talent categories require documented achievement — Ch. 63.9's EB-1A/O-1 criteria: publications, media, judging, original contributions — all of which your public work generates), scholarship panels, and employers. The practices: archive everything publicly and timestamped (git history is your notary; blog posts with dates are your publication record), collect third-party documentation as you go (merged PRs, conference acceptances, correspondence that acknowledges your contributions, mentions and citations of your work — screenshots and URLs, saved contemporaneously), and maintain a living dossier (a private folder: achievements, evidence links, letter-writer contacts — updated monthly, because reconstructing two years of evidence the week before a deadline is impossible). The dossier is boring; the visa it enables is not.
63.12Building Relationships Before Relocation
The final principle: relocate into a network, not into a void. Everything in Ch. 62.7's correspondence practice compounds toward the moment you arrive somewhere — and the difference between arriving known versus unknown is the difference between a two-week and a two-year integration. The concrete program: by relocation time, aim for — ten researchers who know your name from thoughtful exchange, three OSS communities where you're a recognized contributor, one or two collaborators on actual work (papers, projects — remote co-authorship is the strongest pre-relocation asset), and attendance at whatever remote-accessible events your subfield offers. Then: when you land, the lab visits, meetup talks, and conference coffees are continuations, not cold starts. The book's deepest theme, stated as logistics: the laboratory you don't have (Part XVII) is replaced first by a network, then by a location — in that order, and the network is buildable from where you sit today.