How to Write the NCWIT Aspirations in Computing Essay

A strong essay usually does four jobs at once. It explains what shaped your interest in computing, what you have already done with that interest, what opportunity or resource gap stands between you and your next step, and what kind of person you are when you work, learn, and solve problems. If one of those pieces is missing, the essay often feels flat: impressive but impersonal, heartfelt but unproven, or ambitious but ungrounded.

Do not open with a thesis such as “I am passionate about computer science.” Start with a concrete moment instead: a bug you stayed up to fix, a robotics failure that forced a redesign, a classroom moment when you noticed who was excluded, a project that finally worked after several iterations. The point of the opening is not drama for its own sake. The point is to place the reader inside a real scene that reveals how you act.

As you plan, keep asking one question: So what? If you mention a club, project, course, internship, or challenge, explain why it mattered. What changed in your thinking? What responsibility did you take? What did the experience prepare you to do next?

Brainstorm Across the Four Material Buckets

Most applicants have more usable material than they think. The problem is not a lack of experiences; it is weak sorting. Brainstorm in four buckets before you outline.

1. Background: what shaped you

This is not a request for your whole life story. Choose only the parts that help the reader understand your path into computing. Useful material might include a class, family responsibility, community need, school limitation, mentor, first build, or a moment when you saw technology solve a real problem.

• What first pulled you toward computing, and why did it stick?
• What environment did you grow up or learn in?
• What barriers, constraints, or expectations shaped your path?
• What specific moment made computing feel useful, not just interesting?

Keep this section selective. One vivid detail is better than a broad autobiography.

2. Achievements: what you have done

This is where many essays become vague. Do not merely list activities. Show responsibility, action, and outcomes. If you built something, explain what it did. If you led, explain whom you led and what changed. If you competed, taught, researched, volunteered, or coded, name the stakes and the result.

• What projects, teams, courses, or initiatives best represent your work?
• Where did you solve a problem rather than just participate?
• What can you quantify honestly: users, hours, growth, funds raised, students taught, bugs fixed, events organized, prototypes tested?
• What did you learn when something failed or had to be redesigned?

If you have several achievements, choose the ones that reveal a pattern. The committee should see not random busyness, but a coherent direction.

3. The gap: why support matters now

Many applicants underwrite this section because they fear sounding needy. Instead, be precise and practical. What do you need in order to keep building? The answer might involve tuition, time, equipment, coursework, transportation, access to advanced opportunities, or the ability to reduce outside work and focus on study.

• What next step are you trying to reach?
• What stands in the way?
• How would scholarship support change your options in concrete terms?
• Why is this the right moment for investment in your growth?

The strongest version of this section connects need to momentum. You are not asking the reader to rescue a dream in the abstract; you are showing that support would help you continue work already underway.

4. Personality: who you are on the page

Committees remember people, not just résumés. Add details that reveal your habits of mind: curiosity, persistence, generosity, humor, discipline, or care for users and teammates. Personality often appears in small choices: the way you describe debugging, the student you mentored, the question you kept asking, the problem you could not ignore.

• How do you behave when a project gets hard?
• What values guide the way you build or collaborate?
• What detail would make this essay unmistakably yours?

A useful test: if you removed your name, could this essay belong to ten other applicants? If yes, it needs more specificity.

Build an Outline That Tells a Clear Story

Once you have material, shape it into a sequence with forward motion. A strong scholarship essay often works best in four or five paragraphs, each doing one distinct job.

1. Opening scene: begin with a concrete moment that reveals your relationship to computing. Keep it brief and active.
2. Context: explain what that moment meant in the larger arc of your development. This is where background belongs.
3. Evidence: show one or two achievements in enough detail that the reader can see your actions and results.
4. Need and next step: explain the gap between where you are and where you are trying to go, and how scholarship support would matter.
5. Closing reflection: end by connecting your past work to the kind of contribution you intend to make.

Within each body paragraph, use a simple internal logic: set up the situation, name your responsibility, describe what you did, and show the result. Then add reflection. That final move matters. A paragraph about building an app or leading a team is incomplete until you explain what the experience taught you about problem-solving, collaboration, access, or the kind of work you want to pursue.

Keep one main idea per paragraph. If a paragraph tries to cover your childhood, your coding club, your internship, and your financial need all at once, the reader will retain none of it. Clear transitions help: “That early interest became practical when…,” “I tested that commitment by…,” “Those experiences also exposed a limitation…,” “Support now would allow me to…”.

Draft With Specificity, Reflection, and Active Voice

When you draft, favor sentences that show a person doing something. “I organized a weekend workshop for 18 middle school students” is stronger than “A workshop was organized.” Active voice creates accountability and energy.

Replace broad claims with evidence. Instead of saying you are dedicated, show the late redesign, the repeated test, the student you kept tutoring, the feature you rebuilt after user feedback. Instead of saying you love technology, show what you made, fixed, improved, or questioned.

Use numbers when they are honest and relevant. Numbers create scale and credibility, but only if they clarify meaning. Good details include timeframes, team size, frequency, measurable outcomes, or the scope of a project. Do not force metrics into every sentence. One exact detail can do more work than five inflated ones.

Reflection is what turns activity into significance. After each major example, add two or three sentences that answer:

• What did this experience change in how I think?
• What did it reveal about the problems I want to solve?
• Why does it make me more ready for the next stage?

Your closing should not simply repeat your opening. It should show development. By the end of the essay, the reader should understand not only what happened to you, but what you intend to do with what you have learned.

Revise for Reader Impact, Not Just Correctness

Revision is where strong essays separate themselves from competent ones. First, read for structure. Can you summarize each paragraph in five words? If not, the paragraph may lack a clear job. Next, read for momentum. Does each paragraph build on the last, or does the essay feel like separate résumé bullets glued together?

Then revise for depth. Circle every sentence that states a fact about you. Now ask whether the essay also interprets those facts. If you mention a project, does the reader know why it mattered? If you mention a challenge, does the reader know how you responded? If you mention need, does the reader know what support would enable?

Use this checklist:

• Opening: Does the first paragraph begin in a real moment rather than with a generic claim?
• Specificity: Have you included concrete details, not just labels like “leadership” or “passion”?
• Evidence: Do your examples show action and result?
• Reflection: Have you answered “So what?” after each major example?
• Need: Is the role of scholarship support clear and practical?
• Voice: Does the essay sound like a thoughtful person, not a brochure?
• Ending: Does the conclusion look forward with purpose?

Finally, cut anything that could appear in almost any scholarship essay. Generic praise of education, broad statements about changing the world, and recycled lines about loving STEM weaken credibility unless tied to your own record and aims.

Common Mistakes to Avoid

1. Starting with a cliché. Avoid openings such as “I have always been passionate about computer science” or “Since childhood, technology has fascinated me.” These lines tell the reader nothing distinctive. Start with action, tension, or observation.

2. Listing activities without a through-line. A résumé lists. An essay interprets. Choose fewer examples and develop them.

3. Confusing difficulty with insight. Simply stating that something was hard does not make it meaningful. Explain what the challenge taught you and how you changed your approach.

4. Hiding the need section. If scholarship support matters, say how. Be concrete, not melodramatic.

5. Sounding inflated. You do not need grand language to sound impressive. Clear verbs, accountable detail, and honest reflection are more persuasive than superlatives.

6. Writing for an imaginary “perfect applicant.” Your goal is not to imitate what you think a scholarship winner sounds like. Your goal is to present a credible, specific, thoughtful version of your own path.

If you want one final standard, use this: by the end of the essay, the committee should be able to answer three questions easily. What has this student done? What has this student learned? What will support help this student do next? If your draft makes those answers clear, you are close.