What Not To Do

12. What Not To Do

Fatima, several risks in your current profile are not about ability—they are about how admissions readers might interpret incomplete or poorly framed information. Selective universities evaluating linguistics and computational linguistics applicants are looking for evidence of analytical depth, quantitative preparation, and technical ownership. When those signals are unclear, strong candidates can accidentally present themselves as less prepared than they actually are.

The following pitfalls are the ones most likely to weaken your application if they are not handled carefully.

1. Do Not Frame Language Preservation Work as Purely Service-Oriented

If you are involved in language preservation, documentation, or community language work, a major mistake would be presenting it only as humanitarian or cultural service. Admissions readers evaluating computational linguistics want to see the technical systems behind the work.

If the application emphasizes only helping communities, cultural appreciation, or volunteering, it risks being interpreted as social engagement rather than computational scholarship. The committee discussion flagged this distinction as especially important for technical programs.

A purely service narrative creates two problems:

• It removes the computational element from the work.
• It places the activity in the “community service” category instead of “technical research or engineering.”

For computational linguistics programs, that framing mistake significantly weakens the intellectual signal of the activity.

2. Do Not Leave the Technical Infrastructure Invisible

Closely related to the previous issue: avoid describing projects in ways that hide the systems, tools, or technical frameworks behind them.

If you built datasets, worked with transcription pipelines, used coding tools, or interacted with linguistic data systems, failing to mention those elements will cause admissions readers to underestimate the rigor of the work.

Many applicants unintentionally write descriptions like:

• “Worked on documenting endangered languages.”
• “Helped preserve linguistic resources.”

Descriptions like these sound meaningful but technically vague. For a field like computational linguistics, vagueness signals lack of depth—even when the work was actually sophisticated.

3. Do Not Let Collaborative Work Hide Your Personal Contribution

Admissions readers must understand what you personally built, analyzed, coded, or designed. If an activity description reads like a team summary rather than an individual contribution, it creates ambiguity.

This is especially risky in:

• Research projects
• Group computational projects
• Collaborative linguistic fieldwork
• Team data or NLP projects

Statements like “our team analyzed language data” or “we built a linguistic model” create a major interpretation problem: admissions officers cannot tell whether you were leading technical work, assisting, or observing.

If your personal role is unclear, committees typically assume the contribution was limited.

4. Do Not Use Collective Language That Obscures Ownership

Even when your contribution was substantial, wording can unintentionally dilute it. Overuse of “we,” “our project,” or “our research” weakens the clarity of your intellectual role.

This is one of the most common mistakes strong students make in technical applications. The application reader only sees a few lines describing each activity. If those lines fail to isolate your contribution, your impact becomes invisible.

Avoid language patterns that make your role indistinguishable from the group.

5. Do Not Assume Admissions Readers Will Infer the Technical Depth

In interdisciplinary fields like computational linguistics, reviewers often come from different backgrounds—computer science, linguistics, mathematics, or cognitive science.

If your activity descriptions rely on readers to “fill in the gaps” about the computational aspects, that assumption may fail. Reviewers will not infer complexity that is not clearly stated.

Ambiguity almost always works against the applicant.

6. Do Not Allow Your Transcript to Appear Light in Mathematics

Computational linguistics sits at the intersection of language and quantitative modeling. Because of that, admissions committees pay very close attention to mathematical preparation.

If advanced math courses were available at your high school but your transcript does not show progression into them, the application may raise concerns about readiness for computational coursework.

You have not provided your course list yet. Without that information, it is impossible to verify whether your math trajectory signals strong preparation. This gap needs careful attention.

If admissions readers cannot clearly see rigorous quantitative preparation, they may categorize the applicant as “linguistics-focused but not computationally prepared.”

7. Do Not Assume a High SAT Automatically Signals Quantitative Depth

Your SAT score of 1520 is strong, but standardized tests do not replace evidence of sustained mathematical coursework.

Selective programs—especially places like MIT—look for long-term academic preparation, not just testing strength.

If the transcript does not clearly show advanced math progression, a strong SAT score alone will not eliminate that concern.

8. Do Not Leave Coursework Information Missing in the Application Narrative

Right now, you have not provided details about:

• AP / IB courses
• Advanced math classes
• Advanced computer science courses
• Advanced linguistics coursework (if available)

If these exist but are not contextualized anywhere in the application narrative, readers may underestimate the rigor of your academic preparation.

Missing academic context often hurts applicants more than weaker credentials.

9. Do Not Let Interdisciplinary Interests Look Unfocused

Computational linguistics sits between disciplines, which can be powerful—but it also creates a presentation risk.

If your activities appear split between “language interests” and “technical interests” without clear integration, the application may look scattered instead of interdisciplinary.

This happens when:

• Language-related work looks purely cultural or community-based
• Technical work appears unrelated to language
• The application never explicitly connects the two

When this happens, admissions readers may struggle to see the intellectual thread tying the application together.

10. Do Not Use Activity Descriptions That Sound Like Job Duties

Another subtle risk is describing work in a task-oriented way rather than an analytical or intellectual way.

For example, phrases that sound like job responsibilities—rather than technical or research contributions—can unintentionally downplay the complexity of your work.

This is especially common in research or data-heavy projects where the student actually performed analytical work but describes it in administrative language.

11. Do Not Let Ambiguity Persist Into Recommendation Letters

Teacher or mentor recommendations that describe you as “helpful,” “dedicated,” or “interested in languages” but fail to mention technical reasoning or analytical ability can reinforce the wrong narrative.

If recommenders do not understand that your intended path involves computational analysis of language, their letters may emphasize the wrong strengths.

This can unintentionally position you as a humanities-focused applicant rather than a computational one.

12. Do Not Wait Until Senior Fall to Clarify Technical Identity

Junior year and the summer before senior year are when your academic narrative solidifies. Waiting until application season to clarify your computational role in projects is risky.

If descriptions, documentation, or recommendation context are vague when applications are written, there may not be time to correct the narrative.

Ambiguity compounds quickly once applications are submitted.

Risk Monitoring Timeline (Junior Year → Application Season)

Month	Key Pitfalls to Avoid	Checkpoint
March–April	Leaving math coursework or technical preparation unclear	Confirm your transcript clearly reflects quantitative rigor
May	Allowing project descriptions to remain vague about your role	Document your individual contributions to collaborative work
June	Framing language work purely as service	Identify the computational or analytical systems involved
July	Letting interdisciplinary interests appear disconnected	Align language and computational themes (see §06 Essay Strategy)
August	Submitting activity descriptions that hide technical depth	Rewrite activity entries with precise contribution language
September	Recommenders emphasizing the wrong strengths	Ensure recommenders understand your computational linguistics focus

If these interpretation risks are avoided, your academic profile—3.92 GPA and 1520 SAT—will be evaluated on the strengths it already contains rather than being weakened by presentation issues.