Syrian Talent: Hiring Across Borders

What does a readable portfolio actually contain?

Hiring Syrian professionals across borders works best when you treat the process as a documentation problem before it becomes a legal one. Ask for a portfolio that shows decisions, not just finished outputs, and write the contract around a defined scope with a payment schedule. Everything else, visas, time zones, tooling, follows from those two moves. A portfolio that survives an international hiring round is not a gallery. It is a record of choices. When you review work from a designer, developer or filmmaker who has moved between Syria, Turkey, Lebanon, the Gulf or Europe, you are reading a career that has been interrupted by events outside the person's control. The portfolio has to carry the continuity that a CV alone cannot. Ask for three projects and a short paragraph on each: what the constraint was, what was traded away, what shipped. A constraint might be bandwidth, a payment processor that does not operate in the country, a client who needed Arabic and English in the same interface, or a team that lost two members mid-sprint. The interesting part is the trade, not the screenshot. For software work, this means reading the experience as it would be read by an international team. Local tooling decisions, offline-first patterns, right-to-left layout, and how the person documented handoffs all matter more than a list of frameworks. For design, a case study that names the rejected option is worth more than a polished mockup. For film and archives work, the question is how source material was handled and what was kept.

How do you write a contract when the person is abroad?

Scope first, then money, then jurisdiction. That order prevents most of the arguments. Write the scope as deliverables with a boundary: what is included, what is explicitly not, and what triggers a change order. A freelance contract that says "website redesign" is unenforceable in practice. One that says "six screens, two rounds of revision, handoff in Figma and a component list" can be checked by both sides without a lawyer. On payment, split into milestones tied to those deliverables, not to calendar dates. If the person is invoicing from a country with limited banking access, agree early on the rail: a platform that supports the currency, a transfer to a relative's account, or a payment agent. Decide who absorbs the fee. Put it in writing, because the fee is often the difference between a milestone that clears and one that does not. On jurisdiction, pick one and say why. Many teams default to their own country's law because it is familiar, which is fine, but the freelancer should know before signing. If the work is ongoing, a short termination clause with a notice period protects both sides more than a long dispute resolution section nobody will use. Keep the contract in English and, if the person prefers, a second copy in Arabic. Two versions are not a legal problem if one is marked as the reference text.

What changes when the team is remote and distributed?

Remote work across time zones is a scheduling problem disguised as a culture problem. The fix is written handoffs. End each working day with a short note: what moved, what is blocked, what needs a decision. This is not bureaucracy. It is the only way a colleague six hours behind can pick up the thread without a meeting. Teams that skip it end up with a permanent morning call that suits one side of the world. Tooling should be chosen for readability, not for fashion. A shared document with a decision log beats a chat thread that scrolls away. A task board with explicit owners beats a channel where everyone assumes someone else is handling it. If the person is working from a place with intermittent power or connectivity, offline-capable tools and a clear expectation about response times matter more than any integration. Pay attention to the invisible load. A colleague managing a visa appointment, a family in another city, or a currency that moved 30 percent in a month is not less committed. They are carrying something your local hires are not. Build slack into deadlines for the first three months and say so out loud, so it does not read as a concession.

Which questions should you ask in the first interview?

Skip the puzzle questions. Ask about constraints and continuity. What was the hardest trade-off in your last project, and who disagreed with you? This surfaces how the person works with a team, not just how they think alone. How did you keep your work visible to people who were not in the room? This is the remote-work question in disguise, and it is the one that predicts whether handoffs will be clean. What did you have to rebuild after moving? A portfolio, a client list, a professional network, a certification. The answer tells you how the person handles discontinuity, which is the defining feature of a mobile career. What do you want to be doing in two years, and what would have to be true for that to happen here? This is where you find out whether the role is a stepping stone or a fit. It is also where you can be honest about what your company can and cannot offer someone working across borders.

How do you keep experience legible after a move?

Legibility is the whole game. A career that reads as a series of gaps is a career that gets filtered out by a recruiter who does not know the context. Rebuild the record deliberately. Translate titles into terms an international hiring manager recognizes, without erasing what the role actually was. Date the work by project, not only by employer, so a period of freelance or informal work does not look empty. Keep a running file of deliverables, clients, and outcomes, updated monthly, because reconstructing it after two years is painful and lossy. For creative work, the archive is the asset. Designers, filmmakers and writers who kept their source files, drafts and notes can show process, which is what senior hiring looks for. Those who only kept the final export have less to show, even if the work was stronger. Mentoring helps here, and it runs both ways. A person who has already navigated a move can tell a younger colleague which documents to keep, which clients to ask for a reference, and which contracts to refuse. That transmission is not charity. It is how a professional community keeps its experience from evaporating every time someone crosses a border.

What to do next

Pick one thing from this article and apply it this week. If you are hiring, rewrite one job description so the scope is a deliverable list rather than a wish list. If you are the one applying, open a document and write down the last three projects as decisions, constraints and outcomes. If you are managing a distributed team, add a written end-of-day handoff for two weeks and see whether your morning calls get shorter.

The next experiment is small and measurable. That is the point.

If you want a sense of how this is discussed by the people doing it, Syrian talent employment resources collect portfolios, contract notes and mentoring material aimed at professionals working between Syria and exile. It is a useful reference point when you are writing a job description and want the language to match the reality of a mobile career.