Should You Add Vibe-Coded Projects on Your Resume?
When AI-assisted projects belong on a resume, and what you should be able to explain before listing them.
You can probably include vibe-coded projects on your resume if they are real projects and relevant to the role, but you should be able to explain them honestly, and fully.
The answer depends a lot on how much work you put into the project, and if you know the project like the back of your hand. Some people understand vibe coding as just asking the agent to build something. If that's what you did, you probably shouldn't list it on your resume.
If you used the AI to help you develop the project faster but decided on the tools used, the decisions made, tested and found the bugs that popped up, steering the AI at every step, you can probably list it as an actual project of yours.
If you cannot explain how the project works, why certain choices were made, or what part you personally contributed, it is risky to list it.
Present the project truthfully: name the technologies, describe the result, and be ready to say where AI helped versus where you edited, tested, debugged, or designed things yourself.
Interviewers may dig into the details, and weak answers will hurt your credibility fast. The worst candidate I ever interviewed had a project like that that they wanted to highlight, they couldn't explain the architecture or logical inconsistencies, every question had them surprised.
Don't be the person someone remembers like that.
Projects are a great way to allow a candidate to express their experience or skill without proven work experience. A resume's goal is to land you an interview. If the resume oversells you and you end up in an awkward discussion about a project you ''made'' but can't explain, it defeats the purpose.