Put it in the section that best explains the experience
Most internships fit under Experience or Relevant Experience because they involved supervised work for an organization. A laboratory appointment may fit under Research Experience, and a campus-based practicum may belong under Projects or Academic Experience when that label is more accurate. You do not need a separate Internships section for one role. Use section order to help the reader: a recent relevant internship usually appears before unrelated part-time work, while a first-year student may still place Education and selected coursework above limited experience.
Use the official title and identify the organization
Write the title shown in your offer or employer records and the organization's real name. If the official title is vague, you can add a clarifying function in parentheses without inventing a promotion—for example, ‘Summer Intern (Data Analytics).’ Do not rename yourself Software Engineer when the employer called the role Student Intern. If you worked through a university, research consortium or staffing organization at a host site, format the relationship so it is clear who employed or appointed you and where the work occurred.
Show dates and location consistently
Use the same month-and-year format throughout the resume, such as May 2026–August 2026. For a current internship, write the start date–Present only while you are actually participating. Location can be the city and state, ‘Remote,’ or a hybrid label when it helps explain the arrangement. Do not list an expected future internship as completed experience. After accepting but before starting, it is usually safer to leave it off applications unless a form specifically asks about future commitments; plans can change and you have no work outcomes to describe yet.
Build bullets from contribution, method and result
Start with the work you personally did, then name the method or constraint and the outcome you can support. ‘Analyzed 4,000 survey responses in Python to identify three recurring support issues used in a team recommendation’ tells the reader more than ‘Helped with data analysis.’ Not every result needs a percentage. Scope, frequency, audience, accuracy, time saved, decision supported or artifact delivered can all make the work concrete. If you did not measure an outcome, describe the deliverable honestly instead of manufacturing an improvement figure.
Separate your work from the team's achievement
Internships are collaborative, and your bullets should show both the context and your own part. ‘Worked on a team that launched…’ is incomplete unless the next phrase explains what you owned. Avoid claiming the whole organization's revenue, product launch or research result because you contributed one analysis. Useful verbs describe what you actually did: built, tested, documented, interviewed, reconciled, modeled, designed or presented. Be prepared to explain the inputs, choices and limitations behind every line in an interview.
Handle confidential work without becoming vague
Do not include customer names, private metrics, unreleased product details, protected research data or internal system information. You can still describe the problem type, general scale, method and audience: ‘Built an internal dashboard for weekly inventory review’ may be enough. Follow any confidentiality agreement and ask a supervisor when uncertain. Replacing protected numbers with invented public-looking numbers is not a solution. A precise description of your method can demonstrate skill without exposing the organization's information.
Label remote, unpaid and research roles accurately
Remote work is simply a location or arrangement, not a lesser experience. Unpaid status usually does not need to appear in the title, but you should never describe a volunteer or course requirement as paid employment when a form asks. A stipend-funded research program can use the program's official appointment title. Academic credit does not change what you accomplished. Accuracy matters because background checks, references and interview questions may compare the resume with the employer's records.
Edit toward the next role and keep a complete master copy
Keep a longer master resume containing the accurate bullets, tools and projects from each experience. For an application, select the two to four bullets most connected to its responsibilities and place the strongest match first. Remove routine details when a more relevant accomplishment can use the space. Update the resume soon after the internship while names, scope and results are clear, and save a copy of nonconfidential work samples or public links you are permitted to keep. Do not wait until the next recruiting deadline to reconstruct the term from memory.
A practical starting point
An internship resume entry
Data Analytics Intern — Example Organization | Phoenix, AZ May 2026–August 2026 • Cleaned and analyzed 4,000 survey responses in Python, identifying three recurring issues used in the team's service recommendation. • Built a weekly dashboard that combined data from two internal reports and documented the update process for the next analyst. • Presented findings to six operations stakeholders and incorporated feedback into the final analysis. Use only figures, tools and outcomes you can verify. Replace this example with your actual work.
This is editorial guidance, not an employer-required format. Use true details, respect authorship rules, and follow the actual application prompt.
Check the program-specific instructions
Use these independent guides to find the official requirements and application route. General advice does not override a publisher's instructions.
Check eligibility and the selected role's document instructions before submitting. FirstInternships does not accept applications or store your resume.
Find a program