Turns "I built a to-do app" into a portfolio description that shows judgment, trade-offs and results — what reviewers actually scan for.
Rewrite my project description for my {PORTFOLIO / GITHUB README / CV}. Reviewers spend 30 seconds — make them count.
MY PROJECT (rough description): {WHAT IT IS, WHAT IT DOES, TECH USED, ANYTHING HARD ABOUT IT}
Produce:
1. ONE-LINER: what it does + for whom + the impressive bit, in under 20 words. No "simple" or
"basic" — never undersell in the first line.
2. FULL DESCRIPTION (100–140 words): the problem it solves → the interesting decision or trade-off
I made (this signals seniority more than any tech list) → one concrete challenge and how I solved it → outcome (users, performance, or what I learned that changed how I build).
3. TECH LIST: ordered by relevance to the jobs I want ({TARGET ROLE}), not alphabetically.
4. THE QUESTION IT PLANTS: a good project description makes interviewers ask about it. What
question does mine invite, and my 60-second answer.
Rule: specifics beat adjectives. "Handles 10k concurrent users" beats "highly scalable".