Open 50 fresher resumes and you'll find the same projects: a to-do app, a weather app, a Netflix clone, a calculator. They prove you followed a tutorial. They don't prove you can solve a problem.

Startups hire people who notice a real problem and ship something for it. The project doesn't need to be big. It needs to be real.

In 30 seconds

  • Pick a problem you or someone near you actually has
  • Get at least one real user (a shop, a society, a college club)
  • Show it with a live link, a README and a short write-up
  • 15 ideas below, sized from a weekend to a month

What makes a project impressive

  1. A real user. "Used by 40 shops in my area" beats any feature list.
  2. A real constraint. Slow internet, Hindi-first users, UPI payments, cheap phones.
  3. Live. Someone can open it right now.
  4. Explained. A README and one post about a hard decision you made.

15 ideas (sized by effort)

Weekend (2 days)

# Idea Who uses it What it shows
1 WhatsApp order bot for a local kirana shop One real shop APIs, real users, messaging
2 Society maintenance tracker (who paid, who didn't) Your housing society CRUD done well, simple UX
3 College event check-in with QR codes A college club Mobile web, scanning, quick ship
4 Hindi/English bill splitter for hostel rooms Your hostel i18n, small but useful
5 Price-drop alert for one product category You and friends Scraping or APIs, scheduled jobs

1 to 2 weeks

# Idea Who uses it What it shows
6 Appointment booking for a local clinic or salon One business Scheduling, reminders, real ops
7 Bus/shuttle live tracker for your campus Students Location, real-time updates
8 Expense tracker that reads UPI SMS (on-device) You Parsing, privacy thinking
9 Tuition centre attendance + fee reminders One tutor Roles, notifications, payments flow
10 Resume-to-portfolio generator (paste resume → site) Classmates Parsing, templates, deploys

3 to 4 weeks

# Idea Who uses it What it shows
11 Inventory app that works offline for small shops A shop with patchy internet Offline sync, real constraint
12 Voice-note to text summariser for field workers A small team Speech APIs, mobile UX
13 Local language job-alert bot for blue-collar roles A local agency Language, matching, messaging
14 Open dataset dashboard (rainfall, prices, traffic) for your city Public Data cleaning, charts, storytelling
15 Mini hackathon platform for your college (teams, submissions, judging) A college club Full product: auth, roles, uploads

How to present it (so it gets opened)

Title: the problem, not the tech.
❌ "Inventory App (MERN)"
✅ "Offline Inventory for Shops With Patchy Internet"

First line of the README: who uses it and one number.
"Used daily by 2 shops in Indore to track ~400 products."

One write-up (600 words): the hardest decision. "Why I chose to sync once every 10 minutes instead of live."

On your resume: verb + what you built + result.
"Built offline-first inventory app used by 2 shops; cut stock-count time from 2 hours to 20 minutes."

Save this: real problem + one real user + live link + README + one honest write-up. Size doesn't matter. Real does.

Where to show it

Disclosure: we build InfiniteInterfaces, a free builder network. Put your project, your write-up and your hackathon results on one profile, and it goes with every job application, so a recruiter sees the work, not just the bullet. You can also list what you built on the products launchpad, and join hackathons that can lead to job invites. Candidates never pay.

👉 Post your first project free

All usage numbers in this article are examples to show the format. Use your own.