Turn a college project into 3 resume bullet points

You are a senior engineer reviewing fresher resumes for an Indian tech
internship. I'll paste a description of one of my college or personal
projects. Rewrite it as exactly 3 resume bullet points.

Rules:
- Each bullet starts with a strong action verb (Built, Shipped, Engineered,
  Implemented, Designed).
- Each bullet names at least one specific technology I mentioned.
- Preserve any number I included. If I didn't mention numbers, suggest ONE
  realistic metric I could measure myself and mark it as "[measure this]".
- Tone: confident but honest. I am a student, not a staff engineer.
- No buzzwords, no emojis, no markdown, plain text only.
- Do not invent users, companies, or outcomes I did not describe.

Here is my project:
[PASTE PROJECT DESCRIPTION — what it does, tech stack, what you built, anything
you measured]

Who this is for

This prompt is built for final-year B.Tech students and recent graduates in India who do not have internship experience and are relying on college projects or personal projects to fill their resume. If your projects section is the main thing a recruiter will look at, these bullet points need to carry weight.

Most students describe their projects in long paragraphs or vague one-liners like "Built a website using HTML and CSS." Neither format works. Recruiters at companies like Flipkart, Razorpay, or even TCS Digital spend seconds on each resume. They scan for action verbs, specific technologies, and measurable outcomes. This prompt forces the AI to produce exactly that.

It also works if you built something during a hackathon, contributed to an open-source project, or created a side project to learn a new framework. The input is flexible. As long as you can describe what you built and what tools you used, this prompt will produce clean, professional bullets.

How to use it

Step 1: Write a short description of your project. Include what it does, the tech stack you used, what your specific contribution was, and any numbers you know (users, API calls, data size, response time). Do not worry about formatting. Just get the facts down.

Step 2: Copy the prompt and paste it into ChatGPT, Claude, or Gemini. Replace the placeholder at the bottom with your project description. The more detail you give, the better the output. One line of input will produce generic bullets. A paragraph of input will produce sharp ones.

Step 3: Review the output. Check that every claim is true. If the AI marked something as "[measure this]," go back to your project and actually measure it. If you cannot measure it, remove that part. Do not leave "[measure this]" in your final resume.

Example before and after

Before (what a student typically writes): "I made an expense tracker app using React and Firebase for my final year project. It tracks expenses and shows charts."

After using this prompt:

• Built a full-stack expense tracking application using React and Firebase, supporting real-time data sync across [measure this] user sessions.
• Designed an interactive dashboard with Chart.js to visualize monthly spending patterns across 5 configurable categories.
• Implemented Firebase Authentication for secure login and Firestore rules for per-user data isolation.

The difference is clear. The "before" version tells a recruiter almost nothing. The "after" version names specific technologies, describes what was actually built, and suggests where to add a number. A recruiter scanning this resume now sees React, Firebase, Chart.js, authentication, and data isolation — all in three lines.

Notice that the AI did not invent a user count or claim the app was "deployed to production." It stayed within what the student described and flagged where a metric could be added.

Common mistakes to avoid

Giving the AI a one-line description. If you write "Made a to-do app in React," the AI has nothing to work with. Spend two minutes writing a real description: what the app does, what tech you used, what features you built, and whether you worked alone or in a team.

Leaving "[measure this]" in your final resume. The AI uses this tag to suggest where a number would strengthen the bullet. It is a prompt for you to go measure something, not a placeholder to submit. If you cannot find a real number, rewrite the bullet without one.

Using all three bullets for the same project if you have multiple projects. If you have two or three projects, run this prompt for each one and pick the best two bullets from each. A resume with diverse projects looks stronger than one project with six bullets.

Accepting bullets that claim more than you did. Read every word. If the AI wrote "Engineered a microservices architecture" and you built a single Express.js server, change it. The prompt tells the AI to stay honest, but you are the final reviewer.

When not to use this prompt

Do not use this prompt if you already have well-written bullet points and are trying to tailor them to a specific JD. For that, use the bullet point rewriter prompt instead.

Also skip this if your project was a tutorial walkthrough with no modifications. Recruiters can spot "to-do app from YouTube tutorial" from across the room. If you followed a tutorial step by step, either extend the project with your own features first, or use a different project entirely.