What you will learn
- Write resume bullets that pass the 6-second recruiter scan
- Use the "Built X using Y, achieving Z" formula for technical projects
- Identify which details matter to hiring managers and which are noise
- Avoid the most common resume mistakes that disqualify CS students
Why this matters
Recruiters spend 6 seconds on your resume. If your project bullets say "Used React and Node.js" — so did 10,000 other applicants. A strong bullet proves you can build, ship, and reason about tradeoffs. It's the difference between landing the interview and getting filtered out.
The formula: Built X using Y, achieving Z
Every resume bullet should follow this structure:
- X — what you built (the feature or product)
- Y — the specific technologies (not a laundry list — pick 2-3)
- Z — the outcome or design decision (what makes it impressive)
Good bullets
Built a tech layoffs content site with Next.js App Router and Prisma, using Server Components for SEO-friendly pages that render in under 200ms
Implemented Stripe Checkout with webhook-based payment verification, gating premium content for 3 access tiers stored as a Prisma enum
Designed a normalized PostgreSQL schema with 6 models, explicit join tables, and performance indexes on high-traffic query paths
Added dynamic Open Graph metadata via
generateMetadata, increasing social link preview click-through by making every article shareable with rich previews
Bad bullets (and why)
Used React, Next.js, Tailwind CSS, Prisma, PostgreSQL, NextAuth, Stripe, and Vercel
- Problem: This is a technology list, not an achievement. It says nothing about what you built or why.
Built a website with a database
- Problem: Too vague. Every web app has a database.
Implemented CRUD operations for articles
- Problem: CRUD is expected, not impressive. Focus on the interesting decisions.
Worked on the frontend and backend
- Problem: This describes your role, not your impact.
What to include vs. what to drop
Include
- Schema design decisions (normalization, indexes, enums)
- Server/client rendering strategy and why
- Payment integration with webhook verification
- SEO implementation with measurable outcomes
- Authentication architecture (OAuth, session management)
- Deployment setup (CI/CD, preview deployments, env management)
Drop
- "Responsive design" — it's expected in 2026, not a differentiator
- "Used Git for version control" — this is assumed
- "Followed best practices" — empty claim with no evidence
- Technology laundry lists without context
- Number of lines of code or hours spent
Ordering and formatting
- Lead with your strongest bullet — the one that shows the most technical depth
- Use 3-4 bullets per project, not 6-8
- Start every bullet with a strong verb: Built, Designed, Implemented, Integrated, Optimized
- If you deployed it, include the URL — a live project is 10x more credible than a description
- Quantify when possible — "6 models," "3 access tiers," "under 200ms," "50+ articles"
Quick quiz
Q: Which resume bullet is strongest for a full-stack content site project?
How to explain it in an interview
"I write resume bullets using the 'Built X using Y, achieving Z' formula. X is the feature — not 'a website' but 'a paywall-gated content site.' Y is 2-3 key technologies, not a laundry list. Z is the outcome or interesting design decision — 'webhook-based payment verification' or 'Server Components for SEO-friendly rendering.' I lead with my strongest bullet and cap each project at 3-4 lines. If it's deployed, I include the URL."