Choose from a wide range of NEWCV resume templates and customize your NEWCV design with a single click.
Use ATS-optimised Resume and resume templates that pass applicant tracking systems. Our Resume builder helps recruiters read, scan, and shortlist your Resume faster.
Use professional field-tested resume templates that follow the exact Resume rules employers look for.
Create Resume
Use professional field-tested resume templates that follow the exact Resume rules employers look for.
Create ResumeIf you're a high school or college student applying for a Nuxt.js internship, part-time developer role, summer position, or entry-level frontend job, your resume is not evaluated the same way as an experienced engineer's resume. Recruiters are not expecting years of professional work history. They're trying to answer a simpler question:
Can this student build things, learn quickly, and contribute with supervision?
For student Nuxt.js candidates, hiring managers care less about prior employment and more about evidence of technical ability. Strong projects, GitHub activity, hackathons, coursework, internships, open-source contributions, and collaboration signals often matter more than traditional work experience.
A student resume succeeds when it proves:
You understand frontend development basics
You've built working Nuxt/Vue applications
You can follow engineering workflows
You know Git and team collaboration fundamentals
You solve problems independently
When screening student applications, recruiters and engineering managers usually score resumes mentally across several categories:
Technical fundamentals
Evidence of real coding work
Project complexity
Learning initiative
Collaboration signals
Communication skills
Growth potential
A student with no work history but strong projects often beats a student with weak internship experience.
Why?
Because projects reveal how you think.
You can grow into the role quickly
This is where many student resumes fail. They list technologies without showing evidence of usage.
Saying "Nuxt.js, Vue, JavaScript" means very little.
Showing how you used them changes everything.
Projects show:
Architecture decisions
Technical curiosity
Problem-solving ability
Initiative
Technical depth
Persistence
A completed Nuxt project says far more than a generic skills section.
Student resumes should prioritize evidence.
Use this structure:
Contact information
Professional summary
Technical skills
Projects
Education
Coursework
Experience or internships
Hackathons or competitions
Technical clubs or leadership
GitHub and portfolio links
Move projects above experience if your projects are stronger.
That is extremely common for student developers.
Most student summaries fail because they sound generic.
Weak Example
"Motivated student seeking opportunities to grow and learn."
This tells recruiters nothing.
Good Example
"Computer Science student with hands-on experience building responsive web applications using Nuxt 3, Vue 3, JavaScript, TypeScript, and Tailwind CSS. Built and deployed multiple frontend projects using component-based architecture, API integrations, and GitHub collaboration workflows. Seeking internship or entry-level opportunities to contribute to real development teams while expanding frontend engineering skills."
This immediately establishes:
Technical focus
Technologies used
Real experience
Direction
Career goal
Student resumes often overload this section.
Recruiters prefer organized categories.
Good Example
Languages: JavaScript, TypeScript, HTML, CSS
Frameworks: Nuxt.js, Vue.js, Tailwind CSS
Tools: Git, GitHub, Vercel, VS Code, Postman
Frontend Concepts: Responsive design, component architecture, REST APIs, state management
Databases: Firebase, MongoDB basics
Development Practices: Agile, pull requests, debugging, testing
Keep skills honest.
Interviewers can identify keyword stuffing quickly.
Projects frequently determine whether student candidates move forward.
Strong projects prove:
You can build applications
You understand workflows
You can solve problems
You can ship products
Include:
Project title
Technologies used
What you built
Technical decisions
Measurable outcomes
Student Events Platform
Nuxt 3, Vue 3, TypeScript, Tailwind CSS, REST APIs
Built a responsive event platform allowing students to browse, search, and filter campus events
Integrated public APIs to dynamically display event information
Developed reusable Vue components using component-based architecture principles
Implemented responsive layouts for desktop and mobile devices
Deployed application using Vercel with automated GitHub deployment workflows
Reduced duplicate code through reusable UI components
Notice the difference:
This explains actual implementation.
Not just technologies.
Many recruiters click portfolio links.
Unfortunately, many student portfolios hurt applications.
Common problems:
Broken links
Empty GitHub profiles
Incomplete projects
Tutorial clones
Poor mobile responsiveness
A stronger portfolio project:
Portfolio Website Using Nuxt Content
Created a personal portfolio website using Nuxt Content and dynamic routing
Developed reusable UI sections and responsive layouts
Added project showcases, GitHub links, and technical blog content
Deployed through Vercel and configured continuous deployment
Optimized performance and page loading speed
Recruiters notice deployment.
Shipping matters.
Coursework helps students without experience.
But avoid listing random classes.
Choose courses supporting frontend development.
Good Coursework Section
Relevant Coursework
Web Development
Software Engineering
JavaScript Programming
Database Systems
Data Structures and Algorithms
Human Computer Interaction
Computer Networks
This gives hiring managers context.
Many students underestimate hackathons.
Recruiters often love them because hackathons simulate real engineering behavior:
Time pressure
Team collaboration
Rapid learning
Problem solving
University Hackathon Participant
Collaborated with four students to build a Nuxt/Vue prototype within 36 hours
Used GitHub pull requests and Agile sprint task management
Integrated APIs and built responsive frontend components
Presented working MVP to judges and technical mentors
Even without winning, this shows initiative.
Student candidates often believe open source requires expertise.
Not true.
Simple contributions count:
Documentation improvements
Bug fixes
Testing updates
UI enhancements
Small features
Recruiters see:
Collaboration ability
Git familiarity
Engineering workflow exposure
That single line can strengthen a student resume significantly.
Use accomplishment-focused bullets.
Avoid task-only descriptions.
Weak Example
"Worked on frontend development project."
Good Example
Built responsive web pages using Nuxt 3 and Tailwind CSS
Connected REST APIs and displayed dynamic content using asynchronous data fetching
Created reusable Vue components to improve maintainability
Debugged frontend rendering issues and improved usability
Collaborated using GitHub branches and pull request workflows
Participated in Agile team meetings and sprint planning
Deployed applications using Vercel
Built interactive interfaces using reactive state management
Improved page responsiveness across mobile and desktop layouts
Recruiters repeatedly see the same problems.
Bad:
"Nuxt, Vue, JavaScript, TypeScript"
Better:
Show where they were used.
Your retail job may matter less than your frontend project.
Prioritize strategically.
Recruiters recognize cloned tutorials quickly.
Projects should include original thinking.
Avoid:
Passionate
Hardworking
Results-driven
Team player
Show evidence instead.
For student engineers, GitHub often acts as an unofficial second resume.
SIMAR KAUR
Email | Phone | LinkedIn | GitHub | Portfolio
Professional Summary
Computer Science student with hands-on experience building frontend applications using Nuxt 3, Vue 3, TypeScript, and Tailwind CSS. Developed responsive web applications using API integrations, reusable component architecture, and GitHub workflows. Experienced collaborating on student projects and hackathons. Seeking internship, part-time, or entry-level Nuxt.js opportunities.
Technical Skills
Languages: JavaScript, TypeScript, HTML, CSS
Frameworks: Nuxt.js, Vue.js, Tailwind CSS
Tools: Git, GitHub, Vercel, Postman
Concepts: Responsive design, APIs, debugging, Agile development
Projects
Student Events Platform
Nuxt 3, Vue 3, TypeScript
Built responsive event browsing platform with search functionality
Connected public APIs and displayed dynamic content
Created reusable components
Deployed project through Vercel
Portfolio Website
Nuxt Content, Tailwind CSS
Developed portfolio website with dynamic pages and project showcases
Built responsive layouts and integrated deployment pipelines
Education
Bachelor of Science in Computer Science
Expected Graduation: 2027
Relevant Coursework
Web Development
Software Engineering
Database Systems
Data Structures
Hackathons
University Hackathon Participant
Most student rejections happen because resumes create uncertainty.
Recruiters ask:
"Can this person contribute within weeks?"
Strong resumes remove doubt.
The highest-performing student applications usually demonstrate:
Evidence of building real applications
GitHub activity
Deployment experience
Team collaboration
Technical curiosity
Learning initiative
The resume itself is not the goal.
The goal is reducing perceived hiring risk.
That is how student developers move from "interesting" to "interview."
Upload Resume
Import from Linkedin
