How to Write a Fresh Graduate IT Resume With No Experience

A fresh graduate IT resume with no experience isn't really empty. Your capstone or thesis, your OJT, your org work and your side projects all count, as long as you write them like work: what you built, what tools you used, and what happened because of it. Put those in a "Projects and Experience" section near the top, add your GitHub or portfolio link in the header, and keep the whole thing to one page.

Most fresh grad resumes I see make the same mistake. They list duties instead of results, they bury the capstone at the bottom, and they open with an objective that says nothing. This post fixes that, line by line.

What goes on a fresh graduate IT resume with no experience

Here's the layout that works for most entry level IT roles in the Philippines:

1. Header: name, city (just "Quezon City" or "Cebu City," no full address), mobile number, professional email, LinkedIn URL, GitHub or portfolio URL.
2. Summary: two lines about the role you want and what you bring.
3. Projects and Experience: capstone, OJT, freelance or side projects, relevant org roles.
4. Technical Skills: grouped by type.
5. Education: degree, school, year. Latin honors or a relevant award if you have one.
6. Certifications: only real, completed ones.

Notice that education is near the bottom. Recruiters already know you just graduated. What they want to see first is proof you can do something.

Fixing your summary

Before:

Every recruiter has read that sentence ten thousand times. It tells them nothing about you.

After:

Specific role, specific proof, specific tools. Adjust the role title for each application.

Turning your capstone or thesis into experience

Your capstone is the biggest thing you've built. Treat it like a job entry, with a title, a date range and bullet points.

Before:

• Capstone project: Inventory System
• Used PHP and MySQL
• Group of 4

After:

Inventory and Sales System for a Local Hardware Store (Capstone, Aug 2025 to May 2026)

• Built the order and stock modules in PHP (Laravel) and MySQL for a real client, replacing their paper logbook.
• Designed the database schema (12 tables) and wrote the reporting queries for daily sales and low-stock alerts.
• Led user testing with the store owner and two staff, then fixed 15 usability issues before final defense.

Three things changed. There's a real client and a real problem. Your personal contribution is clear (in a group project, say what you did). And there are numbers you can defend in an interview. Only use numbers that are true; if you don't remember the exact count, describe the scope instead.

Here's a quick test for each bullet: could you talk about it for two minutes if an interviewer said "tell me more"? If not, either the bullet is vague or you're claiming more than you did. Fix it now, because the interview will find it later.

If your thesis was research-heavy rather than a build, frame it around method and tools: the data you collected, how you analyzed it (Python, R, SPSS, Excel), and what you found.

Making OJT count, even if it was mostly admin work

Plenty of OJT experiences involve more photocopying than coding. That's fine. Pull out every technical or problem-solving task, however small.

Before:

• OJT at City Hall IT Office
• Assisted the IT staff
• Did other tasks as assigned

After:

IT Intern, City Hall Management Information Systems Office (Jan 2026 to Apr 2026, 486 hours)

• Handled walk-in and phone support for 40+ employees: printer setup, Wi-Fi issues, Windows reinstalls.
• Logged and tracked requests in a shared Google Sheet, which the office kept using after my internship.
• Helped image and deploy 25 desktops for a new department.

That reads like an entry level IT support analyst, because that's basically what you did. If your OJT was at a software company, describe the features you touched, the bugs you fixed, or the test cases you ran. Our post on turning an internship into a full-time IT job has tips on documenting this while it's happening.

Org work and side projects

Org roles matter when they show something an employer needs: organizing, communication, or technical work.

Before: Member, Computer Society

After: Technical Head, Computer Society (2024 to 2025). Set up and ran the registration system for a 300-attendee hackathon using Google Forms and Apps Script.

Side projects are your best friend if your capstone was weak or your OJT wasn't technical. One finished, deployed project beats five half-done tutorials. A simple to-do app isn't impressive anymore, but a small tool that solves a real problem (a tuition payment tracker for your sibling's school, a GCash expense logger, a tool that scrapes your org's event sign-ups) is. For web dev hopefuls, our junior web developer portfolio guide covers what projects to build.

Where to put your GitHub and portfolio links

Put them in the header, on the same line as your email and LinkedIn. Recruiters skim the top of the page; links buried at the bottom get missed.

A few rules:

• Use clean URLs: github.com/juandelacruz, not a long link with tracking junk.
• Also link the specific repo or live demo next to each project title, so a recruiter can click straight to it.
• Make sure the repos you link have a README with a screenshot description, how to run it, and what you built.
• Pin your best repos on your GitHub profile. Delete or archive the "hello-world-test-2" clutter.
• If you send a PDF, check the links are clickable before you hit submit.

Writing your skills section without padding it

Before: HTML, CSS, JavaScript, Java, C++, Python, PHP, React, Angular, Vue, Node, MySQL, MongoDB, Firebase, AWS, Azure, Docker, Kubernetes, Photoshop, MS Office

If you list Kubernetes, the interviewer will ask about Kubernetes. Sayang ang chance if you freeze.

After:

• Languages: JavaScript, PHP, SQL
• Frameworks and tools: Laravel, React (basic), Git, Postman
• Databases: MySQL
• Other: Windows troubleshooting, Google Workspace admin basics

Group by type and only list what you could discuss for two minutes without panicking.

The part that's hard to do alone

None of this needs a course. You can rewrite every bullet with the examples above and a free afternoon. What's hard is judging your own resume. You know what your capstone did, so a vague line still reads clearly to you. A recruiter skimming for ten seconds doesn't have that context.

A second reader fixes that. In the Fresh Grad Track, week 1 is all about this: lessons on the ten-second resume test and writing project bullets, a GitHub cleanup task, then you submit your resume and a coach writes back on specific lines (which bullet is vague, which skill you can't defend, what to move up). You get it back while there's still time to fix it before week 2, when you start applying. You can read a couple of these lessons free in the Fresh Grad preview.

Quick checks before you send it

• One page, saved as PDF, named Lastname_Firstname_Resume.pdf.
• No photo unless the posting asks for one, no birthdate, no religion, no full home address.
• Every bullet starts with a verb: built, tested, designed, handled, set up.
• The job title in your summary matches the job you're applying for.
• Someone else has proofread it, ideally someone who has hired or works in IT, not just a classmate.

Once your resume is ready, use it to apply for the roles listed in our guide to IT jobs for fresh graduates in the Philippines. If you want a ready template with these sections already laid out, it's in the free IT Job Starter Kit.

Frequently asked questions

Should a fresh graduate IT resume be one page?

Yes. A fresh grad rarely has enough relevant material for two pages, and recruiters skim fast. Cut weaker items before you shrink the font.

Can I put group projects on my resume?

Absolutely, but state your own part clearly. Write "Built the payment module" rather than "We built a system," and be ready to explain your piece in detail.

Do I need a portfolio website as a fresh grad?

Not always. A clean GitHub profile with good READMEs is enough for most developer and QA roles. A portfolio site helps more for front-end and design-adjacent roles.

Should I include my GWA or Latin honors?

Include Latin honors or a strong GWA if you have them. If not, leave GWA off and let your projects do the talking.

Can someone review my fresh grad resume?

A batchmate or an IT friend is a good start. In the Fresh Grad Track, the resume is a week 1 assignment and a coach replies with written feedback on your actual draft. It's training, not a placement service, so it improves your resume but can't promise interviews.