Example only: fictional experience
The following resume is an educational example, not a real candidate, testimonial, or verified career history. Employers and institutions are placeholders. Replace every detail with your own; omit anything you cannot support.
Example Candidate
Student | City | Professional email | Relevant portfolio
Summary
Computer science student interested in software engineering internships. Building web applications through coursework and a campus club, with an emphasis on clear documentation and testing.
Experience or relevant work
Student Developer | Example Technology Club
Dates: use your actual start and end dates
- Built an event registration page with validation and a confirmation message for the campus technology club.
- Tested the page on mobile and keyboard-only navigation before sharing it with the organizing team.
- Maintained setup instructions so another student could continue the project after the event.
Selected project
Study Planner
- Created a planner that stores tasks locally and lets users filter by course and due date.
- Documented browser storage limits and added tests for sorting tasks with missing dates.
Skills
JavaScript / HTML / CSS / Git / Problem solving / Documentation
Education
B.Sc in Computer Science | Example College | Expected graduation: replace with your own
Why these bullets work
The examples name a specific artifact, explain a method, and show what was checked or changed. This makes the contribution easier to discuss in an interview without relying on invented impact numbers. Keep supporting notes or links where you are permitted to share them.
Rewrite pattern: Replace "responsible for projects" with "implemented [specific change] using [method] and verified [observable result]." Fill each bracket with a fact from your own work.
Writing tips for this role
- Write expected graduation explicitly rather than making an unfinished degree look completed.
- Include availability only when it is useful for the internship application.
- Describe campus and volunteer work as what it was, without inflated job titles.
Common mistakes to avoid
- Adding personal details that the employer has not requested.
- Hiding relevant projects below an unrelated hobbies list.
- Sending broken repository links or unfinished demos without an explanation.