Your first resume.
Already full of potential.

What should come first?

Use the Student / early career option when creating a resume. It puts skills and projects before internships and education. Existing members can apply Skills and projects first from the editor Design tab; their content is preserved.

1. Name and focused introductionYour field, interests and the opportunity you want.
2. Relevant skillsTools and methods you can demonstrate.
3. Selected projectsCoursework, personal builds, hackathons or research.
4. Internships and experienceOnly real roles, including part-time or voluntary work.
5. Education and supporting evidenceDegree, relevant coursework, certifications and leadership.

This is a starting point. For a research role, education or research may deserve the first position. Reorder sections for the opportunity.

Write an introduction with direction

Describe what you study, a relevant skill or area of interest, and the contribution you want to make. You do not need to apologize for being a student.

Only use that wording if it is true for you. Replace vague claims such as hardworking with a specific activity or result.

Show skills through examples

Group related skills, such as Programming, Data analysis, Design, Laboratory methods or Languages. Select skills relevant to the role. Be ready to discuss how you used each one.

Link a skill to evidence: Python in a dashboard project, Figma in a usability study, writing in a student publication, or teamwork in an event you organized. Coursework and independent practice can count when described accurately.

Make academic and personal projects count

A project entry should answer four questions: What problem did you address? What did you personally contribute? Which tools or methods did you use? What did you produce or learn?

For team projects, separate your contribution from the group outcome. A useful prototype with an honest explanation is better than an inflated claim.

Add GitHub, Streamlit or another project link

Open Projects in the editor. Each entry supports four independent links:

• Project website: the main project page or portfolio entry.
• GitHub / source repository: code and documentation on any public repository host.
• Live demo / Streamlit: a working app, prototype, video or deployed demonstration.
• Case study or other link: a notebook, report, design file or supporting presentation.

Use full https:// links. Open each link in a signed-out browser before publishing. Add a useful README with setup instructions, your contribution, limitations and credits. Avoid committing passwords or private data.

Describe internships and other real experience

Include internships, part-time work, volunteering, tutoring, student organizations and freelance work when relevant. State the organization, role, dates and actual contribution. Label an internship clearly.

If you have no experience entries, leave the section empty. It will not appear on your public profile. Do not invent an internship or turn a personal project into employment.

Use education and coursework selectively

Include your qualification, institution and expected graduation date. Relevant coursework can explain your foundation when it supports the role. Add a thesis, laboratory project, academic award or certification when useful.

Make room for evidence. A short selection of relevant courses is easier to scan than a complete transcript. Add leadership and community work when they show specific contributions.

A final check before you publish

• Put the most relevant skills and projects near the top.
• Check spelling, dates, contribution claims and public links.
• Choose which contact details and sections to publish.
• Review the actual page on a narrow screen and check your exported document.
• Keep evidence and project documentation up to date.

For additional guidance, see Harvard SEAS on resumes and portfolios. Adapt advice to the employer, country and role.