How to Write About an Internship in Your MS SOP
An internship in an MS SOP gets one paragraph: one task you owned, one result, one lesson pointing at the degree. What Berkeley and UCSD ask. A rewrite.
How to Write About an Internship in Your MS SOP
A two-to-six-month internship gets one paragraph, not a section: one task you owned, one result you can state, and one thing it showed you that the MS will teach. UC San Diego's graduate division asks for this directly: "Briefly describe what you did in each experience."
The weak internship paragraph is easy to spot. It reads like the internship offer letter: "worked on backend development, collaborated with cross-functional teams, gained exposure to agile methodology." Those lines describe the role the company planned, not the work you did. In a US statement of purpose (SOP) for an MS, the reader needs the second. When your paragraph is drafted, a free Quick Review against the CS, AI and data SOP rubric reads it for what you produced and whether a reader could check it.
The UC Berkeley, UC San Diego, Purdue and Carnegie Mellon pages quoted below were checked on October 31, 2026. The three graduate-school pages state no cycle year; the Carnegie Mellon page lists Fall 2027 deadlines. Recheck your own program's SOP instructions before you submit. This page belongs to our graduate school essays hub.
What prompts ask about work and internships
| School | What its page says | What it tells you to write |
|---|---|---|
| UC Berkeley Graduate Division | "Work experience, especially if you had any kind of responsibility for testing, designing, researching, or interning in an area similar to what you wish to study in graduate school." | Relevance first: the internship counts most when it is "in an area similar" to the MS |
| UC San Diego Graduate Division | Lists "research experiences, internships, work experience" as examples, then: "Briefly describe what you did in each experience. Also, make sure to articulate what you have learned about the field and how those lessons stimulated you to pursue an advanced degree." | What you did, briefly, and what you learned that leads to the degree |
| Purdue Graduate School | "Relevant topics may include coursework, work and research experiences, internships, presentations, exhibits, publications, and community service." | Internships are one of several listed sources of preparation, not a required section |
| Carnegie Mellon School of Computer Science | "You should describe any relevant education, research, commercial, government or teaching experience." | "Relevant" again; commercial experience is named |
None of the four asks for a list of duties, a company description or the stipend. Two of them (Berkeley and Carnegie Mellon) put relevance first. Berkeley also has a separate line for applicants who worked after graduating: "company or non-profit, your work/design team, responsibilities, what you learned". That line is about full-time work, but its four items are a sound template for an internship too.
Our view: an internship earns its paragraph by what you did in it, not by the company's name. The basis: UC San Diego asks you to "describe what you did", and Berkeley weights work by your "responsibility for testing, designing, researching, or interning". The countercase: if you worked full time for a year or more after graduating, your work history may deserve more than one paragraph; our guide to an SOP with work experience covers that case.
What a two-to-six-month intern can claim
A short internship gives you a narrow claim. Make it precise rather than large.
| You can claim | You should not claim, unless it is literally true |
|---|---|
| One task you were assigned and finished | "Led the project" or "owned the product" |
| A change you made, with a before-and-after number | The team's or product's metrics as your result |
| A tool, test or review practice you learned on the job | "Industry expertise" |
| A problem you met and could not yet solve | "My solution was adopted company-wide" |
| What your manager asked you to do next | A pre-placement offer as proof of skill, without the work behind it |
The offer-letter test. Put your internship offer letter or the job posting beside your paragraph. Any sentence you could have copied from it describes the role, not you. Delete it, or replace it with what you actually did on that task.
How to name the company. Name it once, with a few words on what it does if a US reader would not know it: "at a 40-person logistics software company in Pune". If you signed a non-disclosure agreement, describe the kind of problem and your method, not the client, the data or the internal system names. A reader can credit "I cut the response time of a search endpoint" without knowing whose endpoint it was.
One internship or two? Your resume lists every internship. Your SOP picks the one that is "in an area similar to what you wish to study", in Berkeley's words. A second internship gets a clause only if it adds a different kind of evidence. Our guide to why an SOP reads like a résumé shows how to give the two documents different jobs.
Unpaid, virtual and certificate internships
Unpaid or paid makes no difference to the paragraph. None of the four pages above says anything about whether an internship was paid. Leave the stipend out.
Virtual internships. Say it was remote once, then write it like any other internship: the task, your result, what you learned. Remote work with a measurable deliverable is still work.
Training programs called internships. If your "internship" was a fee-paid program that taught a course and issued a certificate, describe it as what it was: a training course. If it included a real project with a result, write the project. If it was lectures and a quiz, it belongs in your preparation list at most, and our guide to mentioning NPTEL and Coursera courses in an SOP covers when a course earns a sentence.
Research internships at a university lab are a different document problem: a question, a supervisor and a letter. Our guide to a summer research internship in your SOP covers that case.
Constructed example: an eight-week backend internship
Constructed example, written by us, not a real applicant statement. Context (invented): Rohan Iyer, a final-year computer science student, did an eight-week backend internship at an invented logistics software company and is applying for an MS in computer science.
Before (61 words): "I completed an internship at a reputed software company where I worked as a Backend Developer Intern. I was responsible for developing REST APIs, writing unit tests, and collaborating with cross-functional teams. I gained exposure to Agile methodology, Git, Docker and AWS. This internship helped me understand how software is built in industry and strengthened my desire to pursue higher studies."
After (128 words): "During an eight-week internship at a 40-person logistics software company in Pune, I was assigned the order-search endpoint, which took 1.8 seconds at the 95th percentile. I traced most of that time to one query that ran once per order line, replaced it with a single join backed by a composite index, and confirmed with a load test of 5,000 requests that the 95th percentile fell to 420 milliseconds. My manager then asked me to check whether the fix held at three times the load, and I could not answer that with the tools I had. I could fix one query, but I could not yet reason about how the whole system behaves under load. That is the gap I want MS coursework in distributed systems to close."
Why the revision works:
- The task is singular and named: one endpoint, assigned to him. The offer-letter phrases are gone.
- The result has a baseline: 1.8 seconds to 420 milliseconds, measured by a stated test. A reader can ask "how did you measure it?" and the paragraph has already answered.
- The lesson is a gap, not a feeling. It ends on something the MS teaches, which is UC San Diego's "how those lessons stimulated you to pursue an advanced degree".
- The tools list is cut. Git, Docker and AWS go on the resume.
Two more steps belong to the full statement, not this paragraph. Rohan should name the actual distributed-systems courses at each program, checked on its own course pages. His career goals paragraph should then say what role this training leads to.
Check the internship paragraph
- Offer-letter test. Pass: no sentence could be copied from the offer letter or job posting.
- One task. Pass: the paragraph names one task you were assigned or chose.
- A number or a found limit. Pass: there is a before-and-after figure, a test result or a stated problem you could not solve.
- Relevance. Pass: the last sentence connects to something the MS teaches.
- Company line. Pass: the company is named once, with a few words of context if it is not widely known; no confidential details.
- Length. Pass: one paragraph. If it is two, cut the second or move it to the resume.
Questions about internships in an SOP
Should I mention a one-month internship?
Only if you finished something you can describe with a result. If the month was onboarding and shadowing, list it on the resume and leave it out of the SOP.
My internship is unrelated to the MS I am applying for. Should I include it?
Write only the part that transfers, in one or two sentences, or leave it out. Berkeley weights work "in an area similar to what you wish to study"; an unrelated internship needs a clear bridge to earn space.
Should I mention my pre-placement offer?
Our view: only if it explains a decision the reader will wonder about, such as why you are choosing the MS over a job you were offered. Then one clause is enough. The offer does not replace the work as evidence.
What if I signed a non-disclosure agreement?
Describe the problem type, your method and your result in general terms. Leave out the client, data and internal names. The reader needs to see what you did, not the company's secrets.
Should I link my internship code?
Usually you cannot, because it belongs to the company. If you have a public repository that reproduces the method on open data, our guide to GitHub links in a CS SOP covers where the link goes.
Get a free review of your statement of purpose
Get a free Quick Review of your statement of purpose against GradPilot's MS SOP rubric for computer science, AI and data. It reads what your statement shows you producing, whether a reader could check it, and whether your stated direction fits that evidence. Applying outside computing? The general MS statement of purpose rubric reads preparation, goals and program fit. Both start from the master's SOP review page.
More guides on what goes in an MS SOP:
- How to write about your final-year project in an SOP: the four facts and the team-credit test.
- Resume for MS in US: one-page fresher format: where the full internship list goes.
- Hackathons and competitive programming in an SOP: when a prize earns a sentence.
Sources
Retrieved October 31, 2026, except where noted.
- UC Berkeley Graduate Division, Writing Your Statements (no cycle stated): work experience including "interning", and the post-graduation work line.
- UC San Diego Graduate Division, Statement of Purpose (no cycle stated): internships as an example; "Briefly describe what you did in each experience."
- Purdue University Graduate School, How to Apply (no cycle stated): internships among relevant topics for the Academic Statement of Purpose.
- Carnegie Mellon School of Computer Science, Graduate Admissions (Fall 2027 deadlines listed): "relevant education, research, commercial, government or teaching experience."
Get feedback on your statement of purpose
Paste your draft. The free Quick Review shows what to fix against an admissions rubric before you submit.