Ship your portfolio — then watch real humans visit it
A portfolio site is table stakes; knowing what visitors do on it is the skill. Build it with AI, deploy with real analytics installed, drive 20+ real visits over 5 days, and make one improvement based on what the data shows.
Posted by The AI Internships
The work brief
- 01Build and deploy your portfolio (AI builder or code + AI): who you are, 2+ projects from your micro-internships, contact. Let AI draft the copy, then cut anything that doesn’t sound like you.
- 02Install free analytics (Vercel Analytics, Umami Cloud, GoatCounter — or GA4).
- 03Share the link where real people will click it: WhatsApp status, LinkedIn, class groups. Collect 20+ visits over 5 days.
- 04Read the data — pages, devices, time-on-page, drop-offs — and ship one improvement it justifies.
What you’ll produce
Submission standard
Submit the live URL, an analytics screenshot showing real traffic over days, your reading of the data, and the change you shipped because of it. Include your AI workflow: tools, best prompts, and what you changed from the AI’s output. Also submit your portfolio's public repo; the analytics screenshot must show your own dashboard with a date range spanning 5+ days.
Your live portfolio URL
Public linkRequiredAnalytics screenshot: visits over 5+ days, pages, devices
Analytics screenshot from YOUR own dashboard (tool + your site visible), showing 20+ visits with a visible date range spanning 5+ different days — plus pages and devices. A single-day or dateless shot fails the authenticity gate.
Image uploadRequiredWhat the data says: where visitors came from, what they did, where they left
Written responseRequiredThe improvement you shipped because of the data, and what you expect it to change
Written responseRequired
You’ll complete these inside your private workspace.
What you must submit as proof
This brief requires evidence an AI can’t fabricate.
Public GitHub repo for your portfolio
Commit history must show the initial build AND the data-driven change as separate dated commits — a single paste fails the authenticity gate.
Public linkRequired
Submissions without this evidence cannot be submitted.
Protect other people in your proof. Blur faces, names, phone numbers and email addresses before you upload, and refer to anyone you worked with by role or number ("Listener 1", "the stall owner"). Your proof is only ever used to check your work — it is never published, never appears on your certificate, and is never shown in your public portfolio.
How your work is evaluated
The passing benchmark is 70/100.
Live portfolio
29%The site is live, presentable, and shows real project work.
Real traffic
29%Analytics show 20+ real visits spread over multiple days.
Data-driven change
14%The shipped change follows from the data, not from whim.
Dated multi-day traffic + build trail
29%Fails if the live URL is dead, the analytics screenshot lacks a visible multi-day date range or your account/tool, or the repo is a single dump with no separate commit for the change you shipped.
How we grade your AI usage
Using AI is the point — it’s the skill this certificate proves. You’ll answer three short questions about how you used it: what you asked, what was wrong with its first answer, and what you changed. Specific, honest answers score high. “I pasted the brief and submitted the answer” scores near zero.