03 Extracurricular Strategy

Zara, your activity portfolio already points in a clear direction: applying data science to real public problems. The committee flagged your police use‑of‑force dataset work as the anchor that ties the rest of your activities together. That kind of coherence is valuable for selective programs in data science and statistics because it shows you are not just learning technical skills—you are applying them to questions with real civic relevance.

Your strategy for the remainder of this application cycle is not to add more activities. Instead, the goal is to present the depth, leadership, and measurable impact of what you have already done so admissions readers can quickly understand the scope of your work.

Clarifying Your Central Theme: Civic Data Science

The strongest narrative thread across your activities is the idea of using data to understand and improve communities. The police use‑of‑force dataset project already signals this direction clearly. When admissions officers read your activities section, they should immediately see a consistent progression:

  • Technical data work (the policing dataset project)
  • Community impact through coding education (Girls Who Code leadership)
  • Personal discipline and leadership through athletics (track captain)

The key improvement is making the technical work legible to non‑experts. Admissions readers are rarely specialists in data science, so your activity descriptions must translate technical effort into understandable outcomes. Right now, the committee noted that your open‑source work lacks enough detail for a reviewer to judge its complexity or significance.

For example, instead of describing a project generically as “worked on an open‑source dataset,” focus on concrete scope:

  • What dataset you assembled or cleaned
  • How large it was or what sources were combined
  • What analysis or tools you built around it
  • Who used it or what insights it produced

This shift—from describing tasks to describing outcomes—can significantly strengthen the technical credibility of your application.

Reframing Your Open‑Source and Technical Work

Because your intended major is data science/statistics, admissions officers will look closely at how sophisticated your technical work actually is. If your current activity descriptions simply say that you “contributed to open source,” that leaves reviewers guessing.

Instead, restructure descriptions so they communicate three things quickly:

  • Problem: What question or issue the project addressed.
  • Technical action: What you actually built, cleaned, or analyzed.
  • Outcome: What the result enabled.

For the policing dataset project, that might mean clarifying elements such as:

  • The types of data sources you compiled
  • Whether you standardized or cleaned inconsistent data
  • Any analysis, visualizations, or tools produced
  • Whether others can access or use the dataset

Even simple outcome metrics—datasets compiled, features implemented, analyses conducted—help admissions readers understand that this work required real technical skill.

Positioning Your Leadership in Girls Who Code

Your leadership profile is already strong. Founding a Girls Who Code chapter with about 40 members and mentoring 15 students in Python demonstrates both initiative and teaching ability.

The key is emphasizing scale and responsibility. When describing this activity, make sure readers can see:

  • You founded the chapter (initiative)
  • You built a community of ~40 members (organizational scale)
  • You personally mentored 15 students (direct impact)

If possible, clarify outcomes of the mentorship itself. For example, you might describe whether students completed coding projects, learned foundational Python concepts, or continued into advanced programming. Even brief indicators of growth make your leadership role more tangible.

This activity also strengthens your narrative because it connects your technical interests to community impact. It shows that you are not only building data skills—you are helping others gain access to them.

Athletics as Leadership and Discipline

Your role as varsity track captain and school record holder in the 800m adds an important dimension to your profile. Highly selective STEM programs see many applicants whose lives revolve entirely around academics. Athletics demonstrate endurance, time management, and leadership under pressure.

The record itself signals performance excellence, while the captaincy shows that teammates trust you in a leadership role. When writing the activity description, emphasize:

  • Captain responsibilities (leading workouts, mentoring teammates, or coordinating meets if applicable)
  • The achievement of the school record
  • Your long-term commitment to the sport

This activity should remain prominent in your top activities because it demonstrates a different type of leadership than your technical work.

Activity Prioritization

Admissions readers at Berkeley, Carnegie Mellon, and Georgia Tech typically move quickly through the activities section. Your first few entries should highlight the strongest signals of academic direction and leadership.

Priority Tier Activities to Feature Strategic Goal
Top Tier Police use‑of‑force dataset project; Girls Who Code founder Establish civic data science identity and leadership
Second Tier Open‑source contributions Demonstrate technical depth and collaboration
Third Tier Varsity track captain and 800m school record Show discipline, resilience, and leadership outside academics

If you have additional activities, you have not provided them yet. If so, make sure they reinforce your technical interests or leadership story rather than distracting from it.

Time Allocation for Senior Fall

Because you are already in the application year, your time should go toward strengthening how these activities are presented rather than trying to launch entirely new commitments.

  • Refine activity descriptions so each one shows scope and measurable outcomes.
  • Document specific numbers where possible (datasets created, students mentored, members involved).
  • Ensure your most technical work is explained clearly enough for non‑technical readers.

Admissions officers should come away with a simple impression: Zara Okonkwo uses data science to investigate civic issues, leads others in learning technical skills, and demonstrates discipline through athletics.

Senior Fall Execution Calendar

Month Key Actions Outcome
August
  • Draft detailed activity descriptions emphasizing outcomes and scope
  • Clarify technical explanation of the policing dataset project
Strong first draft of activities section
September
  • Refine open‑source activity descriptions to show technical complexity
  • Quantify leadership impact in Girls Who Code (members, students mentored)
Clearer technical and leadership narrative
October
  • Finalize activity ordering and wording for Early Action submissions
  • Ensure activities align with themes developed in essays (see §06 Essay Strategy for approach)
Polished activities section ready for submission
November–December
  • Reuse and refine activity descriptions for remaining applications
  • Update any measurable outcomes from fall activities if relevant
Consistent presentation across all applications

The core objective is clarity. You already have leadership, technical engagement, and athletic distinction. The difference between a good activities section and a compelling one will come down to how concretely you show the scale and impact of the work you have already done.