Anvil Career
Get Your Report
Back to Blog
PORTFOLIO AUDIT

Nothing to Write on Your Resume? Here's How to Build One From Zero in 2 Weeks.

•8 min read

You open a blank Google Doc. You type "RESUME" at the top, center-aligned, 16pt bold. Then you stop. There is nothing to put below it. No internship. No live projects. No GitHub profile worth linking. No open source contributions. The advice you have read says "highlight your projects" but you do not have any. "List your experience" — also none. The resume advice industry is built for people who have things to put on a resume. This article is for the people who do not — and who need to build that resume from zero in 14 days.

WHAT A MINIMUM VIABLE FRESHER RESUME ACTUALLY NEEDS

SECTION MINIMUM YOU CAN GET AWAY WITH OPTIMAL
Contact Name, phone, email, GitHub link Add LinkedIn and portfolio site URL
Education B.Tech [Branch], [College], [Year], CGPA Add 1-2 relevant coursework items if CGPA is low
Skills 3-5 technologies you can actually use. Not 20. Group by category: Languages, Frameworks, Tools
Projects 1 deployed project with live URL, README, and Git history 2 projects: 1 deep (your best work) + 1 wide (different skill)
Experience Do not leave blank. Fill with open source / freelance / hackathon 1 relevant internship or open source contribution with merged PR
The 14-Day Resume-Ready Project Sprint THE 14-DAY RESUME-READY PROJECT SPRINT Days 1-2 Scaffold + Plan Pick project. Init repo. Days 3-7 Build Core Features Frontend + API + DB + Auth Days 8-10 Deploy + Domain VPS. Nginx. SSL. PM2. Day 11-14 Doc + Apply README. Resume. Start. Days 1-2: Pick a real problem. Inventory management for a local shop. Attendance tracker for your class. NOT a Netflix clone. NOT a weather app. NOT a todo list. Those get you rejected. Day 14: Your resume now has a project. A live URL. A commit history. A README. You are no longer the person with nothing to write. Start applying.

WHAT TO PUT IN THE "EXPERIENCE" SECTION WHEN YOU HAVE NONE

WHAT YOU HAVE HOW TO FRAME IT
Open source contribution (merged PR) "Contributed to [Project Name] — fixed [issue] affecting [N] users. PR #[number] merged."
Freelance project (built for a client) "Built [project] for [client] — [what it does]. Deployed at [URL]. Managed requirements, delivery, and deployment independently."
Hackathon project "Built [project] in 48 hours at [Hackathon Name] — [what it does]. Placed [X] out of [Y] teams. [Tech stack used]."
College tech fest / event organiser "Organized [event] with [N] participants. Built [tool/website] for registration and tracking. [Link if applicable]."
THE RESUME THAT GOT A ZERO-EXPERIENCE STUDENT 3 INTERVIEW CALLS IN 2 WEEKS

Before: "B.Tech Computer Science. Skills: C, C++, Java, Python, HTML, CSS, JavaScript, React, Node.js, MongoDB, SQL. Projects: Online Shopping Website (course project)." Result: zero calls in 60 applications. After: "Built and deployed Attendance Tracker at tracker.example.com — full-stack app with JWT authentication, PostgreSQL, and CI/CD pipeline via GitHub Actions. 60+ incremental commits. Documented architecture in README with API docs." Result: 3 interview calls from the next 15 applications. The difference was not formatting. It was evidence.

5 RESUME MISTAKES THAT GET FRESHERS AUTO-REJECTED

MISTAKE WHY IT GETS YOU REJECTED FIX
Objective statement as the first section Recruiters skip it. Waste of prime resume real estate. Remove it. Start with your strongest project or your GitHub link.
Skills section with 15+ technologies Signals you know nothing deeply. "Proficient in C, C++, Java, Python, JS, TS, React, Node, MongoDB, SQL, Docker..." — no fresher is proficient in all of these. List 3-5 technologies you can actually build with. Specificity beats breadth.
No links or URLs anywhere Recruiter cannot verify anything you claim. Resume goes in the rejection pile. Add your GitHub link. Add deployed project URLs. Make them clickable.
PDF with bad formatting Resumes with photos, DOB, marital status, or decorative elements read as unprofessional. Plain single-column layout. No photo. No DOB. No marital status. No "Gender: Male."
Projects described by technology, not impact "Built using React, Node.js, MongoDB" tells the recruiter nothing about what you actually did. "Built a placement dashboard used by 200+ students to track application status across 15 companies." Describe the outcome.