Between graduation and your first tech job stands a frustrating gap: every job asks for experience, and nobody gives you the first one. Thousands of graduates across Jordan, Egypt, Saudi Arabia and the wider region enter the market every year with the same degree and the same coursework — and those hired first are not necessarily the smartest, but the ones who understood the rules of the game early. This guide puts those rules in your hands. Understand the market you are entering Our region's tech market lives a paradox: strong demand for proven competence, and heavy crowding at the junior gate. Companies do not lack new applicants — they lack evidence of their competence. That is the insight everything below is built on: your mission is not to apply to more jobs, but to build stronger evidence than the other applicants have. Pick a track — then commit to it for a year The new graduate's biggest trap is scattering: a month learning web, then an AI course, then a taste of mobile — and after a year, nothing deep in any direction. Choose one track (backend, frontend, mobile, data...) based on your genuine inclination and local market demand, and commit to it for at least a full year. Depth gets hired; scatter does not. Fundamentals before frameworks Frameworks change every few years; fundamentals serve you for a decade: data structures and algorithms at a practical level, deep command of one language, and the basics of databases, HTTP and Git. Serious companies test exactly these fundamentals — because whoever has them learns any framework in weeks, and whoever lacks them keeps copying solutions they do not understand. Three real projects equal a year of experience University projects and tutorial follow-alongs convince nobody — your whole cohort has the same ones. Build three projects that solve real problems, however small: a tool you actually use, a service for a local problem you know firsthand, or a contribution to an open-source project. The golden test for each project: can you discuss it in depth for half an hour? Why this architecture? What was the hardest bug? What would you change today? Your GitHub account is your first CV Before anyone interviews you, many reviewers will open your GitHub. Make it tell a story of commitment: regular activity even if modest (consistency matters more than volume), repositories for your three projects with clear READMEs explaining the problem, the solution and how to run it, and clean code with meaningful names. An account dead for months raises a question you do not want raised. Internships and freelancing: experience before the job Do not wait for the full-time job to start working. An internship — even modestly paid — gives you what no course can: working in an existing codebase with a real team. Freelancing on small projects for local clients teaches you to handle vague requirements and real customers. Both turn into honest experience lines on your CV and concrete stories in your interviews. Apply smart, not hard Sending the same CV to a hundred jobs performs worse than tailored applications to twenty roles that genuinely match your track. Read the post carefully, adjust your summary and skill order to mirror it, and apply within the first days of posting when you can. And do not be intimidated by long requirement lists: if you match more than half of the core items, apply — job posts are wish lists, not strict minimums. Relationships open doors applications cannot A meaningful share of hiring in our region passes through referrals and prior acquaintance. You do not have to be a natural networker — genuine presence is enough: attend local tech events and developer meetups in your city, post what you learn on LinkedIn even as simple notes, and message developers whose work you respect with specific, respectful questions. Ask for advice, not a job — advice usually comes, and doors come with it. Rejection is part of the road — not a verdict You will get rejected. Many times. That is not a failure signal; it is the nature of a crowded entry gate. The difference between those who arrive and those who give up is treating rejection as data: at which stage do you usually stall? Before the interview — the problem is the CV or targeting. After the technical test — the training target is obvious. After interviews — work on stories and communication. Adjust, then try again — the whole cycle improves with every round. Your first ninety days on the job Got it? Now the most important phase begins: turning the first job into a launchpad. In your first three months: ask questions hungrily and write down the answers (a question repeated only twice is the acceptable kind), deliver your first small tasks impeccably before asking for big ones, and request feedback on your work early instead of waiting for the formal review. Your professional reputation is built in these weeks — and it is the most valuable thing you take from a first job. The bottom line: the gap between the degree and the first job is not crossed by waiting or collecting more certificates — but by building evidence: one deep track, three real projects, a living GitHub account, a human presence in your local tech community, and verified tests on modern hiring platforms. Start today with the smallest of these steps — our region's market rewards those who show up with proof.