Skip to main content

Resume Building Guide

Think of your resume like a README.md for your career. It needs to be clean, easy to scan, and "bug-free" (no typos!). Recruiters look at a resume for about 6 seconds before deciding to keep it or bin it. You have to make those seconds count.

1. The "A Master" Layout​

Don't use fancy, colorful templates with "Skill Bars" (e.g., "React: 80%"). Computers (ATS - Applicant Tracking Systems) hate those. Use a clean, single-column layout.

The Order of Operations:

  1. Header: Name, Phone, Email, Location (City/State), and links to your GitHub and LinkedIn.
  2. Summary: 2 sentences about who you are.
    • Example: "Full-Stack Developer and Founder of CodeHarborHub. Passionate about building scalable educational tools using React, Node.js, and AWS."
  3. Skills: Group them by category (Languages, Frontend, Backend, Cloud/Tools).
  4. Projects: (This is the most important part if you're a new grad!).
  5. Education: B.Tech details, graduation year, and GPA (if 7.0+).

2. Formatting Your Skills​

Don't just list every word you've ever heard. Categorize them so a recruiter can find what they need in 1 second.

CategoryWhat to include
LanguagesJavaScript (ES6+), TypeScript, HTML5, CSS3, Java, C++.
FrontendReact, Next.js, Redux, Tailwind CSS, Bootstrap.
BackendNode.js, Express, REST APIs, WebSockets.
DatabasesPostgreSQL (SQL), MongoDB (NoSQL), Redis.
Cloud/DevOpsAWS (EC2, S3, RDS), Docker, Git, GitHub Actions (CI/CD).

3. How to Describe Your Projects​

Don't just say "I built a chat app." Use the STAR method (Situation, Task, Action, Result) or the "X-Y-Z" formula.

Formula: "Accomplished X as measured by Y, by doing Z."

  • Noob way: "Made a tutorial site using React."
  • Master way: "Architected CodeHarborHub, an open-source learning platform, serving X+ students by implementing a React frontend and a Node.js backend deployed on AWS EC2."

4. The "DevOps" Edge​

Since you've been learning Cloud and System Design at CodeHarborHub, you have a massive advantage. Highlight it!

Include bullet points like:

  • "Containerized application using Docker for consistent development and production environments."
  • "Automated deployment workflows using GitHub Actions, reducing manual deploy time by 100%."
  • "Optimized data retrieval speed by 40% by implementing Redis Caching for frequently accessed API endpoints."

5. Resume Checklist (Before you hit 'Send')​

  • PDF Format: Never send a .docx or .txt.
  • Hyperlinks Work: Click your GitHub and Project links. If they lead to a 404, you won't get the job.
  • No Fluff: Remove "Hardworking," "Team player," or "Quick learner." Prove these through your projects instead.
  • Keywords: Does the job description say "PostgreSQL"? Make sure "PostgreSQL" is in your skills list.

Practice: The "GitHub" Audit​

Before you submit your resume, a Master ensures their GitHub looks professional:

  1. Pinned Repos: Pin your best 3-4 projects.
  2. READMEs: Every pinned project must have a screenshot and a clear "How to Run" section.
  3. Green Squares: Try to keep your contribution graph active. It shows you are consistently building!