# My AI‑Built Portfolio Landed Me an Interview > Source: > Published: 2026-10-10 16:18:48+00:00 # My AI‑Built Portfolio Landed Me an Interview Seeing Guilherme’s AI‑crafted portfolio on GitHub made me realize the same workflow could cut weeks off my own job search. The site is built with React.js, Next.js, TypeScript and Node.js, and it’s already live for recruiters to glance at. The repo, kira8000/pavaneli-site, is a clean, component‑first structure that feels more polished than a lot of hand‑coded beginner pages. ## What the AI Delivered The generated code drops you right into a functional Next.js project. Running `npm run dev` spins up a local instance instantly, and the TypeScript configuration is already in place, so you skip the initial setup hassle. The portfolio includes a head‑shot section, a skills grid, and a projects carousel—all wrapped in a responsive layout that works on mobile without extra tweaking. Because the AI handled the routing and styling, you can see the site in the browser within minutes of cloning the repo. The biggest win is speed: Guilherme says it was one of the fastest deployments he’s ever done. The AI also exported a concise README that lists the tech stack and points to the live URL, so you can push to a hosting service and have a professional page online almost immediately. ## Next Steps If You Want to Ship It If the generated code works as advertised, the logical move is to add your personal branding. Start by editing the bio section to reflect your unique voice— recruiters notice the subtle differences between a generic template and a genuine narrative. Next, swap the placeholder projects for real work; the repo already uses a static JSON file for the project list, so you just need to replace the URLs and descriptions. After you’re satisfied locally, push the changes to the GitHub branch and enable automatic deployment on Vercel or Netlify using the existing `vercel` or `netlify` scripts. Those platforms read the `package.json` scripts automatically, so you won’t need to configure anything extra. If something breaks on the live site, the first check is the build log. A missing `tsconfig.json` or an unused import will surface as a TypeScript error in the console, so run `npm run build` locally to catch those before they reach production. Finally, verify that the page passes a basic accessibility scan. Tools like `axe` can be run via `npm test` if the project includes a script for it. Even a quick check for alt‑text on images and proper heading hierarchy makes a noticeable difference to hiring managers using screen readers. By following those steps, you turn an AI‑generated starter into a portfolio that stands out. The original repo gives you a solid foundation, and the few manual edits are enough to make it feel personal without sacrificing the speed advantage that AI tools bring. If you’re still on the fence, try cloning kira8000/pavaneli-site, running `npm run dev` and seeing how quickly you can swap in your own content. The process is fast enough that you can iterate daily while you hunt for your next role. [Next Stop writing negative constraints for your LLM agents →](https://promptcube3.com/en/threads/9905/) ## All Replies （1） Want a live back-and-forth? [Join the global AI chat room](https://promptcube3.com/en/chat/) — login to talk. That `npm run dev` command is the exact reason I stopped rebuilding my site from scratch every time I get bored with my stack.