CV & Project Ideas
Build a CV that gets responses. Build projects that get interviews.
What Egyptian Hiring Managers Actually Look For
- ▸ Your GitHub link is more important than your GPA
- ▸ 1 page max for less than 3 years of experience
- ▸ List projects with links to GitHub AND live demo
- ▸ Include your tech stack clearly
- ▸ Don't lie about skills — you will be tested
- ▸ English CV for most companies (even local ones)
What to Include — Section by Section
✅ Include:
Name, email, phone (WhatsApp number), GitHub URL, LinkedIn URL, portfolio website if you have one
❌ Skip:
Address (unnecessary), photo (optional and risky), age/birthdate
2–3 lines: who you are, main skills, what you're looking for. Optional but powerful if done right.
✅ Good:
"CS student at Cairo University specializing in backend development with Python and Django. Built 3 production apps. Looking for a backend internship where I can solve real problems."
❌ Bad:
"Hardworking team player passionate about technology"
University name, faculty, expected graduation year, GPA (only if > 3.5/4 or equivalent).
Drop high school info after year 2.
✅ Categorize them:
Languages (Python, JS) • Frameworks (React, Django) • Tools (Git, Docker) • Databases (PostgreSQL, MongoDB)
❌ Skip:
Soft skills list (communication, teamwork) — everyone says this and it adds nothing.
✅ Each project needs:
Project name + 1-line description + tech stack + GitHub link + live demo link
Mention impact: "Reduced loading time by 60%", "500+ users"
❌ Avoid:
Tutorial copies, university homework assignments
Company, role, dates, 2–3 bullet points of what you did + impact.
Even unpaid internships count — mention them. Skip unrelated work experience unless you have nothing else.
✅ Worth listing:
Google, AWS, Meta, Harvard CS50, IBM certifications
❌ Skip:
Udemy certificates (everyone has them — they don't impress)
CV Templates
Keep it clean, black and white, ATS-friendly.
Graduation Project Guide
A forgettable project: generic topic, barely works on demo day, no GitHub repo. An impressive project: solves a real problem, works live, has clean code on GitHub, built with a modern stack. The difference is not talent — it's preparation.
Professors care about: documentation, research methodology, theoretical depth. Industry cares about: does it work? Is the code clean? Would a user actually use this? Balance both: satisfy the academic requirements AND make something that works in the real world.
Q1: Does a real person need this? (If only your professor will ever see it, rethink.) Q2: Can you demo it live on presentation day? (If it's just a paper, it won't help your career.) Q3: Does it involve tech you want to put on your CV? (Pick a stack companies actually use.)
Clean README with: project description, screenshots, tech stack, how to run it, architecture overview. Add a .env.example file. Deploy it (Vercel, Railway, etc.). Add the live link to the README. This single repo can be the most important thing on your CV.
FAQ
Projects and GitHub. Seriously. Build 2–3 real projects that solve actual problems, push them to GitHub with good READMEs, and deploy them with live demos. A weak GPA with strong projects beats a 4.0 GPA with no GitHub activity at almost every company in Egypt.
Quality over quantity. 2–3 solid, completed, deployed projects beat 10 half-finished tutorial copies. Each project should: have a GitHub repo with a clear README, be deployed and accessible online, and solve a real problem or demonstrate a real skill.
Start with tutorials to learn, but do NOT put tutorial copies on your CV. Build your own version from scratch, adding features the tutorial didn't have, and making it your own. Employers can easily spot clones. The project list on this page has original ideas worth building.
Yes, especially if you're applying for your first job. Label it as "In Progress" and describe what you've built so far. Just make sure you can demo what you have live during an interview. Don't list it if it's just an idea — it needs to have real code.
Local Egyptian companies: they want to see you can ship a complete product with the stack they use (React, Node, Python). Emphasize completion and real functionality. Remote global employers: they care more about code quality, tests, deployment, documentation, and solving a real problem. A well-documented GitHub repo matters more than a fancy UI.