Build a Portfolio That Converts Recruiter Interest
Building a Portfolio Site That Actually Works
Before anything else, you need to actually build the site. Two paths:
- Build from scratch using React, Next.js, or plain HTML/CSS and deploy it yourself. Good practice, takes longer.
- Use a site builder. Lovable, Framer, and Webflow let you get something clean up fast without fighting boilerplate. Lovable specifically lets you build with AI, which is worth trying.
Either path works. What matters is that the site exists, loads fast, and puts your work front and center.
Most recruiters who open portfolio websites only skim at best. If the first screen can't answer what you build, with what stack, and where the proof lives, they close the tab.
What gets read first
Assume mobile.
Your hero section should answer three things immediately: who you are, what kind of builder you are, and where to find your work. Not "aspiring technologist." Something like "CS student, backend-leaning" or "full-stack projects, Python and React."
Above the fold should have three exits: a featured project, a GitHub link, and a way to contact you or grab your resume. If those require hunting, you've already lost people who would've given you 30 more seconds.
Clarity beats novelty. A clean layout with obvious hierarchy beats a landing page that hides your work behind animations. Fix the signal first, add polish after.
Project cards
Two to four strong projects are all you need. Of course, feel free to build more if you're passionate.
Each card needs: a one-line outcome, the stack, a demo link if you have one, and a GitHub link.
Write the one-liner as problem, then what you built, then stack.
Weak: Todo app
Strong: Built a shared task board for our club's ops team of 6 people. React frontend, FastAPI backend, deployed on Render.
If the project came from a course that's fine, but don't stop at the assignment name. Name the scope, the tradeoffs, and what you decided.
If you link a live demo, it has to work. A broken demo is worse than no demo. If you can't keep it up, replace the link with screenshots, a video, and a tight README.
Your repo should have setup steps, a one-line architecture note, and an honest "my role" section if it was a team project. Commit history that shows you driving changes matters.
If you only have tutorial builds, add one non-template requirement to each and document what broke in deployment. That gap between "I followed a course" and "I shipped something" almost always shows up in the debugging stories you're tempted to leave out.
Hosting and ops
Pick something you can explain: GitHub Pages, Netlify, or Vercel. A custom domain is nice but not mandatory. What is mandatory: fast load times, no broken links, images that aren't massive. Run a broken-link audit before you send the URL anywhere.
Align your resume and LinkedIn
Your portfolio and resume are one story in two formats. Stack keywords and project titles should match across both. Put one canonical portfolio URL in your resume header and LinkedIn contact section.
Do this now
- Fix or remove one broken demo
- Rewrite three project one-liners into problem / what you built / stack
- Add your portfolio URL to your resume and LinkedIn, then open both side by side and look for contradictions