Free account: 5 resume reviews with AI rewrite suggestions + 10 eligible AI actions each month. See plans →
ReachRole

Guides for your first job

Turn "worked on website"into a real bullet.

Action verb, what you built, a result. Ten before/after examples across branches, and a warning about the one thing that can undo an otherwise strong resume: an invented metric.

  • Ten examplesbefore and after
  • Never inventa metric you can't defend
  • One formulayou can reuse everywhere

Action verb (what you did) + what you built or worked on + a result, even a small, honest one. A metric is a bonus, not a requirement — a true, specific outcome beats a vague, impressive-sounding number every time.

Ten before/after examples

Before

Worked on a website for my college project.

After

Built a responsive event-registration website for the college fest using React and Node.js, used by 200+ students to register over one weekend.

Before

Did machine learning project on image classification.

After

Trained a CNN image classifier to distinguish 5 plant diseases from leaf photos, reaching 87% accuracy on a held-out test set.

Before

Made an app for attendance.

After

Developed an Android attendance-tracking app with QR check-in, replacing a paper register for a 40-student class.

Before

Helped with a hardware project.

After

Designed and assembled the sensor circuit for an IoT soil-moisture monitor, integrating it with a Raspberry Pi to log readings every 5 minutes.

Before

Worked as a marketing intern.

After

Wrote and scheduled 15 social media posts a week during a 2-month marketing internship, contributing to a 12% increase in page followers.

Before

Did an internship in finance.

After

Reconciled monthly vendor accounts for 30+ suppliers during a finance internship, reducing outstanding discrepancies from 18 to 3 by the end.

Before

Built a chatbot.

After

Built a rule-based customer-support chatbot for a mock e-commerce site, handling 10 common query types with a Python/Flask backend.

Before

Worked on database stuff for a project.

After

Designed and normalised a MySQL schema for a library management system, cutting duplicate-record errors reported by testers to zero.

Before

Did testing for the group project.

After

Wrote and executed 25 manual test cases for the group's food-delivery app, identifying and logging 14 bugs before final submission.

Before

Helped organise a college event.

After

Coordinated logistics for a 300-attendee technical fest as part of a 5-person team, managing vendor bookings and the day-of schedule.

Never invent a metric.

Never invent a metric you can't explain if asked. "Increased efficiency by 40%" with no way to justify that number in an interview is worse than no number at all — it invites a follow-up question you can't honestly answer, and that damage outweighs whatever the number added. If you genuinely don't have a measurable result, describe the scope instead (how many users, how many test cases, how many records) — that's still concrete and still honest.

Put it into your actual resume

Rewrite your bullets, then check how they parse.

Rewrite my resume Check my ATS score

Keep going

Project explanation scripts GitHub / project review All fresher guides

QUESTIONS? WE'VE GOT ANSWERS

Common questions

Writing bullets that hold up under questioning

What if my project genuinely had no measurable result?
Use scope instead of impact — how many users, how many features, how many records, how many test cases, how long it took. A well-described scope is still far more concrete than "worked on", and it's honest, which matters more than forcing a metric that doesn't exist.
Is it okay to estimate a number if I don't remember the exact figure?
A reasonable, roughly accurate estimate ("around 200 students", "roughly 2 weeks") is fine and normal. What to avoid is a precise-sounding number you've made up entirely, since that's the kind of detail an interviewer is most likely to probe.
How long should each bullet be?
One line, generally under about 25 words. If it's running to two full lines on the page, it usually means you're trying to fit too much into one bullet — split it into two, or cut it down to the single most important part.
Should every bullet follow the exact action-what-result structure?
It's the strongest default, but not a rigid rule — some bullets are naturally stronger when they lead with the result and follow with how you got there. What matters is that every bullet is specific and true, not that every one follows an identical template.
What action verbs work best for a fresher resume?
Verbs that describe what you actually did: built, designed, developed, implemented, tested, analysed, coordinated, automated, reduced, improved. Avoid vague verbs like "worked on", "helped with", or "was involved in" — they describe presence, not contribution.
Can I use this formula for internship bullets too, not just projects?
Yes — the same action-what-result structure applies to internship experience, and it's just as important there since an internship bullet is often the most scrutinised line on a fresher resume.
Still have questions? We're happy to help.
Email us We usually reply within a day