Hiring in Iran offers access to a surplus of high-quality engineering and technical talent, often at a competitive cost. However, the distance—both geographical and regulatory—can make the process opaque.

To succeed, you need a rigorous filter. This guide covers how to interview for competency, bridge the cultural gap, and technically verify credentials using local systems like SAJAD.

The Decision Matrix (Do You Need a Local Employee?)

Before you schedule the first Zoom call, decide on your engagement model. This dictates your interview strategy.

Feature	Full-Time Local Employee	Remote Contractor / Freelancer
Commitment	High. Subject to Iranian Labor Law (termination is hard).	Low. Output-based. Easy to end.
Verification	Critical. You need official degree verification.	Moderate. Portfolio/Code is more important.
Best For	Building a long-term core engineering team.	Project-based tasks, design, distinct modules.
Verdict	Start with a Contractor model (3 months) before upgrading.

Pre-Interview Prep (Don’t Waste Time)

Most interviews fail because the logistics weren’t clear. Send a “One-Pager” to candidates before the call covering these three points:

1. The “Remote Operating System”:

   • Time Zones: “We work EST hours. Can you overlap 1 PM – 5 PM Tehran time?”

   • VPN/Connectivity: “Do you have reliable paid VPNs to access our Jira/Slack?” (Crucial question).

2. The Financial Reality:

   • Currency: “We pay in [USDT / Euro / USD via Exchange House]. We do not pay in Rials.”

   • Invoicing: “You are responsible for your local tax compliance.”

3. The “Paid Trial” Concept:

   • Be up front: “The final stage is a 1-week paid paid trial (approx. 10 hours) to test actual output. We pay $X for this upon completion.” This filters out 50% of candidates who are “job collectors.”

The Interview (Separating “Doers” from “Talkers”)

Iranian candidates are often well-educated and polite. You need to dig past the “we” to find the “I.”

A. The “English Stress Test” (10 Minutes)

Don’t just ask “How is your English?” Simulate a crisis.

• The Prompt: “Imagine the server goes down on a Friday night and you can’t reach me. Walk me through exactly what you write in the status update email.”

• What you are looking for: Clarity, brevity, and the ability to escalate blockers without panic.

B. Behavioral Questions (STAR Method)

Look for Situation, Task, Action, Result.

• Conflict: “Tell me about a time a client asked for a feature that was technically impossible. How did you say no?” (Tests Taarof/politeness vs. professional pushback).

• Autonomy: “Tell me about a project you shipped where the manager was completely absent.”

C. Red Flags 🚩

• The “We” Trap: Answers like “We built the API…” instead of “I wrote the endpoints for…”

• Vague Deliverables: Cannot show a specific repo, portfolio link, or screenshot because “it was internal/secret.” (Push for a redacted version).

• Timeline Mismatches: Dates on the CV don’t align with the stories they tell.

Cultural Context & Work Rhythm

Understanding the local “operating rhythm” prevents friction.

1. The Weekend Gap

• Iran: Thursday (Half day) & Friday (Full off).

• West: Saturday & Sunday (Full off).

• The Fix: Monday to Wednesday is your “Sync Zone.” Thursday is their Saturday; Sunday is their Monday.

2. The “Nowruz” Pause

• Iran shuts down for roughly 2 weeks starting March 20th/21st (Persian New Year).

• Action: Do not schedule launches or critical sprints in late March.

3. Decoding “Silence”

• In some contexts, silence means “I am working on it.” In others, it means “I am stuck but afraid to lose face.”

• The Fix: Establish a “No-Surprise” rule. “I value bad news fast. If you are stuck for >2 hours, ping me. It’s not a failure; it’s collaboration.”

Verification (The “Deep Dive”)

This is the most critical technical step. Do not rely on a PDF scan of a degree; these can be photoshopped. Use this 4-Level Verification System.

Level A: Low-Cost “Sanity Check” (15 Mins)

• Documents: Ask for the degree certificate + transcript + English translation.

• The Interview Check: “Who was your thesis supervisor? What was the exact title of your final project?”

• Why: Fakers often copy the degree name but forget the professors or specific coursework details.

Level B: Official Digital Verification (The “Code Sehat”)

Iran has a centralized digital system for higher education verification.

1. Ask the Candidate: “Please provide your Authenticity Code (کد صحت / Code Sehat) for your degree.”

   • Note: Graduates obtain this code via the SAJAD (Portal of Student Affairs) system.

2. Verify It: Go to the official portal (e.g., portal.saorg.ir) and enter the code. The system will display the verified degree details (Name, University, GPA, Date).

   • Value: This is the gold standard for domestic verification.

Level C: Consular Verification (For International Use)

If you need the document for a visa or formal HR compliance abroad:

1. The Mikhak System: The Iranian Ministry of Foreign Affairs (MFA) uses the Mikhak (میخک) platform for consular services.

2. The Process: The candidate uploads documents to Mikhak -> MFA validates -> You (or the candidate) receive a verification code.

3. The “Apostille” Reality: Iran is NOT a member of the Hague Apostille Convention.

   • Result: You cannot just get an “Apostille stamp.” Documents must be legalized by the Iranian MFA and then by the Embassy of your country in Tehran (or a third country if no embassy exists).

Level D: Direct University Check (The “Old School” Way)

• Ask the candidate to email the university registrar cc’ing you to authorize the release of information.

• Then, email the university using your official company domain (e.g., hr@yourcompany.com).

Phase 6: Contracts & Compliance (The Bottom Line)

1. IP & Data Rights

• Since enforcing a contract across borders is hard, use Technical Enforceability.

• Least Privilege: Give access only to the specific repo/figma file needed.

• Data Residency: Ensure no sensitive customer PII (Personally Identifiable Information) leaves your secure environment (use VDI or remote desktop if necessary).

2. The Exit Clause

• Include a clear “Handover Protocol.”

• Clause: “Final month’s payment is released only upon receipt of [List of Assets: Code, Keys, Design Files].”

Summary Checklist for Employers

• Defined the Role: Is it remote-friendly?

• Established Payment: Can I pay via Crypto/Exchange House?

• Scheduled Interview: Prepared STAR questions + English simulation.

• Verification: Did I ask for the Code Sehat (Authenticity Code)?

• Rhythm: Have we agreed on the Mon-Wed overlap hours?

Disclaimer: Sanctions regulations (OFAC, etc.) regarding hiring in Iran are strict and change frequently. Always consult with a legal compliance expert in your jurisdiction.