What Not To Do
12. What Not To Do: Critical Pitfalls That Will Sink Your Application
Alex, this section may be the most important one you read. Every mistake listed below is drawn directly from patterns observed in how admissions committees evaluated your profile. These are not abstract warnings — they are specific to your application as it stands today.
---Pitfall #1: Do Not Assume "Excellent but Well-Rounded Technical" Is Enough
This is the single most dangerous assumption you can make, Alex. Your profile — a 3.92 GPA, 1520 SAT, Computer Science major — is strong on paper. But at Stanford, MIT, and Georgia Tech, it lands in the most saturated applicant pool in American higher education. Both review committees independently flagged your profile as "substitutable" — meaning every individual element has direct analogs in dozens of other applicants in the same round.
Here's what that looks like in practice:
| Your Element | How Many Others Have It | Why It Doesn't Differentiate |
|---|---|---|
| 3.92 GPA | Thousands in the CS pool | Strong but not a ceiling-breaker; many admitted students are 3.95+ |
| 1520 SAT | Well within the middle 50% at all three targets | Meets the threshold but provides no competitive edge |
| CS major intent | The single most popular declared major at Stanford and MIT | Places you in the deepest, most competitive sub-pool |
What this means: Do not write your application as if being a "strong CS student" is your thesis. That is a category, not a differentiator. Your essays, activities, and framing must answer the question: "Why this specific person and not the 200 other applicants who look nearly identical on paper?"
---Pitfall #2: Do Not Add More Activities in the Same Technical Lane
Alex, if your instinct right now is to sign up for another robotics team, join a second ML research group, or start yet another coding-adjacent extracurricular — stop. This is the most common strategic error high-achieving CS applicants make, and it will actively hurt you.
Your profile has been flagged for over-coherence — everything points in one direction (technical, CS, STEM) with insufficient dimensionality. Adding more of the same deepens this problem rather than solving it.
| ❌ Do NOT Do This | ✅ Instead, Consider This |
|---|---|
| Join another hackathon team | Lead a non-technical initiative (community organizing, arts, tutoring) |
| Add a second research internship in CS | Apply CS skills to an unexpected domain (public health, music, civic engagement) |
| Start a "coding for kids" club (overdone) | Pursue something that reveals a completely different facet of who you are |
| List every GitHub project you've touched | Curate 1–2 projects with measurable real-world impact |
Admissions officers at Stanford and MIT are not building a class of one-dimensional technologists. They want people who bring intellectual range. Your activities list should make a reader say "I didn't expect that from a CS applicant" — not "this is exactly what I expected."
---Pitfall #3: Do Not Leave the Additional Activities Section Blank or Treat It as Optional
Alex, MIT's review committee specifically flagged that leaving the Additional Activities section empty or underdeveloped is leaving points on the table. This is not a throwaway field. At MIT in particular, readers use this section to gauge dimensionality, intellectual curiosity outside your primary lane, and whether you'll contribute to residential life beyond the lab.
What not to do:
- Do not leave it blank because you think your main activities "speak for themselves"
- Do not fill it with padding activities you did for a week
- Do not list more technical activities here — this is your chance to show breadth
- Do not assume this section isn't read carefully — at MIT, it is
Since you have not provided your full activities list yet, Alex, I cannot assess what you currently have here. You should add your complete extracurricular profile so we can evaluate whether this section is strategically optimized or dangerously thin.
---Pitfall #4: Do Not Overstate Your Research Role
This is a credibility trap that destroys applications, Alex, and it is particularly acute for CS applicants who have done research under a faculty PI. Here is the rule:
Your application's description of your research contribution must be independently verifiable by your recommendation letter.
If you claim intellectual leadership — that you designed the methodology, originated the research question, or drove key results — but your PI's recommendation letter describes you as a capable lab member who executed assigned tasks well, you have created a credibility gap. Admissions readers at Stanford and MIT are expert at detecting this mismatch. They read thousands of these pairings every cycle.
| What You Claim | What the Letter Says | Committee Reads It As |
|---|---|---|
| "I led the research direction" | "Alex was a diligent contributor" | Exaggeration → credibility concern across entire application |
| "I co-developed the approach" | "Alex helped implement our method" | Mild inflation → reader discounts your other claims too |
| "I contributed to implementation and analysis under Dr. X's guidance" | "Alex was a diligent contributor who handled implementation and analysis" | Honest and aligned → builds trust in everything else you wrote |
Action step: Before you write your activities descriptions, ask your PI what they plan to say about your role. Align your language to match or slightly understate what they'll write. An honest, well-aligned research description is worth ten times more than an inflated one.
---Pitfall #5: Do Not Rely Purely on Narrative Strength to Differentiate
Alex, you are applying to schools where every serious applicant has a compelling personal narrative. A beautifully written essay about your passion for CS, a heartfelt story about what technology means to you, a well-crafted "why this school" essay — these are necessary but not sufficient. They are table stakes.
In applicant pools where narrative quality is uniformly high, what forces a committee to act — to move you from "maybe" to "admit" — are concrete proof points:
- Competition results: Specific placements, not just "participated." Given your CS focus and Washington State location, results from events like the Congressional App Challenge (Districts 7/9), UW Math Olympiad, or WSSEF carry real signal.
- User metrics: If you built an app or tool, how many people used it? What problem did it solve? "Built an app" is a story. "Built an app used by 500 students at my school to schedule study groups" is evidence.
- Adoption data: Did anyone outside your immediate circle use, reference, or build upon your work? Was your code forked? Was your project covered by local media?
- Quantifiable outcomes: Revenue generated, users served, hours volunteered, people taught — numbers that an admissions reader can't argue with.
The test: For every major activity or achievement you plan to highlight, ask yourself: "Could a committee member verify this claim with a 30-second search or a single phone call?" If the answer is no, you are relying on narrative. Find the proof point or reframe the achievement around one you can substantiate.
---Summary: Your Anti-Pattern Checklist
| # | Pitfall | Risk Level | Your Status |
|---|---|---|---|
| 1 | Assuming "strong CS student" is a differentiator | 🔴 Critical | Currently at risk — profile is substitutable |
| 2 | Stacking more technical activities | 🔴 Critical | Activities not yet provided — assess immediately |
| 3 | Neglecting Additional Activities section | 🟠 High | Activities not yet provided — flag for review |
| 4 | Overstating research contributions | 🟠 High | Research details not provided — align with PI before writing |
| 5 | Relying on essays alone without proof points | 🔴 Critical | No competition results or metrics provided yet |
Alex, every one of these pitfalls is avoidable — but only if you address them before you start writing your applications. The strongest applicants to Stanford, MIT, and Georgia Tech are not the ones with the best stats. They are the ones who made the fewest unforced errors. Make sure you are not handing the committee a reason to say no.