What Not To Do

12 Things That Can Quietly Undermine Your Application

Alex, for highly selective computer science programs like Stanford, MIT, and Georgia Tech, strong students are rarely rejected because of a single obvious flaw. Instead, applications lose strength through subtle patterns that make the profile look common, unclear, or inflated. The committee discussion surfaced several risk areas that applicants with your academic profile frequently run into. Avoiding these pitfalls is just as important as adding new achievements.

1. Letting Test Scores Carry Too Much of the Application

Your SAT score of 1520 and GPA of 3.92 are excellent, but elite CS programs routinely see applicants with similar or stronger academic metrics. One of the most common mistakes strong students make is assuming these numbers will distinguish them on their own.

If the rest of the application reads like a list of classes and activities without clear intellectual depth, admissions readers often see it as academically strong but not uniquely compelling. Treat your scores as a baseline credential, not the centerpiece of your narrative.

2. Listing Leadership Titles Without Explaining the Technical Work

The committee flagged a frequent pattern among CS applicants: titles such as “captain,” “lead programmer,” or “founder” appearing in the activities list without concrete technical explanation.

If an activity description emphasizes hierarchy rather than engineering substance, admissions readers may assume the role was managerial rather than technical. For CS applicants especially, vague leadership descriptions weaken credibility.

Any leadership claim that is not tied to real engineering work can appear inflated.

3. Presenting Research Without Context

Many applicants mention research or publications without clarifying key details such as:

• What the research actually did
• What your personal contribution was
• Whether the publication venue is selective or informal

If your application references research but does not clearly explain these elements, admissions officers may treat it cautiously. In some cases, poorly explained research signals can hurt credibility more than they help.

You have not provided details about research activities in the information shared for this plan. If such work exists, failing to contextualize it would be a major risk.

4. Keeping Technical Work Invisible

Another issue the committee highlighted is “invisible work.” Many students build impressive technical projects that never leave their personal computer.

From an admissions perspective, private work is extremely difficult to evaluate. If projects are not documented, shared, demonstrated, or explained publicly in some form, readers cannot gauge their impact or sophistication.

Invisible projects often end up functioning like undocumented claims rather than verifiable accomplishments.

5. Writing Essays That Sound Like a Generic “Future Tech Leader”

Computer science applicants frequently fall into a predictable essay pattern: describing how technology will change the world and how they want to be part of that change.

Admissions readers at Stanford and MIT encounter thousands of variations of this theme each year. When essays lean heavily on broad technological optimism instead of personal intellectual curiosity, they tend to blend together.

This is especially risky for applicants with strong technical profiles because the essays are expected to reveal how you actually think about problems.

(See §06 Essay Strategy for a deeper explanation of how to avoid this.)

6. Submitting an Activities List That Looks Overcrowded but Shallow

Another frequent issue is the “overstuffed” activities section: many clubs, competitions, or organizations listed with minimal involvement.

You have not provided your full activities list yet. Without that information, it is impossible to assess depth. However, a long list of short-term or lightly involved activities often signals résumé-building rather than genuine engagement.

Selective CS programs typically respond more positively to depth and sustained commitment than to sheer quantity.

7. Overclaiming Impact

Admissions readers quickly notice exaggerated impact statements. Phrases like “revolutionized,” “transformed,” or “led a large initiative” can raise skepticism if the scale of the work is unclear.

When impact claims are vague or inflated, the reader often discounts the activity entirely.

Specific evidence tends to matter far more than dramatic wording.

8. Ignoring the Importance of External Validation

For technically oriented applicants, outside recognition often helps admissions readers evaluate the level of work being done.

In Washington State, competitions and regional academic events can serve as signals of technical ability. However, simply participating without clear outcomes rarely carries weight.

For example, competitions like science fairs, math contests, or programming competitions are most meaningful when the results demonstrate measurable distinction. Listing participation alone typically has limited admissions impact.

9. Assuming Admissions Readers Understand Your Technical Work

Highly technical students sometimes write activity descriptions that read like internal documentation rather than explanations.

Admissions officers are intelligent generalists, not necessarily specialists in machine learning, distributed systems, or advanced algorithms. If descriptions rely heavily on jargon, the significance of the work can be lost.

When readers cannot understand what you actually built or solved, the accomplishment becomes difficult to evaluate.

10. Treating Georgia Tech as a “Safety” School

Even though the earlier evaluation categorized Georgia Tech as a stronger probability than the other two schools, it remains a highly selective CS program.

A common mistake is putting significantly less effort into essays or application presentation for schools perceived as more attainable. That approach often backfires, especially for competitive technical majors.

Every school on your list requires a carefully crafted application.

11. Waiting Too Long to Prepare Application Materials

Many juniors underestimate how much time strong applications require. Essays, activity descriptions, and recommendation planning often take months to refine.

When students start too late—usually early fall of senior year—they end up submitting rushed materials that fail to capture the depth of their work.

This timing problem is one of the most common preventable weaknesses in otherwise strong applications.

12. Leaving Critical Information Out of the Application

Another risk is assuming admissions readers will infer things that are never explicitly stated.

If an application does not clearly communicate:

• What you built
• What your role was
• What the measurable outcome was

then those details effectively do not exist from the reader’s perspective.

Right now, several parts of your profile are not provided in the information available for this plan—such as your course rigor, extracurricular activities, awards, and technical projects. Leaving those areas underdeveloped or poorly documented would significantly weaken an otherwise strong academic profile.

Risk-Management Timeline (Junior Spring → Senior Fall)

Month	Pitfall to Watch	Preventive Check
March	Invisible work	Audit which technical activities or projects currently lack public documentation.
April	Weak activity descriptions	Review whether each activity explains concrete technical work rather than just titles.
May	Research ambiguity	Ensure any research mentions clearly describe your contribution and the publication context.
June	Generic narrative	Begin brainstorming essays (see §06 Essay Strategy for approach).
July	Overcrowded activities section	Evaluate whether your activities list shows depth or just quantity.
August	Technical jargon in descriptions	Rewrite activity descriptions so a non-specialist reader can understand them.
September	Inflated impact language	Replace vague claims with measurable outcomes.
October	Uneven school effort	Confirm that every application—including Georgia Tech—has fully developed essays.

The strongest applicants avoid these mistakes not by adding endless activities, but by presenting their existing work with clarity, credibility, and depth. Preventing these pitfalls ensures that your academic strength actually translates into a compelling admissions narrative.