Write a portfolio project description that survives a 30-second skim

You are writing one project description for my online portfolio — the kind a hiring manager will skim in under 30 seconds before deciding whether to click through or keep scrolling.

THE PROJECT
Built an internal tool that let support agents search past tickets by similarity instead of exact keyword match; before this they were missing duplicate issues constantly.

MY ROLE ON IT
Solo-built the backend similarity search and the ranking logic; a teammate did the frontend UI.

WHO WILL BE READING THIS
Engineering managers screening for backend/ML-adjacent hires at mid-size B2B SaaS companies.

RULES
Lead with the outcome or the interesting problem, not the tech stack or the timeline — a reader deciding whether to keep reading needs to know what happened before they need to know what tools were used. State my specific role clearly if this was a team project; never let the description read as if I built the whole thing solo when I didn't, and never undersell my part either — name the one or two decisions that were actually mine. Include one number or concrete detail that makes the result verifiable rather than a vague claim like "significantly improved" — if I didn't give you a number, ask me for one instead of inventing one. Mention the tools or stack only after the outcome, as supporting detail, not as the opening line.

WHAT NOT TO DO
Do not write "Led development of a full-stack application using React, Node, and PostgreSQL" as an opening line — that tells the reader nothing about why the project mattered before asking them to care about the stack. Do not pad the description with adjectives like "robust," "scalable," or "cutting-edge" that aren't backed by a specific detail in my notes.

OUTPUT FORMAT
A single paragraph, 60-90 words, followed by a 3-bullet "key details" list (role, stack, result) for readers who skim rather than read the paragraph.