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
Worked on a website for my college project.
Built a responsive event-registration website for the college fest using React and Node.js, used by 200+ students to register over one weekend.
Did machine learning project on image classification.
Trained a CNN image classifier to distinguish 5 plant diseases from leaf photos, reaching 87% accuracy on a held-out test set.
Made an app for attendance.
Developed an Android attendance-tracking app with QR check-in, replacing a paper register for a 40-student class.
Helped with a hardware project.
Designed and assembled the sensor circuit for an IoT soil-moisture monitor, integrating it with a Raspberry Pi to log readings every 5 minutes.
Worked as a marketing intern.
Wrote and scheduled 15 social media posts a week during a 2-month marketing internship, contributing to a 12% increase in page followers.
Did an internship in finance.
Reconciled monthly vendor accounts for 30+ suppliers during a finance internship, reducing outstanding discrepancies from 18 to 3 by the end.
Built a chatbot.
Built a rule-based customer-support chatbot for a mock e-commerce site, handling 10 common query types with a Python/Flask backend.
Worked on database stuff for a project.
Designed and normalised a MySQL schema for a library management system, cutting duplicate-record errors reported by testers to zero.
Did testing for the group project.
Wrote and executed 25 manual test cases for the group's food-delivery app, identifying and logging 14 bugs before final submission.
Helped organise a college event.
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 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.
Choose projects that earn their space
Start with two or three relevant projects if they fit comfortably. This is a practical starting point, not an ATS rule: one substantial project can be stronger than several unfinished tutorials.
- Match: does it demonstrate a skill requested in the vacancy?
- Ownership: can you separate your contribution from your teammates’ work?
- Evidence: can you show a demo, report, repository, test, or design?
- Depth: can you explain one failure, trade-off, and next improvement?
Turn a tutorial into work you can defend
Credit the starting tutorial. Add a change you designed yourself—such as input validation, accessible navigation, an additional analysis, or tests—and describe that contribution. Do not present a copied application as an original product.
When you have no numerical result
Describe a verified capability or deliverable: “Added validation for missing dates and documented the rejected-row report.” You do not need a percentage improvement in every bullet. If you benchmark speed, keep the baseline, test conditions, and measurement method.
Rehearse your project explanation before adding it to the resume builder.
Common questions
Writing bullets that hold up under questioning