How to List an Internship on a Resume: Placement, Bullets, and 6 Filled Examples

Where internships go: the placement decision

Placement is the first decision and the one most candidates get wrong. The right answer depends on how much non-internship experience you have, how recent the internship is, and what field you are applying into. The wrong placement at any stage either buries the experience where recruiters do not look (current students placing internships at the bottom under "Activities") or signals career immaturity (a senior professional still labeling roles as "Intern" five years out). Four common scenarios cover almost every case.

The general principle: an internship belongs where a recruiter scanning the top third of the resume will see it. For a student, that is a dedicated section below Education. For everyone else, that is the main "Experience" section. There is no scenario where an internship belongs at the bottom of the resume under "Activities" or "Other," because that placement signals to the recruiter that you do not value the experience yourself.

The internship bullet template

Internship bullets follow the same pattern as full-time bullets, with one structural adjustment for the magnitude problem. The canonical pattern is Action verb + scope + tools + quantified outcome. An internship is usually 8 to 12 weeks long, which means the work you can claim ownership of is smaller in scope than a year-long full-time tenure. Quantifying the work feels harder, but the data is available if you look in the right places.

Quantify what you can: tasks completed, code reviews shipped, pages of research compiled, customer calls logged, model accuracy improvements, presentations delivered, audience size for those presentations, dollar value of the deliverable you contributed to. Use stack-rank metrics when raw numbers do not exist or do not convey the signal you want: "Top-3 finalist in summer cohort of 47 interns," "Selected to present final project to senior leadership," "Code reviewed and approved by four senior engineers before merge." These framings translate a short engagement into a comparative ranking that the recruiter can immediately calibrate.

Aim for one specific number or one specific peer comparison per bullet. Even soft numbers ("approximately," "over") beat zero numbers. A bullet that says "Conducted approximately 60 customer discovery interviews across three vertical segments" is calibrated and credible; a bullet that says "Conducted customer discovery interviews" is invisible.

Bullet count, dates, and timeframes

Internship entries follow slightly different conventions than full-time roles because the duration is shorter and the role description is less self-evident. Three rules cover almost every case.

• 3 to 4 bullets per internship. Counterintuitively, internships often get more bullets than full-time roles, not fewer. A 10-week internship leaves a recruiter with no implied context (a multi-year full-time tenure tells them you owned something for years; a summer internship does not), so the bullets have to carry more weight. Three is the floor for any serious internship listing; four is the ceiling unless the internship spanned two summers or converted into a part-time role.
• Date format: month and year on both sides. Write internships as "Jun 2024 to Aug 2024" or "Jun 2024 – Aug 2024." Year-only formats invite the recruiter to assume the role was longer or shorter than it actually was. Do not use em dashes anywhere on the resume; use the en dash entity (–) or the word "to" between dates.
• Stacked lines when a summer internship became a continuing part-time role. Some internships convert into part-time school-year work. List both lines stacked under one employer header, like this: "Marketing Intern, Jun 2024 – Aug 2024 (full-time, summer cohort)" on one line, then "Marketing Associate (Part-Time), Sep 2024 – present (~12 hours/week during school year)" on the next. Recruiters read the stacked layout as a return offer, which is itself a strong signal.

If the internship lasted less than 6 weeks, consider whether to list it at all. Engagements shorter than 6 weeks rarely produce shippable outcomes and can read as resume padding. Exceptions include accelerator programs, fellowship cohorts, and selective short-format internships (Forage virtual experiences, Bank of America's spring weeks, Meta's University Fall Recruiting Program) where the selectivity itself is the signal.

Internship titles: keep them honest

The title on the offer letter is the title that goes on the resume. There is no scenario in which inflating an internship title helps; recruiters who back-channel references will surface the discrepancy, and ATS systems trained on industry title taxonomies (Workday, Greenhouse) penalize titles that do not match the salary band implied by the rest of the entry.

• List the actual title from the offer letter. If you were hired as "Marketing Intern," list "Marketing Intern." If you were hired as "Software Engineering Intern," list that exact string. Do not paraphrase, do not promote yourself to "Associate," do not drop "Intern" to read as more senior.
• "Intern" or "Summer Intern" is fine. Recruiters expect to see "Intern" in the title for early-career resumes. Hiding the word does not make the resume read as more senior; it makes the recruiter wonder why the dates only cover 10 weeks of a single summer.
• Use the specific title when the firm uses one. Investment banks, large management consultancies, and big-tech engineering programs use specific titles. Goldman Sachs uses "Summer Analyst." McKinsey uses "Summer Associate." Google uses "Software Engineering Intern" or "Student Researcher" depending on program. Keep those titles exactly as the firm uses them; recruiters know the program titles and screen on them.
• Do not promote "Intern" to "Associate" or "Analyst." The post-graduation title at most banks and consulting firms is "Analyst" or "Associate." Internship titles are usually "Summer Analyst" or "Summer Associate." Removing "Summer" implies a full-time role and is treated as misrepresentation.

One exception worth knowing: if the internship was unusually senior (you led a project that a full-time hire would have led, you reported directly to a senior leader, you owned a workstream that produced a shipped feature or a published research note), the bullets carry that signal. The title still stays as "Intern."

6 filled examples by scenario

The six examples below cover the most common internship-listing scenarios. Each example shows the section header, the date format, the title line, and the bullets that translate the internship into hiring signal. Use them as a template, not as copy-paste text.

INTERNSHIPS

Marketing Intern, Acme Outdoor Apparel
Boulder, CO · Jun 2025 – Aug 2025

• Owned weekly Instagram and TikTok content calendar (~24 posts/week);
  organic engagement rate rose from 2.1% to 3.4% across the 10-week cohort.
• Analyzed paid-search keyword performance in Google Ads for the "trail
  running" product line, surfacing 7 negative-keyword candidates that the
  team adopted (CPC dropped 11% on the next refresh).

EXPERIENCE

Software Engineering Intern, Stripe
San Francisco, CA · Jun 2025 – Aug 2025

• Shipped a billing-reconciliation microservice (Go, gRPC, Postgres)
  used by the merchant-finance team; reduced manual reconciliation
  workload by an estimated 11 hours/week per analyst.
• Authored 6 unit-test suites and 2 integration-test suites; code
  reviewed and approved by 4 senior engineers before merge to main.
• Selected as 1 of 3 interns (cohort of 28) to present capstone work
  to the VP of Engineering; recommendation adopted into Q4 roadmap.

Software Engineering Intern, Carta
San Francisco, CA · Jun 2024 – Aug 2024

• Migrated 47 internal dashboards from Tableau to Metabase as part of
  the BI-cost-reduction initiative; total annual savings ~$38K.
• Built a Python data-validation script that flagged 312 missing-field
  records across the cap-table backfill, unblocking a customer migration.
• Authored a developer onboarding guide (24 pages) that became the
  default reference for the 9 incoming Summer 2025 interns.

Computer Science Tutor (Part-Time), University of Michigan CSE
Ann Arbor, MI · Sep 2023 – May 2025

• Held weekly office hours for EECS 281 (Data Structures &
  Algorithms); supported ~40 students per term across two academic years.
• Wrote 14 supplemental practice problem sets used by the course staff
  for the 2024 and 2025 cohorts.

EXPERIENCE

Summer Analyst, Goldman Sachs – Global Markets, Equities Division
New York, NY · Jun 2025 – Aug 2025

• Rotated through cash equities, derivatives, and electronic trading
  desks; built a Python pricing tool for a basket-trade workflow now
  deployed on the desk and used on ~$420M of daily flow.
• Authored 4 client-ready morning notes on consumer-staples earnings;
  one note circulated firmwide and cited in a senior salesperson's
  morning call to 14 institutional accounts.
• Top-quartile rating in the 47-person Equities summer class; received
  full-time return offer for Jul 2026 start.

RESEARCH

Undergraduate Research Assistant, Wharton Finance Department
Philadelphia, PA · Sep 2024 – May 2025

• Co-authored working paper on post-IPO insider trading patterns
  (data: WRDS, Compustat); presented at the Wharton Undergraduate
  Research Symposium, April 2025.
• Cleaned and merged 18 years of SEC Form 4 filings (~840K rows) into
  a panel dataset now in use by 3 follow-on research projects.

EXPERIENCE

Software Engineering Intern, Mid-Sized FinTech Startup
Remote · Mar 2026 – May 2026 (12-week paid internship)

• Shipped a customer-facing transaction-search feature (React, Node.js,
  PostgreSQL) used by ~6,200 weekly active users; reduced support tickets
  on "can't find transaction" by 34% over the first month after release.
• Wrote 9 Cypress end-to-end tests and 22 Jest unit tests; raised test
  coverage on the consumer-app repo from 41% to 58%.
• Paired with senior engineers on 14 PRs; received written feedback
  praising code clarity, test discipline, and willingness to ship.

Software Engineering Fellow, Hack Reactor Full-Time Immersive
Remote · Dec 2025 – Mar 2026

• Completed 800-hour full-stack JavaScript program (React, Node.js,
  PostgreSQL, Express, Docker); graduated in top 10% of the 38-person
  cohort based on final-project assessment.
• Capstone: built a multi-tenant SaaS scheduling app (React + Node +
  Postgres) deployed on AWS; live demo passed all 12 instructor rubric
  criteria.

PRIOR CAREER

Senior Account Manager, Regional Marketing Agency
Atlanta, GA · 2019 – 2025

• Owned a $2.4M annual book of business across 14 mid-market clients;
  consistently delivered 110% to retention quota over six annual cycles.
• Transitioned to software engineering in Dec 2025 (see above).

INTERNSHIPS

Data Science Intern, Mid-Sized Health-Tech Company
Boston, MA · Jun 2025 – Aug 2025
(CPT-authorized, F-1 visa; OPT-eligible upon graduation May 2026)

• Built a patient-readmission prediction model (XGBoost, scikit-learn)
  on a dataset of 142K discharge records; held-out AUC 0.81, beating the
  prior logistic-regression baseline of 0.73.
• Containerized the model with Docker and integrated it into the
  internal MLOps pipeline; model served via FastAPI to the care-management
  team and now scores ~4,200 discharges/week.
• Authored a 14-page model card documenting features, fairness audit
  results across 6 demographic slices, and re-training cadence; adopted
  as a template for 3 follow-on models in the same group.

EXPERIENCE

Returnship Program Associate, Path Forward x Major Financial Institution
New York, NY · Feb 2026 – May 2026 (16-week structured returnship)

• Led the redesign of a quarterly client-portfolio review workflow used
  by 22 senior advisors; reduced average report-prep time from 4.5 hours
  to 1.8 hours per advisor.
• Built an internal dashboard (Tableau + Snowflake) tracking 6 client-
  experience KPIs across the wealth-management book; adopted into the
  monthly executive review pack.
• Mentored 2 junior analysts on financial-modeling best practice;
  received written feedback from the program sponsor recommending
  conversion to full-time hire upon program completion.

CAREER BREAK
Feb 2020 – Jan 2026 · Primary caregiver for two children; maintained
CFA charter active status and completed a Coursera Financial Modeling
specialization (Wharton, 2024) during the break.

PRIOR EXPERIENCE

Senior Wealth Manager, Boutique RIA
Greenwich, CT · 2012 – 2020

How ATS parsers handle internship entries

The five major ATS platforms parse internship entries differently, and the differences are large enough that the same internship can rank in the top 10% of a screen on one platform and the bottom 30% on another. The platform-specific behavior below is drawn from observed parser output across the Workday, Greenhouse, iCIMS, Lever, and Taleo engines.

The cross-platform rule that satisfies every major parser: include the literal "Intern" string in the title line, place the entry inside a section labeled either "Experience" or "Internships" (never a combined header), and use a consistent date format with month and year on both sides. That combination is the highest-compatibility configuration across all five platforms.

When NOT to list an internship

Internships earn their place on the resume by being recent, relevant, and stronger than what they would displace. Three scenarios cover the most common cases for omitting an internship.

• 5+ years past the internship with relevant full-time work. Once you have multiple years of full-time experience that uses the same skills the internship demonstrated, the internship adds nothing and consumes space. Drop it. The exception is a brand-name internship (Goldman Summer Analyst, Google STEP, Stripe SWE intern) which still earns one line in early-career applications up to roughly 7 years post-grad, after which it goes.
• Unpaid or course-credit-only with no shippable work. An unpaid internship that consisted mainly of shadowing or administrative tasks competes poorly against paid roles in the same field. When you have stronger paid roles to highlight, drop the unpaid entry. When the unpaid internship produced a concrete deliverable (a published research note, a launched feature, a shipped report), keep it and use the deliverable as the primary bullet.
• High school internships once you have college-level experience. By sophomore year of college, any college-level internship displaces a high-school internship. The narrow exception is a high-school internship at an institution the recruiter will recognize (Smithsonian, NASA, a federal agency) and that produced a concrete artifact, in which case it can earn one line in college-application resumes and early summer-internship applications. By full-time recruiting season, high-school entries should be gone.

Common internship-listing mistakes

The eight mistakes below cover most of the internship-listing errors that recruiters cite when they pass on otherwise strong early-career resumes. Each is easy to fix and high-leverage relative to the time it takes.

• Listing every task instead of selecting 3 to 4 high-signal ones. The instinct to document every responsibility hurts more than it helps. A bullet that says "Also performed general administrative duties as needed" signals that the candidate could not identify the work that mattered.
• Omitting the tools and tech stack. ATS systems match on tool names. A bullet that says "Built a data pipeline" misses every recruiter screening on Python, SQL, dbt, Airflow, or Snowflake. Name the tools.
• Padding short internships with filler bullets. A 10-week internship with 6 bullets reads as overstated. Three or four strong bullets beat six padded ones every time.
• Mixing internship and part-time job dates without clarification. When a summer internship converted to part-time school-year work, stack the lines and label each (full-time summer cohort vs. part-time school year). Recruiters who see overlapping date ranges without explanation flag the resume for review.
• Listing "Intern" without the function. Always write "Marketing Intern," "Software Engineering Intern," or "Investment Banking Summer Analyst," never just "Intern." The function is the keyword the ATS filters on.
• Inflating titles. Promoting "Summer Intern" to "Summer Associate," dropping "Intern" to read as full-time, or rewriting an unpaid internship as "Project Manager" all qualify as misrepresentation. Recruiters back-channel references and ATS taxonomies penalize inflated titles.
• Burying internships under "Activities." An internship is professional experience, not an extracurricular. Placing it under "Activities" tells the recruiter that the candidate does not value the experience and the recruiter should not either.
• Skipping the company description for unknown firms. When the internship was at a small or regional firm, a one-line italicized company descriptor under the title helps the recruiter calibrate scope. "Acme Outdoor Apparel, $42M annual revenue, ~210 employees, direct-to-consumer outdoor brand" takes one line and prevents the recruiter from miscoding the role as a hobby project.

Fixing these mistakes typically raises a recruiter's internal "would-interview" rating on an entry-level resume by a full point on the standard five-point scale. The fixes take an hour. Test your resume free to see which internship-listing patterns are pulling your score down and what to change before the next application.

Frequently asked questions