How to Write MIT Short Answers: Hacker Voice and Build/Make/Break Stories Across Five 150-200 Word Prompts
Published on May 10, 2026
MIT's five short answers (150-200 words) follow completely different rules from other schools' supplements: no rhetoric, no metaphors, and a hacker tone. This article breaks down good and bad examples for each prompt and how to write build/make/break stories.
How to Write MIT Short Answers: Hacker Voice and Build/Make/Break Stories Across Five 150-200 Word Prompts
Published on May 14, 2026
Every November, when students begin writing the MIT supplement, I say the same thing:
"Forget every personal statement, Why X essay, and diversity essay you have written over the past three months. MIT's rules belong to a different world."
Students usually look confused. After all, for the previous three months I have been teaching them show don't tell, how to use metaphor, how to build a narrative arc, how to develop voice. In MIT short answers, none of those techniques apply.
MIT's supplement consists of five short answers, each 150-200 words. Its aesthetic philosophy is the exact opposite of Harvard / Yale / Princeton: MIT wants hackers, not poets. Poetic sentences, literary metaphors, profound reflections: at MIT, these are red flags. The MIT adcom wants answers that are specific, quantifiable, technical, and direct. After 15 years of working with MIT applicants, I have coached 60+ MIT applicants, 18 of whom were ultimately admitted. This article breaks down the hacker voice behind these five prompts, good and bad examples for each question, and the mistakes Taiwanese students most often make.
1. The Hard Specs of the MIT Supplement
First, here are the five short answers from the 2024-25 application cycle:
#
Prompt
Word count
1
We know you lead a busy life... we'd like to know more about something you do for the pleasure of it.
150 words
2
Describe the world you come from (for example, your family, school, community, city, or town). How has this world shaped your dreams and aspirations?
225 words
3
MIT brings people with diverse backgrounds together to collaborate. Describe one way you have collaborated with others to learn from them, with them, or contribute to your community together.
225 words
4
Tell us about a significant challenge you've faced or something that didn't go as planned that you feel comfortable sharing.
225 words
5
How has the world you come from—including your opportunities, experiences, and challenges—shaped your dreams and aspirations?
(integrated with prompt 2)
Plus the opening short questions:
Department / field interest
Why MIT specifically (50 words)
High school activities one-liner
The most important difference: MIT short answers contain no personal statement-style narrative essay. Each answer responds directly. There is no hook, no thesis, and no reflection paragraph.
2. MIT Voice: Hacker, Not Poet
The biggest difference between MIT adcom reading preferences and those of other top universities is this: they are more likely to come from an engineering mindset than a humanities one.
Harvard / Yale Voice
MIT Voice
Literary metaphor
Concrete object
"I was struck by..."
"I built X using Y to solve Z"
Narrative arc
Direct answer
Reflection > description
Description > reflection
Voice > content
Content > voice
Show don't tell
Just tell (specifically)
Lyrical paragraphs
Bulleted facts
Rich adjectives
Few adjectives
Slow opening
Main point in sentence 1
MIT adcom's internal catchphrase: "Show me what you make," not "Show me how you feel."
This is also why MIT short answers are short. They do not want to read long essays. 150 words is a paragraph, not an essay.
3. Build / Make / Break Stories: The Core Currency of MIT Essays
After 15 years of working with MIT applicants, I have found that all admitted students share one pattern: their short answers contain at least three "build / make / break" stories.
What is a build / make / break story?
Type
Definition
Example
Build
You create something from scratch
Building an automatic plant-watering device with Arduino
Make
You modify / rebuild / remake something
Turning an old washing machine into a rotating base for an astronomy telescope
Break
You take something apart to understand how it works
Disassembling your grandmother's vacuum tube radio
Why MIT likes build/make/break stories: they naturally show a hands-on spirit without requiring the student to say "I am hands-on."
Compare:
Weak (no build/make/break):
I love science. From a young age, I have been fascinated by how things work. Physics is my favorite subject because it explains the universe.
Strong (with build/make/break):
I disassembled my grandmother's 1973 Toshiba tube radio when I was 14. The 6BQ5 power output tube was dead. I learned how RF amplifiers work by trying to replace it (NOS tubes cost $40 on eBay; I bought a Chinese clone for $8 and it sounded fine).
4. Prompt 1 (Pleasure, 150 Words): How to Write "For Fun"
Prompt 1 is the most important question in the MIT supplement. It is not testing your "achievement." It is testing what you are willing to do even when there is no external reward.
Cooking one dish each week that no one in your family has tried before
"I like music"
Stargazing / writing short sci-fi / designing board game rules
"I like spending time with my family"
Solving a tiny puzzle no one else cares about
"I like helping others"
Rule: your "pleasure" must have no award, no competition, and no resume value. If it belongs in the Activities section, it should not go in Prompt 1.
Prompt 1 Example Comparison
Weak example (150 words):
One thing I love doing for fun is reading. I love getting lost in a good book and exploring different worlds. Reading has expanded my horizons and taught me empathy. Some of my favorite authors include Haruki Murakami and Margaret Atwood. I particularly enjoyed reading "Norwegian Wood" because it taught me about love and loss. In college, I hope to continue reading widely across genres. Reading is my way of relaxing after a long day of schoolwork.
Problems:
0 specific details (which book, which page, which scene)
"Taught me empathy" is a cliché
"In college, I hope to continue" is wasted space
"Relaxing after a long day" is generic
142 words wasted
Strong example (148 words):
I read aloud to my dog. Specifically: dense physics papers I don't understand. Last month it was Susskind's lecture notes on black hole information paradox. The dog (Bagel, 12, golden retriever, mostly deaf) doesn't care, but the act of reading aloud forces me to slow down. I noticed I skip the math when I read silently—reading aloud, I can't. >Bagel's job is to fall asleep on my feet. My job is to stop at every "therefore" and ask whether I actually believe it. >Last week I got through eq. 4.23 of the paper before Bagel snored. I went back, redid the algebra. I had skipped a sign error. Bagel got a treat. The paper got a margin note: "trust no professor who writes 'clearly'." >This is how I read.
Why it works:
Specific dog (Bagel, 12, golden retriever, mostly deaf)
Specific paper (Susskind, eq. 4.23)
Concrete mechanism (reading aloud catches errors)
Self-deprecating humor ("trust no professor who writes 'clearly'")
Absolutely no "This taught me X"
5. Prompt 2 (The World You Come From, 225 Words): Avoid the Lyrical Autobiography
Prompt 2 looks like a diversity essay, but it should be written differently. MIT does not want you to write "I am proud of my culture." It wants you to write how this world specifically shaped what you want to do.
Strong angle
Weak angle
One concrete setting (kitchen / factory / temple entrance)
"My family is very supportive"
A specific action / sentence from a family member
"Taiwanese culture values education"
A physical feature of a community
"Taipei is a vibrant city"
Connection to a specific thing you want to do
Connection to generic "I want to make a difference"
Prompt 2 Example (220 words, Taiwanese student)
My father runs a small precision machining shop in Taoyuan. The shop has six CNC mills, two lathes, and a 25-year-old Kitamura horizontal machining center that he keeps because, in his words, "it still does things the new ones can't." >I grew up watching him chase 5-micron tolerances. The room had to be exactly 20°C—machine warm-up took 90 minutes—and he would re-zero the spindle before every batch. When I was eight, I asked why he didn't just buy a newer machine. He said: "The machine doesn't know what you want. You teach it. Old or new doesn't matter." >I think about this when I write code. The compiler doesn't know what you want. You teach it. The bug isn't in Python—the bug is in your assumptions about Python. >My father's shop also taught me that engineering is largely about what you don't see: the 0.003mm of thermal expansion across the part, the 7-second pause between roughing and finishing passes, the operator's intuition about coolant flow that no manual mentions. I want to study mechanical engineering at MIT because the field I'm entering rewards exactly this kind of attention—and because MIT's 2.007 final project culture treats hands-on iteration as the curriculum, not the extracurricular.
Paragraph 3: transfers insight from a physical workshop to coding
Paragraph 4: abstract insight + connection back to a specific MIT course (2.007)
There is no sentence like "I am proud of my Taiwanese heritage." But after reading it, the adcom fully understands how Taiwan's manufacturing culture shaped this student.
The most common weak version of Prompt 3: turning it into a leadership story.
"As captain of the robotics team, I led 12 members to win the national competition. I learned that leadership requires..."
Problem: MIT does not care that you were captain. It cares what you concretely built/made/broke with other people.
Strong Collaboration Story
Weak Collaboration Story
You and 2-3 people got stuck together + the specific technical details of how you solved it
You led a team to win a championship
A partner taught you something you did not know
"Communication is key"
A productive disagreement
"We all worked together"
A specific division of roles
"Everyone contributed"
Prompt 3 Example (222 words)
Three weeks before our FRC regional, our Team 4253 swerve drive started skipping ticks on the encoder. We had 4 days. Hank (a junior, our mech lead) wanted to swap the motor. I thought it was a firmware issue. We argued in the pit at 11 PM with Mr. Liu (our mentor) refereeing. >We did both. Hank pulled the motor; I scoped the CAN bus. >The motor was fine. The CAN bus showed a 4ms gap every 800ms—exactly when the camera pipeline grabbed a frame. We had a thread-priority issue in our 2024 vision code that I had written. >Hank found this funny. (I had been certain it wasn't my code.) >We fixed it in two hours: I lowered the camera thread priority; Hank reassembled the swerve module while we ran tests. Then he made me explain what I did wrong, in detail, in front of the rookie team members—not to embarrass me, but because they would write similar code next year. >I learned two things. First: be willing to be the one who broke it. Second: collaboration isn't agreeing—it's both being willing to be wrong, and someone keeping the time. Hank kept the time that week. He still does. I want to find collaborators like him at MIT.
Breakdown:
Specific technical details (4ms gap, 800ms, CAN bus, thread priority)
Dialogue conflict ("We argued in the pit at 11 PM")
Self-deprecating ownership of error ("I had been certain it wasn't my code")
Specific role division (I scoped the bus, Hank pulled the motor)
Writes collaboration without writing leadership
7. Prompt 4 (Challenge, 225 Words): Don't Write About Death or Injury
Prompt 4 is the most dangerous question in the MIT supplement. Students most often turn it into a lyrical "overcoming hardship" essay.
MIT does not want:
Family member passes away → I became stronger
Sports injury → I learned resilience
Parents divorce → I matured
COVID lockdown → I learned self-discipline
MIT wants:
Strong challenge
Why it works
A project you attempted failed, with the failure mode described precisely
Shows engineering mindset
A math / coding problem you were stuck on for three months
Shows persistence + technical depth
A wrong judgment you made + how you corrected it
Shows self-awareness
A confrontation between you and a rule / system
Shows agency
Prompt 4 Example (219 words)
I spent 4 months trying to make a Raspberry Pi-based 24/7 bird identifier for my apartment's balcony. The hardware worked. The model didn't. >I had naively trained YOLOv5 on the eBird Macaulay Library dataset—500,000 images, mostly studio-quality, mostly North American. My balcony, however, is in Taipei, where 60% of the bird visitors are Light-vented Bulbul and Eurasian Tree Sparrow. Both species are massively underrepresented in eBird, both have plumage that varies seasonally, and both look identical to the model under harsh afternoon sun. >Day 47: model accuracy 41%. >I tried (in order): data augmentation, smaller model, larger model, transfer learning from a Taiwan-specific dataset I found in a TaiwanGBIF paper. None worked. >Day 92: I gave up on YOLO. The breakthrough was realizing I had been treating this as a classification problem when it was an annotation problem—my training labels were systematically wrong because I hadn't accounted for seasonal molting. I spent 3 weeks re-labeling 8,000 photos. Accuracy: 87%. >What I learned wasn't "perseverance." It was: when your model fails, suspect the data first, the architecture second, and yourself third. (Most engineering failures are #1. I was so sure mine was #2 that it took me 3 months to check #1.)
Breakdown:
The whole essay is a technical challenge, not an emotional challenge
Specific data (41%, 87%, 8,000 photos, day 47, day 92)
Self-deprecation + agency ("I was so sure mine was #2")
No "I learned perseverance." Instead, a precise engineering insight
8. Master Rule Table for All Five Short Answers
Rule
Explanation
Get to the point in sentence 1
No warm-up. MIT has no time
One specific detail every 50 words
Number / model / object name / person's name / time
Verbs > adjectives
"I built" not "I am builder-type"
No metaphors
"The canvas of my mind" gets rejected immediately
No thesis statement
MIT is not the SAT writing section
Bullets are allowed
MIT adcom likes bullets
Code blocks / equations are allowed
Encouraged if relevant
Avoid "I learned"
Use "I noticed," "I realized," "I now think" instead
Avoid passive voice
"X happened to me" → "I did X"
Avoid abstract nouns
"Perseverance, resilience, leadership" are all fatal words
9. Five Common Traps for Taiwanese Students
After 15 years of helping Taiwanese students apply to MIT, these are the disasters I see most often:
Trap 1: Treating cram school as a "passion"
"I love math, especially competitive math." → AMC / AIME / gifted math-science programs belong in the honors section. Do not write about exam-style math for Prompt 1.
Trap 2: Writing "My family values education"
"My parents value education" is something 100,000 Asian applicants could write. It is instantly generic.
Trap 3: Achievement-oriented collaboration
"I led my team to win." MIT does not care that you won. It cares how you debugged with other people.
Trap 4: Turning challenge into trauma
"My grandfather passed away during sophomore year." This belongs in the Common App Additional Info section, not MIT's challenge prompt.
Trap 5: Writing Why MIT inside the short answers
"I want to study at MIT because of its world-class faculty." That belongs in Why MIT (50 words). Do not repeat it in the short answers.
10. How to Write Why MIT (50 Words)
MIT gives you only 50 words for Why MIT. It is the shortest Why X in the United States.
Strong 50-word Why MIT
Weak 50-word Why MIT
One specific course / lab / culture detail
"World-class faculty"
Connected to your build/make/break
"Stunning campus"
Direct, with no wasted words
Wasting 10 words at the beginning with "I have always dreamed of MIT"
Example (49 words)
MIT's 2.007 final project—building a custom robot to push hockey pucks—is the only undergraduate ME course I've found where the curriculum is the iteration loop. I want to take it with Prof. Amos Winter, whose Global Engineering Initiative builds prosthetics in India using the same constraints my dad's shop respects.
Breakdown:
Specific course (2.007)
Specific professor (Winter)
Specific program (Global Engineering Initiative)
Connects back to Prompt 2 (dad's shop)
11. Short Essay Format Tips: Paragraphs, Bullets, and Equations Are Allowed
MIT short answers allow and encourage non-prose formats. Students often overlook this.
Acceptable formats:
Bullet list:
Three things I do every weekend:- Re-tune my homebuilt theremin (the heterodyne oscillator drifts)- Walk the same 4.2 km route through Daan Park (counting Brown Shrike sightings)- Read one chapter of Gravitation (Misner-Thorne-Wheeler, 1973 edition)
Equation / code:
The bug was here:```pythonfor i in range(len(arr)): if arr[i] == target: return i + 1 # off by one```I had been awake 19 hours and convinced this was the language's fault. (It was not.)
Number-prefixed paragraphs:
1. Day 1, I thought it was the motor.2. Day 4, I thought it was the firmware.3. Day 12, I realized it was the cable.
These formats look strange in a Harvard / Yale supplement. At MIT, they look normal.
12. Conclusion: MIT Is a School for Builders
After 15 years of real application work, the final reminder I give every MIT applicant is this:
When writing MIT short answers, imagine you are writing a lab report with your robotics partner, not turning in homework to your English teacher.
MIT adcom reads 28,000 applications a year. They are tired of reading "I have always been passionate about science." When they read that a student specifically wrote, "I disassembled my grandmother's vacuum tube radio because the 6BQ5 power output tube was dead," they remember it.
MIT is the school on earth that cares most about what you make. Turn your short answers into five snapshots of your maker portfolio, not five paragraphs of lyrical autobiography.
If the adcom finishes reading and thinks, "This kid will build a 3D printer in their first week at MIT," you have won.
Five short answers, five build/make/break stories. Hacker voice, not poet voice—always.
