Hobbies for Resume
Short answer: List 2–3 hobbies on your resume only when they signal relevant skills or cultural fit — e.g. marathon running (discipline), open-source contributions (coding), debate club (communication). Skip generic hobbies (reading, music, travelling) unless space is abundant; never list hobbies on a one-page IT resume where projects matter more.
Hobbies are the lowest-priority section on a resume. They help only when they differentiate you or prove a skill the job needs. For freshers with thin experience, one strong extracurricular beats three vague interests.
When hobbies help
Creative roles — photography, UI side projects, writing/blogging. Sales/client-facing — debate, Toastmasters, team sports captaincy. Engineering — open-source, hackathons, robotics, competitive programming. Government/teaching — NSS, NCC, volunteering with scale (hours, people served).
Each hobby should connect to a skill: "Marathon finisher (3)" → discipline and goal-setting.
When to skip hobbies entirely
One-page resumes for IT/product roles with strong projects. Senior roles where space is premium. US/UK applications (hobbies can introduce bias). Any resume where hobbies would be generic (reading, listening to music, browsing internet).
Examples
Competitive programming (CodeChef 3★) · NSS volunteer (120+ hours)
Personal finance blog (2,400 monthly readers) · Marathon finisher
Reading books, listening to music, watching movies, surfing the internet