📰
Zara Okonkwo's Admissions Blueprint

Read the entire strategy as a polished, printable magazine-style article.

Read Blueprint →
Admissions Strategy

Zara Okonkwo's Plan

🎯 Data Science / Statistics Grade 12 GPA 3.94 SAT 1530 📍 GA
Version 1 · Updated Apr 29, 2026
Admission chance · 3 schools
1
High
1
Medium
1
Low
Activities
  • Data for Good — Founder & Lead Analyst, 2 yrs
  • Girls Who Code — Chapter Lead, 3 yrs
  • Math Modeling Competition — Team Captain, 2 yrs
  • Track & Field — Varsity, 3 yrs
AP / Honors
AP Computer Science A · AP Statistics · AP Calculus BC · AP Physics 1 · AP English Language · AP Macroeconomics

School Snapshot

3 schools · tap a card to expand
Academic Support Major Fit Support Culture Fit Support Counterpoint Support

The committee actually agreed more than usual on this application. All four reviewers saw the same core strength: a coherent civic data science profile anchored by the police use-of-force dashboard that reached the Atlanta City Council. That project, combined with HiMCM modeling and Girls Who Code leadership, created a narrative that felt authentic and aligned with Berkeley’s public mission. The one repeated concern was missing academic detail — because Berkeley is test-blind, transcript rigor and highest math level matter a lot, and that information wasn’t provided in the file. Ultimately, the committee judged that the civic-impact data work was differentiated enough to keep this in the High tier, though not at the very top of the pool. The most important thing for you is simple: make sure your transcript clearly shows the strongest possible math and quantitative preparation.

Override Condition
Provide clear evidence of top-level quantitative preparation — e.g., documentation of advanced math coursework (AP Calculus BC or higher, statistics, linear algebra) or publishing a deeper technical analysis from the civic dataset showing rigorous statistical methods.
Top Actions
  • Explicitly document your highest math and quantitative coursework (e.g., AP Calculus BC, advanced statistics, multivariable, or similar) and emphasize it in the activities/additional information section if not obvious. · Immediately when preparing the UC application
  • Expand the police use-of-force project into a deeper statistical analysis (regression, trend modeling, or policy insight) and publish the dataset/report publicly or on GitHub with technical documentation. · Within 1–3 months before application submission
  • Use UC essays to explicitly connect your civic data work to Berkeley’s ecosystem (public mission, open data, civic-tech communities, or data science labs). · During UC PIQ writing period
Key Strengths
  • Strong academic baseline with a 3.94 GPA and a HiMCM finalist result demonstrating mathematical modeling and analytical thinking.
  • Civic‑focused data initiative ('Data for Good') that produced a county‑level dataset on police use‑of‑force and was presented to a city council with local news citation.
  • Leadership and sustained engagement: founded a Girls Who Code chapter (~40 members), mentored 15 students in Python, and served as varsity track team captain while holding the school record in the 800m.
Critical Weaknesses
  • Lack of visible course rigor detail, especially math progression, making it hard to evaluate preparation for Berkeley’s Data Science/Statistics curriculum.
  • Technical depth of the 'Data for Good' project is unclear (uncertain whether the student performed statistical modeling or mainly compiled/visualized data).
  • Open‑source contributions are mentioned but not described in enough detail to judge significance or technical complexity.
Power Moves
  • Clearly document the technical methodology used in the Data for Good project (e.g., data collection process, statistical analysis, modeling choices, and limitations addressed).
  • Provide concrete descriptions or links for GitHub/open‑source contributions showing specific code, features implemented, or documentation written.
  • Highlight the highest level math and quantitative coursework completed relative to what the high school offers to demonstrate preparation for rigorous data science study.
Essay angle: Frame a narrative around translating data analysis into civic impact—how building the police use‑of‑force dataset evolved from a technical curiosity into a tool used in public policy discussion when presented to a city council.
Path to higher tier: Clearer evidence of advanced quantitative preparation and deeper technical work—especially detailed statistical or modeling methods in the Data for Good project and substantive open‑source contributions—would strengthen the case that the student already operates at a college‑level data science depth.
Academic Concern Major Fit Concern Culture Fit Neutral Counterpoint Concern
Blocker: Technical distinction relative to CMU’s applicant pool — specifically the absence of a high‑level technical artifact (research, advanced modeling work, or widely adopted softwar...

The committee actually agreed on more than it disagreed about. Everyone saw a strong academic student with a clear and authentic theme: using data science to investigate civic systems, highlighted by the police use‑of‑force dashboard presented to Atlanta City Council. Where the debate emerged was technical depth. The Fit Reader believed the civic‑tech impact could differentiate Zara, but the Academic Reviewer, Major Gatekeeper, and Devil’s Advocate all noted that the CMU benchmark pool usually shows extreme technical artifacts — research papers, elite competitions, or widely used software systems. Ultimately the decision hinged on that comparison: the story is compelling, but the technical ceiling is not yet obvious relative to this particular applicant pool. The most powerful next step is not changing the narrative but deepening it technically — turning the civic‑data work into a rigorous, public, widely used data science project.

Primary Blocker
Technical distinction relative to CMU’s applicant pool — specifically the absence of a high‑level technical artifact (research, advanced modeling work, or widely adopted software system).
Override Condition
Turn the civic data work into a technically rigorous project with measurable external adoption — for example publishing the police‑use‑of‑force dataset and modeling pipeline on GitHub, applying advanced statistical or causal inference methods, and showing real usage by journalists, nonprofits, or researchers.
Top Actions
  • Release the police use‑of‑force analysis as a full technical project: open dataset, documented statistical methodology, reproducible code, and a public GitHub repository demonstrating advanced modeling (e.g., regression, causal inference, fairness analysis). · within 1–3 months
  • Add explicit evidence of mathematical rigor in the application: clearly list highest math courses (multivariable calculus, linear algebra, statistics) and any proof‑based or college‑level coursework. · immediately when finalizing applications
  • Scale the civic data platform beyond a presentation by partnering with journalists, nonprofits, or civic groups and documenting real adoption or policy usage. · next 3–6 months
Key Strengths
  • Strong academic baseline with a 3.94 GPA and 1530 SAT, indicating readiness for selective universities.
  • HiMCM finalist team participation, which signals exposure to real-world mathematical modeling and quantitative problem solving.
  • Founder of a civic data project that built a dashboard analyzing police use-of-force data and presented the work to the Atlanta City Council, with local news citation—showing real-world application of data analysis.
Critical Weaknesses
  • Limited visibility into academic rigor: the file shows a 3.94 GPA and 1530 SAT but provides no course list, class rank, or evidence of advanced math coursework.
  • Unclear individual technical depth: HiMCM is a team competition and the application summary does not specify the student's personal role in modeling, coding, or analysis.
  • Open-source work is mentioned but not described in scope or impact, making it difficult for reviewers to evaluate its significance.
Power Moves
  • Clearly document the technical implementation of the civic data dashboard (tools, programming languages, data pipelines, analysis methods) to demonstrate hands-on quantitative skill.
  • Clarify individual contributions in the HiMCM project and other data work, emphasizing modeling, coding, or statistical analysis performed personally.
  • Provide concrete evidence of impact or scale for projects—such as usage of the dashboard, continued updates, or adoption by community stakeholders.
Essay angle: Focus on the moment when data analysis moved from a personal or academic exercise to something that entered a real civic conversation—building the police use-of-force dashboard and presenting it to the Atlanta City Council—and reflect on how translating messy public data into something policymakers could see and discuss shaped the student’s interest in data science for public decision-making.
Path to higher tier: Admissions confidence would increase with clearer evidence of sustained quantitative depth—such as advanced math coursework, detailed technical work on the dashboard, or demonstrated individual contributions to modeling and analysis—showing that the civic impact projects are supported by strong underlying technical capability.
Academic Support Major Fit Support Culture Fit Support Counterpoint Concern
Blocker: Unclear technical depth relative to Georgia Tech’s top Data Science admits, especially missing evidence of advanced math coursework and large‑scale or research‑level technical builds.

The committee largely agreed that your academic preparation is strong for Georgia Tech — your GPA and SAT sit comfortably within the admitted range. Reviewers were also aligned that your application tells a clear story: using data science to analyze civic systems, highlighted by the police use‑of‑force dashboard and your presentation to Atlanta City Council. Where the discussion became interesting was technical scale. Three reviewers felt the real‑world policy impact made the project compelling, while one argued that Georgia Tech’s strongest admits often build larger engineering systems or conduct deeper technical research. That debate ultimately placed you in the competitive middle of the pool: a credible and coherent data science applicant, but not yet showing the same level of technical infrastructure or research as the most standout admits. Strengthening the technical depth and visibility of your civic‑data work would move you much closer to the top tier.

Primary Blocker
Unclear technical depth relative to Georgia Tech’s top Data Science admits, especially missing evidence of advanced math coursework and large‑scale or research‑level technical builds.
Override Condition
Expand the police use‑of‑force project into a technically rigorous data science system — for example releasing a public dataset/API, publishing a statistical or ML analysis with a university mentor, or demonstrating real external adoption (journalists, researchers, civic orgs). Evidence of advanced math coursework would further remove preparation concerns.
Top Actions
  • Turn the policing dashboard into a technically robust data science project (publish the dataset, document modeling methods, release code, and show real users such as journalists or nonprofits) · before EA or early RD
  • Clearly document advanced math and statistics preparation (AP Calculus BC, AP Statistics, or higher math; include current or planned coursework and any independent study) · immediately in application materials
  • Quantify open‑source technical work (GitHub repos, commits, stars, contributors, dataset size, algorithms used) so reviewers can see the engineering depth behind the civic projects · before submitting activities list and additional information section
Key Strengths
  • Strong academic baseline with a 3.94 GPA and 1530 SAT indicating readiness for rigorous quantitative study.
  • HiMCM finalist distinction demonstrating experience with real-world mathematical modeling and team-based quantitative problem solving.
  • Consistent theme of civic-focused data projects (police use-of-force dashboard, food desert mapping) including real-world engagement such as presenting to the Atlanta City Council.
Critical Weaknesses
  • Course rigor in mathematics, statistics, or computer science is unclear because specific course titles are not provided in the application summary.
  • The technical depth of the police use-of-force dashboard is not well explained, leaving uncertainty about the level of data engineering or modeling involved.
  • Open-source GitHub contributions are mentioned but appear under-emphasized and their scale or impact is not clearly documented.
Power Moves
  • Clearly document the technical architecture and methods behind projects (data pipelines, modeling approaches, tools used) to demonstrate depth beyond visualization.
  • Elevate and quantify GitHub/open-source contributions to show collaborative coding experience and real-world software development practices.
  • Provide explicit evidence of advanced quantitative preparation through coursework, independent study, or additional technical work.
Essay angle: Frame the narrative around translating complex civic data into tools that communities and policymakers can actually use, highlighting the moment of presenting data-driven insights to the Atlanta City Council and the motivation to make public systems more transparent through data science.
Path to higher tier: Stronger verification of technical rigor—such as clearly documented advanced math/CS coursework and deeper explanation or impact of the student’s data projects—would make the profile more compelling for top-tier data science or statistics programs.

Priority Actions

Highest impact — do these first
1
Release the police use‑of‑force analysis as a full technical project: open dataset, documented statistical methodolog...
⭐ Wanted by 2 schools University of California-Berkeley, Carnegie Mellon University · Medium effort · within 1–3 months
2
Explicitly document your highest math and quantitative coursework (e.g., AP Calculus BC, advanced statistics, multiva...
University of California-Berkeley · Low effort · Immediately when preparing the UC application
3
Turn the policing dashboard into a technically robust data science project (publish the dataset, document modeling me...
Georgia Institute of Technology-Main Campus · Medium effort · before EA or early RD
4
Use UC essays to explicitly connect your civic data work to Berkeley’s ecosystem (public mission, open data, civic-te...
University of California-Berkeley · Low effort · During UC PIQ writing period
5
Add explicit evidence of mathematical rigor in the application: clearly list highest math courses (multivariable calc...
Carnegie Mellon University · Low effort · immediately when finalizing applications

Executive Summary

Executive Summary for Zara Okonkwo

Zara, you are entering the admissions cycle with a strong academic and extracurricular profile for highly selective programs in Data Science and Statistics. Your 3.94 GPA and 1530 SAT place you solidly within the competitive academic range for rigorous universities. Beyond academics, your activities show a clear pattern: using data analysis to address real-world civic issues. That alignment between your intended major and your leadership work is one of the strongest aspects of your application.

Your extracurricular record shows both technical depth and leadership. Founding and leading Data for Good with a real-world dashboard tracking police use-of-force data across Georgia counties—and presenting those findings to the Atlanta City Council—is a rare example of a student data project influencing public conversation. Combined with your leadership in Girls Who Code, success in math modeling competitions, and commitment to varsity track and field, you present as a student who combines quantitative skill, initiative, and teamwork.

However, admissions readers will also look for context that has not yet been provided in your profile. You have not provided details about your coursework (AP/IB/honors classes), academic awards beyond HiMCM recognition, recommendation context, or additional independent research or internships. Those pieces often help selective universities confirm the full academic picture for students applying to quantitative majors.

School Verdict Snapshot

  • University of California, Berkeley — High
    Berkeley is an extremely competitive environment for data-related majors. Your civic data work and strong quantitative narrative will resonate, but the overall selectivity of Berkeley—especially in data-focused pathways—means admission remains highly uncertain. Your impact-driven data work is the kind of story that can help you stand out.
  • Carnegie Mellon University — Low
    Programs connected to statistics, machine learning, and data science at CMU are among the most selective in the country. Even with your strong SAT and modeling experience, admission will be very difficult. This should be treated as a reach where a compelling narrative about civic data impact is essential.
  • Georgia Institute of Technology — Medium
    Georgia Tech is a strong and logical target given your academic record and the alignment between your work and data-focused problem solving. Your leadership, modeling competition experience, and civic analytics project fit well with Tech’s applied quantitative culture.

Your Biggest Strength

Your clear, real-world application of data science to civic problems is the most powerful part of your profile. The Data for Good project—especially the Atlanta City Council presentation and local news citation—demonstrates that you are not just learning technical skills but applying them to public policy and community issues. That narrative can anchor your entire application.

Your Biggest Gap

You have not yet provided details about advanced coursework, additional academic distinctions, or extended technical projects beyond the activities listed. For highly selective data science pathways, admissions officers often want evidence of sustained quantitative rigor across classes, competitions, or research.

Top 3 Immediate Actions

  • Fully document your academic rigor. Add details about your math, statistics, computer science, and advanced coursework at your high school. If you have taken AP, IB, dual enrollment, or advanced math classes, those should be clearly highlighted.
  • Expand the technical story of your Data for Good project. In applications, explain the modeling techniques, data pipelines, and analytical methods you used to build the dashboard and analyze the police use-of-force data.
  • Show continued depth in quantitative work. Consider submitting additional materials or describing further analysis, modeling, or civic datasets you have explored. Even extending the existing project or publishing a deeper report could strengthen your data science narrative.

Overall, you are presenting a compelling profile built around data-driven civic impact. If you clearly communicate the technical depth behind your projects and provide more academic context, your application will tell a coherent and memorable story.

Strategy Playbook

14 sections · expand any to read inline

02 Testing Strategy

Zara Okonkwo, your current SAT score of 1530 already places you in a position where additional testing is unlikely to materially improve your admission prospects at the schools on your list. For highly selective programs in data science, statistics, and related quantitative fields, admissions offices expect strong academic signals — and your score already clears that bar. Because of this, testing should be treated as a maintenance task rather than a strategic lever for the rest of your application cycle.

The admissions committee discussion flagged that the areas most likely to influence outcomes at your target schools are academic depth and how clearly your academic preparation is presented. Your testing profile does not need fixing. The priority now is simply ensuring that your score is reported strategically where it matters and that you avoid spending valuable application-season time chasing marginal improvements.

School-by-School Testing Policy Implications

School Testing Policy Impact Recommended Action
UC Berkeley Standardized tests are not considered in evaluation. Do not spend time retesting specifically for Berkeley. Focus energy on the rest of the application.
Carnegie Mellon Strong quantitative scores support applicants to data-focused majors. Submit your 1530. No retake necessary.
Georgia Tech Strong SAT scores align well with the academic expectations of STEM programs. Submit your 1530 confidently.

The practical takeaway is simple: your SAT will help at CMU and Georgia Tech, and it will be ignored at Berkeley. Because of this, further testing preparation would have little impact on your overall competitiveness.

Retake Decision

Under most circumstances, I would not recommend an SAT retake for you. The improvement window above 1530 is small, unpredictable, and unlikely to meaningfully change how admissions officers evaluate your application.

The only scenario where a retake could make sense is if all of the following conditions are true:

  • You have a clear superscore opportunity (for example, a past section score that could easily be improved).
  • You can prepare with minimal time investment during an already busy senior fall.
  • The test date occurs well before application deadlines so it does not interfere with essays or schoolwork.

If those conditions are not present, the rational strategy is to lock in your current score and redirect your time elsewhere. At this stage of senior year, time is the most constrained resource in the entire admissions process.

Score Reporting Strategy

Your goal is simple: ensure that your strongest score is visible wherever testing is considered.

  • Carnegie Mellon: Report your SAT. Your score reinforces the quantitative readiness expected for data-oriented majors.
  • Georgia Tech: Report your SAT as well. A 1530 aligns well with the academic expectations for rigorous STEM programs.
  • UC Berkeley: Testing will not be reviewed, so no reporting decision is required for admissions purposes.

Because your SAT is already strong, the key operational step is simply verifying that all score reports are submitted correctly and on time. Administrative mistakes — missing scores, late reports, or incorrect superscore submissions — are far more common problems than insufficient test performance at this level.

If You Choose to Attempt a Final Retake

If you personally feel that a higher score is achievable with little effort, keep the preparation extremely targeted. Do not restart full test prep. Instead:

  • Focus on error pattern review from previous practice exams.
  • Prioritize math section precision, since quantitative fields value that signal.
  • Limit preparation to short weekly practice blocks so essay writing and schoolwork remain the priority.

If practice tests do not immediately trend above your current score range, abandon the retake quickly and shift your attention back to the broader application.

Testing Timeline (Senior Fall)

Month Key Actions Target Outcome
August
  • Decide whether a final SAT attempt is worthwhile.
  • If retaking, complete 1–2 diagnostic practice tests.
Clear decision: retake or finalize 1530.
September
  • If retaking, complete light targeted review.
  • Register and confirm score reporting logistics.
Testing logistics locked in.
October
  • Final SAT attempt (only if justified).
  • Send official score reports where required.
Final scores submitted.
November
  • Verify score receipt in application portals.
  • Resolve any reporting issues immediately.
No missing test materials.

Bottom Line

Your testing profile is already strong enough for your current target schools. At this point in the admissions cycle, incremental test gains will not significantly change your admissions outlook. The smarter strategy is to treat testing as complete, ensure accurate reporting to Carnegie Mellon and Georgia Tech, and invest the rest of your time in the elements of the application that carry more weight this late in the process.

01 Academic Profile Analysis

Zara Okonkwo, your 3.94 GPA places you in a strong academic position for highly selective universities. At a baseline level, this GPA signals sustained performance across multiple years of high school and will immediately position you as a serious applicant for quantitative majors like Data Science or Statistics. However, GPA alone does not tell admissions readers how demanding your coursework has been. In the materials reviewed so far, the full course list and math progression were not provided, which means evaluators could not assess the rigor of your transcript or the highest level of mathematics you have completed.

At the schools on your list—particularly highly quantitative institutions such as UC Berkeley, Carnegie Mellon, and Georgia Tech—the admissions team looks closely at how far students have progressed through their high school’s available math curriculum. For applicants pursuing data science or statistics, the transcript must clearly show that the student pursued the most advanced quantitative coursework available at their high school. Without seeing that trajectory, admissions readers have limited information to judge readiness for rigorous first‑year coursework in probability, linear algebra, and statistical computing.

Why Transcript Rigor Matters for Your Target Schools

Each of your target universities evaluates academic preparation slightly differently, but they all rely heavily on the transcript when assessing students applying to quantitative majors.

School How Transcript Rigor Factors Into Review Why Your Math Progression Matters
UC Berkeley Berkeley does not consider SAT/ACT scores in admissions decisions. Your transcript becomes the primary academic signal. The highest level of math completed is especially important for data science and statistics readiness.
Carnegie Mellon Highly quantitative programs place heavy emphasis on demonstrated preparation in advanced math. Admissions readers want to see evidence that applicants have challenged themselves with the strongest math options available.
Georgia Tech Rigor of coursework relative to what the high school offers is a key academic factor. Math progression helps reviewers determine whether the student is prepared for technical coursework.

Because Berkeley is test‑blind, this issue becomes especially important there. In the absence of standardized test scores, Berkeley relies heavily on course rigor and grade performance to determine academic readiness. For a student intending to study data science or statistics, the admissions reader will typically scan the transcript quickly to answer a few core questions:

  • What is the highest math level the student reached?
  • Did the student pursue advanced or accelerated math when it was available?
  • Does the math sequence demonstrate consistent upward progression?

Right now, because your course list and math trajectory were not included in the file reviewed, those questions remain unanswered for the admissions reader.

Clarifying Your Math Trajectory

For applicants targeting data science or statistics, the math sequence on the transcript functions as a signal of intellectual preparation. Admissions officers want to see that students pursued the most advanced quantitative coursework available at their high school. This might include courses such as:

  • AP Calculus BC
  • Advanced statistics or AP Statistics
  • Post‑calculus courses (for example multivariable calculus or linear algebra if offered)
  • Honors or accelerated math sequences leading into calculus

It is important to emphasize that you have not yet provided your math course history. Without that information, evaluators cannot determine:

  • Whether you reached calculus during high school
  • Whether you took the most advanced math classes available at your school
  • How early your quantitative acceleration began

Clarifying this progression will significantly strengthen your academic profile across all three target universities because it allows admissions readers to place your GPA in context. A 3.94 GPA in the most demanding courses available sends a very different signal than a 3.94 GPA in a lighter course load.

How Admissions Readers Interpret Quantitative Preparation

When reviewing applicants for quantitative majors, admissions officers often read the transcript in a pattern that prioritizes STEM coursework. They will typically scan the math and science columns first to see how far the student progressed and how consistently they performed. A strong applicant for data science or statistics usually demonstrates two characteristics on the transcript:

  • Vertical progression — moving steadily toward the most advanced math offered at the school
  • Consistent grades — maintaining strong performance in those courses

Your GPA already indicates strong grade performance overall. What is currently missing is the context showing whether those grades were earned while pursuing the highest level of quantitative rigor available. Because your intended major sits squarely in the mathematical and computational domain, this context becomes one of the most important academic signals in your application.

Immediate Actions to Strengthen the Academic Narrative

Since you are applying during your senior year, the focus should not be on adding new courses but on ensuring that your transcript and application materials clearly communicate the rigor you have already completed.

  • Document your full course list. Include every math course taken in high school and the grade level when you took it.
  • Identify the highest math available at your high school. If you reached that level, make sure it is clearly visible in the application.
  • Use the Additional Information section if needed. If your school has an unusual math sequence or limited advanced options, briefly explain this context.

If your transcript already includes advanced math such as calculus or higher-level statistics, making that trajectory visible will strengthen the academic evaluation significantly—especially at Berkeley, where coursework is the primary signal of preparation.

Application Timeline for Academic Positioning

Month Actions Goal
September
  • Compile a full list of all math and quantitative courses taken in high school.
  • Confirm that your transcript accurately reflects your highest math level.
Ensure admissions readers can clearly see your quantitative preparation.
October
  • Review the Additional Information section and add context if your school’s math offerings are limited.
  • Double‑check that course titles are clear and recognizable.
Prevent confusion about the rigor of your math coursework.
November
  • Verify that submitted applications include your most recent transcript.
  • Coordinate with your counselor if mid‑year grades will strengthen your academic profile.
Ensure universities see the strongest and most complete academic record.

Your GPA already places you in a competitive academic tier. The key step now is ensuring that admissions officers can clearly see the depth of your quantitative preparation. Once your full transcript and math progression are clearly presented, reviewers will be able to evaluate your readiness for demanding programs like data science and statistics with far greater confidence.

05 Monthly Action Plan

This calendar is designed to move quickly from clarification of your academic profile to a polished application narrative centered on civic data science. Each phase builds toward presenting your technical work clearly and credibly to admissions readers at Berkeley, Carnegie Mellon, and Georgia Tech. Where deeper guidance is needed, this plan references the relevant sections of the overall strategy.

Month Primary Actions & Target Outcomes
Month 1
  • Audit your quantitative coursework. Create a complete list of all math, statistics, and advanced quantitative classes taken at your high school. Include course titles, level (AP/Honors/etc. if applicable), and the sequence relative to what your school offers. The goal is to clearly demonstrate the highest available rigor (see §01 Academic Profile Analysis).
  • Confirm school context. Verify with your counselor what the most advanced math pathway at your school looks like so your application accurately communicates how far you progressed within available offerings.
  • Begin organizing documentation. Collect syllabi, project summaries, or major assignments from your highest-level quantitative classes so they can inform activity descriptions or portfolio links later in the process.
Month 2
  • Finalize your academic rigor narrative. Convert the coursework audit into a short internal summary explaining the quantitative path you pursued. This will help shape activity descriptions and counselor coordination.
  • Revisit the police use‑of‑force dataset project. Define the analytical questions you want the project to answer and outline the statistical modeling approach you plan to implement (see §03 Creative Projects).
  • Establish a reproducible workflow. Set up version‑controlled code, organized datasets, and clear documentation so the project can eventually be shared publicly.
Month 3
  • Deepen the technical analysis. Expand the dataset project beyond descriptive statistics into stronger quantitative methods. Focus on transparent methodology and clearly interpretable outputs.
  • Document every step. Write clear explanations of data sources, assumptions, and modeling choices so readers can understand both the technical work and its civic relevance.
  • Prepare visual outputs. Begin building charts, model summaries, or interactive outputs that make the analysis understandable to non‑technical audiences.
Month 4
  • Finalize the analytical framework. Complete the statistical modeling and validate that the code runs cleanly from raw data to final results (see §03 Creative Projects).
  • Write project documentation. Draft a clear explanation of the research question, dataset construction, and analytical approach so the project can stand on its own if shared publicly.
  • Prepare a publishable repository. Organize code, data documentation, and a readable project overview that can be linked in applications later.
Month 5
  • Publish the project publicly. Host the analysis and documentation in a location that allows admissions readers to view the work easily (for example through a repository or similar platform).
  • Write a plain‑language summary. Create a concise explanation of the project’s findings and civic relevance that could be understood by journalists or community organizations.
  • Prepare outreach materials. Draft short emails introducing the project and its potential public value.
Month 6
  • Begin outreach to civic stakeholders. Share the project with journalists, nonprofits, or civic groups who work on policing transparency or data‑driven policy analysis.
  • Track responses and engagement. Keep records of outreach and any feedback or interest generated; this can help demonstrate real‑world engagement with the project.
  • Start essay brainstorming. Outline how your civic data science work connects to broader themes of public impact and responsible data use (see §06 Essay Strategy).
Month 7
  • Draft your core personal and supplemental essays. Emphasize the intersection between statistical analysis and public accountability in civic systems.
  • Align school‑specific narratives. Begin shaping essays that connect your interests in data and public impact to institutional values at Berkeley, Carnegie Mellon, and Georgia Tech.
  • Integrate the project into your narrative. Ensure your writing clearly explains the intellectual motivation behind the dataset project and what you learned from building it.
Month 8
  • Revise essays strategically. Strengthen clarity and focus, ensuring each essay highlights both technical curiosity and civic purpose (see §06 Essay Strategy).
  • Prepare activity descriptions. Write precise descriptions for the dataset project and any related work, emphasizing the analytical techniques used and the real‑world problem addressed.
  • Confirm technical links. Make sure the published project repository, documentation, and any visual outputs are accessible and clearly organized.
Month 9
  • Finalize the application activity section. Refine descriptions so they communicate technical depth within the limited character space (see §07 Application Execution).
  • Integrate project links thoughtfully. Include documentation links only where the application format allows and where they strengthen the narrative.
  • Conduct a full application review. Check that academic rigor, civic data science work, and quantitative interests are consistently presented across essays and activities.
Month 10
  • Complete final proofreading. Ensure essays, activity entries, and technical references are accurate and error‑free.
  • Verify all materials before submission. Confirm that every section of the application clearly communicates your quantitative preparation and civic data science project.
  • Submit applications with final documentation links included. The goal is a cohesive application that shows both technical skill and a commitment to data‑driven public impact.

By following this timeline, Zara Okonkwo, you ensure that your most distinctive element—the police use‑of‑force data analysis—evolves from an interesting project into a technically rigorous, publicly documented example of civic data science. The later months then focus on translating that work into compelling essays and precise activity descriptions so admissions readers can immediately understand both the technical depth and the public purpose behind it.

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.

04. Major-Specific Preparation: Data Science & Statistics Alignment

Zara Okonkwo, selective data science and statistics programs are not just evaluating general academic strength; they are trying to determine whether you already think and work like a quantitative analyst. Your HiMCM finalist result signals exposure to mathematical modeling and complex problem solving, which is highly relevant to a data science pathway. However, admissions readers will still be looking for clearer evidence of individual technical engagement with data, modeling, and statistical reasoning. Strengthening how that work is presented—and clarifying your specific role—will be one of the most important steps before submitting applications.

The committee flagged that admissions officers may currently see strong mathematical promise but may not yet see enough concrete evidence of advanced quantitative preparation specifically aligned with data science and statistics. Because you are already in Grade 12, the focus should not be on building entirely new credentials. Instead, the priority is making sure the technical depth you already possess—especially through HiMCM—is clearly visible in your application materials.

Positioning the HiMCM Experience as Technical Evidence

Your HiMCM finalist recognition already indicates exposure to mathematical modeling under time pressure. For data science programs, the key question becomes: what exactly did Zara do?

If your application materials only mention that you participated in a team modeling competition, admissions readers cannot easily assess your technical contributions. Data science programs—especially at places like Carnegie Mellon—want evidence that you personally engaged in tasks such as:

  • Designing or selecting the mathematical model
  • Implementing code for simulations or calculations
  • Performing statistical analysis or interpreting datasets
  • Evaluating model accuracy or limitations
  • Translating quantitative findings into conclusions

If your current activity description does not specify these elements, you should revise it. Clarifying your personal role helps admissions officers understand whether you were functioning as a quantitative contributor rather than simply a team participant.

For example, your application could emphasize elements such as:

  • The type of modeling approach your team used
  • Whether you wrote or implemented code for the model
  • How you handled data cleaning, parameter testing, or simulations
  • Your role in validating or refining the model

You do not need to exaggerate your role. Simply describing the technical components you handled can significantly strengthen how this experience signals readiness for data science study.

Demonstrating Advanced Quantitative Preparation

Another issue the committee raised is that admissions readers need clearer signals of advanced quantitative preparation aligned with statistics and data science. Your GPA (3.94) and SAT (1530) already suggest strong academic ability, but selective programs also look for evidence that applicants have engaged deeply with mathematical reasoning and computational thinking.

You have not provided your specific coursework (AP, IB, honors, or dual enrollment classes). Because of this, admissions readers may not be able to see how far you have progressed in mathematics and quantitative subjects.

If your transcript includes advanced courses relevant to data science—such as statistics, calculus, or computer science—make sure those courses are clearly highlighted in the academic sections of your application. If your school profile already communicates course rigor, your role is simply to ensure that the courses most relevant to quantitative analysis are easy for readers to notice.

If advanced coursework in statistics or computing exists but has not yet been emphasized in your application materials, consider referencing it briefly in supplemental essays where appropriate (see §06 Essay Strategy). This helps reinforce that your modeling experience is supported by academic preparation.

Technical Engagement Expectations by Target School

University What Data Science–Oriented Programs Look For How to Position Your Preparation
Carnegie Mellon University Evidence that applicants already engage deeply with modeling, computation, or statistical analysis. Clarify technical contributions in HiMCM and highlight any coding or quantitative analysis you performed.
UC Berkeley Strong mathematical preparation combined with curiosity about data-driven problem solving. Emphasize the real-world modeling challenge addressed in HiMCM and your reasoning process.
Georgia Tech Applied quantitative thinking and readiness for rigorous technical coursework. Frame your modeling work as applied problem solving with structured mathematical methods.

Across all three schools, the strongest signal will be demonstrating that you personally engaged with quantitative reasoning and data analysis, rather than simply participating in a team competition.

Technical Skills Signaling

You have not provided information about programming languages, statistical tools, or technical software you may use. For data science programs, this information matters because it shows readiness for computational work.

If you have experience with tools commonly used in data analysis—such as programming languages, statistical software, or modeling environments—you should list them clearly in the activities or additional information sections of your application. If you do not currently have formal experience with these tools, avoid overstating technical ability. Instead, focus on the mathematical modeling and analytical reasoning demonstrated through HiMCM.

Admissions officers are not expecting every applicant to have the same technical toolkit, but they do want evidence that you are comfortable working with quantitative systems and structured problem solving.

Optional Short-Term Competitions or Showcases

Because you are applying this cycle, large new projects or research commitments are unrealistic. However, there are a few short-term opportunities you could consider if timing allows:

  • Entering a fall mathematics or statistics competition if registration is still open.
  • Participating in a short data analysis challenge or hackathon.
  • Submitting modeling work from HiMCM to school or regional academic showcases, if available.

These are optional. Your HiMCM finalist recognition is already meaningful; the priority is presenting that experience clearly rather than adding entirely new commitments.

Monthly Execution Timeline

Month Key Actions
September
  • Rewrite your HiMCM activity description to clarify your personal technical contributions.
  • Confirm that relevant quantitative coursework appears clearly in the academic section (you have not provided this information yet).
  • List any programming or statistical tools you have used, if applicable.
October
  • Refine supplemental essays to highlight your modeling mindset and quantitative curiosity (see §06 Essay Strategy).
  • Ask recommenders—especially STEM teachers—to emphasize analytical thinking and problem solving.
  • If feasible, enter a short-term math or data challenge.
November
  • Review applications to ensure technical elements (modeling, analysis, quantitative reasoning) appear consistently across activities and essays.
  • Double-check that the HiMCM role description communicates depth of engagement.
December–January
  • Adapt supplemental responses for remaining deadlines, continuing to emphasize modeling and data analysis themes.
  • Ensure that all materials reinforce your readiness for rigorous quantitative study.

The core message admissions readers should take away is simple: you are not just good at math—you already use mathematical tools to analyze complex problems. Your HiMCM experience provides the foundation for that story. The goal now is to make sure every reader clearly understands how you personally engaged in the modeling and analytical process.

13. Archetype Gap Analysis: Positioning the “Civic Data Scientist” for Top Technical Programs

Zara Okonkwo, your application naturally fits a distinctive intellectual archetype: the Civic Data Scientist. This type of applicant focuses on applying statistical and computational tools to analyze public systems such as policing, governance, or other civic infrastructure. Admissions offices at highly selective technical universities increasingly recognize this archetype because it connects quantitative reasoning with real-world societal impact.

The committee discussion suggests that the thematic direction of your profile is already coherent. In other words, the core narrative itself is not the main vulnerability. Instead, the challenge lies in how your application will be compared against the technical portfolios of students applying to the same programs. At schools such as UC Berkeley, Carnegie Mellon, and Georgia Tech, many admitted students pursuing data science or statistics present tangible evidence of deep technical work—large software systems, advanced statistical modeling, research publications, or elite competition performance.

Your positioning challenge, therefore, is not about finding a better story. It is about demonstrating that the technical machinery behind your civic analysis reaches the level expected by top technical programs.

How Elite Data Science Applicants Are Typically Interpreted

Admissions readers often categorize applicants into informal archetypes when evaluating STEM applications. Each archetype signals a different kind of intellectual promise.

Archetype Typical Evidence in Application Admissions Signal
Competition Mathematician High-level math or statistics competitions Theoretical analytical strength
AI / Software Builder Complex software platforms, machine learning systems Engineering and product development capability
Research Scientist Published papers, formal lab research Academic research potential
Civic Data Scientist Data analysis applied to social systems or policy Quantitative insight with societal impact

Your application most clearly fits the final category. That is a legitimate and compelling archetype—particularly because it bridges technical analysis with real-world decision-making. Universities such as Berkeley and Georgia Tech are especially receptive to applicants who show how data can improve public systems.

However, the committee flagged an important nuance: the most successful applicants within this archetype still demonstrate substantial technical depth beneath the civic framing. Without that layer, the application can risk appearing more policy-oriented than quantitatively rigorous.

Where Your Profile Is Strong

The strength of your archetype is authenticity. Applications that combine data analysis with civic engagement often stand out because they demonstrate purpose beyond academic achievement.

Within the admissions landscape, this positioning offers several advantages:

  • Distinct narrative positioning. Many data science applicants focus narrowly on machine learning or competitive math. A civic analytics focus differentiates you.
  • Real-world problem orientation. Universities increasingly prioritize students who apply technical tools to societal challenges.
  • Policy relevance. Programs like Berkeley’s data science ecosystem and Georgia Tech’s public-interest computing initiatives align well with this intellectual direction.

In short, the conceptual framework of your application is compelling. The admissions risk is not thematic confusion—it is the possibility that reviewers may not see enough visible technical sophistication to match the narrative.

The Core Gap: Demonstrated Technical Depth

Relative to the strongest applicants at highly selective technical universities, the main gap lies in the visibility of advanced technical work.

At schools like Carnegie Mellon in particular, the applicant pool frequently includes students who present major technical artifacts such as:

  • Original research papers in statistics, computer science, or applied mathematics
  • Large-scale software systems used by real users
  • Highly ranked competition results
  • Extensive open-source technical contributions

These artifacts function as proof that a student can already operate at a near–college level within their field. When admissions officers compare applications side-by-side, these concrete outputs make technical ability immediately visible.

The committee discussion indicates that your application may not yet display this same level of tangible technical production. If the civic analysis component is emphasized without accompanying evidence of rigorous modeling, engineering, or statistical methodology, reviewers may interpret the profile as primarily policy-focused rather than technically advanced.

Technical Depth Within the Civic Data Archetype

The most competitive version of the Civic Data Scientist archetype integrates three layers simultaneously:

Layer Description Admissions Impact
Social Problem A real civic system being analyzed (e.g., policing data, policy outcomes) Shows purpose and motivation
Statistical Modeling Rigorous analytical techniques applied to the data Demonstrates quantitative sophistication
Software Engineering Code or tools that process, analyze, or visualize the data Proves technical implementation ability

The strongest applicants integrate all three layers in ways that are clearly visible within their application materials.

For example, in the broader admissions landscape, successful applicants in this archetype often demonstrate:

  • College-level statistical modeling methods
  • Original datasets or complex data pipelines
  • Interactive tools or software platforms that make their analysis usable
  • Clear documentation of methodology

The committee flagged that strengthening the statistical and engineering layers within your civic narrative will be critical for competitiveness at the most selective programs on your list.

School-Specific Archetype Fit

University Archetype Alignment Gap Severity
UC Berkeley Strong institutional interest in data science applied to social systems Moderate
Georgia Tech Values applied analytics and computational problem solving Moderate
Carnegie Mellon Extremely technical applicant pool with large project portfolios High

At Berkeley and Georgia Tech, the Civic Data Scientist archetype aligns naturally with institutional priorities. Applications that combine statistical reasoning with public impact resonate well in these environments.

Carnegie Mellon, however, often evaluates applicants through a more technically intensive lens. Many successful candidates demonstrate large-scale engineering work or mathematically sophisticated research projects. As a result, the gap between narrative strength and technical artifacts can become more noticeable in that context.

Information Gaps in Your Current Profile

Several elements that could significantly affect your archetype positioning were not included in the materials provided.

You have not yet provided:

  • Specific extracurricular activities related to data science, programming, or research
  • Technical projects, coding work, or GitHub repositories
  • Statistics or mathematics competitions
  • Research papers or data analysis projects
  • Course rigor information (AP/IB/honors coursework in math or statistics)

Because these details are missing, it is impossible to fully evaluate how visible your technical depth currently appears in the application. If these elements exist but were simply not included in the profile materials, they may already strengthen your positioning considerably. If they are absent, the technical gap identified by the committee becomes more significant.

Gap Score Summary

Dimension Evaluation
Narrative Coherence Strong
Civic Impact Theme Strong
Technical Artifact Visibility Unclear / Potential Gap
Statistical Modeling Depth Moderate Gap
Software Engineering Evidence Moderate Gap

Overall, your positioning is conceptually compelling but depends heavily on whether admissions readers see clear evidence that your civic data work operates at a sophisticated technical level.

The rest of this strategy plan will focus on ensuring that your application materials communicate that depth clearly and efficiently within the limited time remaining before application deadlines.

Proof of Concept: Students Who Turned Data and Code Into Admission‑Level Narratives

Zara Okonkwo, one pattern appears repeatedly among successful applicants to elite computing and data‑focused programs: they combine strong academics with a clear technical identity that shows up through tangible work. Admissions officers are not only evaluating grades and test scores; they are looking for evidence that a student already thinks like a practitioner in the field they claim to love.

Your academic profile (3.94 GPA, 1530 SAT) already signals strong quantitative ability. What ultimately separates admits at places like Berkeley, Carnegie Mellon, and Georgia Tech is how convincingly the application demonstrates a specific direction within computing or data science. Looking at successful applicants provides a useful blueprint for what that clarity looks like in practice.

Success Story #1: Turning Machine Learning Into a Product

Arvin R. – Stanford (Computer Science, AI)

Arvin’s application stood out because it showed a complete technical pipeline rather than just interest in AI. He trained a convolutional neural network on thousands of hand‑sign images, then converted the model into a mobile application capable of running real‑time inference on an iPhone camera.

Several elements made this compelling to admissions readers:

  • The work demonstrated both theoretical understanding (machine learning model training).
  • It showed engineering execution (deploying the model into a usable app).
  • His GitHub repository included a continuous integration system that automatically tested updates.

The result was not just “a student who likes AI.” Instead, the application presented someone who could design, train, deploy, and maintain machine‑learning systems. That technical completeness is exactly what top computing programs want to see.

For students interested in data science or statistics, this kind of artifact signals the ability to transform raw data into working systems that people can use.

Success Story #2: Cryptography With Deep Technical Rigor

Chen J. – Carnegie Mellon (Cybersecurity)

Chen’s project was a blockchain‑based voting system built using zero‑knowledge proofs. The concept itself was ambitious: allow voters to prove they were registered while preserving anonymity.

What strengthened the application was not just the idea but the depth of execution:

  • He implemented the system using Solidity smart contracts.
  • The protocol incorporated cryptographic privacy protections through zero‑knowledge proofs.
  • He documented a self‑conducted “red team” security audit attempting to break the system.

This level of rigor mirrored the type of work students encounter in advanced university computing courses. Carnegie Mellon is known for valuing applicants who already demonstrate serious engagement with the technical foundations of their field, and Chen’s project provided exactly that signal.

In the broader pattern of successful applicants, technically sophisticated artifacts — research analyses, open‑source tools, or data systems — often carry more weight than general interest alone.

Success Story #3: Data Science With Civic Impact

Aisha B. – Harvard (Computer Science + Government)

Aisha’s project analyzed sentencing patterns using publicly available court records. She scraped thousands of cases, cleaned the dataset, and used statistical analysis in R and Python to identify geographic disparities in sentencing outcomes.

What elevated this project was the connection between technical work and real‑world systems:

  • Large‑scale public data collection using web scraping tools.
  • Statistical analysis using standard data‑science libraries.
  • Communication of results to a local city council.

This kind of work reflects a growing trend in admissions: students who frame computing and statistics as tools for understanding societal systems. Universities with strong public‑service missions — particularly Berkeley — often respond well to projects that engage with housing, policing, transportation, healthcare, or other civic datasets.

The underlying signal is that the student sees data science not just as a technical skill set, but as a method for understanding and improving real institutions.

Success Story #4: The Engineering Parallel — Showing the “Builder Mindset”

Liong Ma – MIT & Caltech (Mechanical Engineering)

Liong built a fully functional desktop CNC milling machine using custom‑machined components, stepper motors, and Arduino firmware. His project documentation included design files, control software, and a detailed account of early failures caused by gear backlash.

Although this project sits in mechanical engineering rather than computing, it illustrates a mindset admissions committees value across technical disciplines: the ability to design, build, test, and iterate on complex systems.

The most compelling part of his application was not simply that the machine worked. It was the documentation of the engineering process — the problems encountered and the technical reasoning behind the fixes.

In data science or statistics, the equivalent signal might come from carefully documented analyses, reproducible code repositories, or clearly explained modeling decisions.

Success Story #5: Independent Scientific Inquiry

Rishab Jain – Harvard & MIT (Biomedical Engineering)

Rishab developed a machine‑learning model designed to track organ movement during breathing to improve radiation therapy targeting. His work used hundreds of CT scans and applied deep learning techniques to predict organ displacement.

Two elements made the work particularly compelling:

  • The project addressed a real medical problem with measurable consequences.
  • The methodology resembled genuine research rather than a classroom exercise.

This type of project demonstrates intellectual independence. Admissions readers often look for evidence that a student can formulate a technical question, build a method to investigate it, and evaluate the results.

The Common Pattern Across These Admits

Across these successful applications, several consistent signals appear:

  • A clear technical identity. Each student demonstrated a focused area within computing, engineering, or data science rather than presenting scattered interests.
  • Artifacts that prove competence. Projects produced tangible outputs: datasets, models, hardware systems, or open‑source code.
  • Connection to real systems. Many projects interacted with real‑world data, institutions, or users rather than purely theoretical exercises.
  • Documentation of the process. Admissions readers could see how the student approached problems, debugged failures, and improved their work.

Another theme the committee highlighted across multiple successful applicants is the rise of civic‑oriented data science. Students who analyze public datasets — transportation systems, court records, housing information, or public health statistics — often present a compelling narrative that connects statistical analysis with societal impact.

This pattern aligns particularly well with universities that value public engagement and large‑scale societal problem solving.

Where Information Is Missing in Your Current Profile

One important limitation: you have not yet provided details about your extracurricular activities, technical projects, research experience, coding repositories, or data analysis work.

Without that information, it is impossible to map your profile directly onto any of the success stories above. The examples here demonstrate what strong evidence of interest in data science or statistics can look like, but your application materials will ultimately need to show your own version of that evidence.

If you have completed programming projects, statistical analyses, data visualizations, research papers, or software tools, they should appear clearly in your activities list and potentially in supplemental materials where schools allow it. If those experiences exist but are not yet documented, the application may currently under‑represent your technical engagement.

Why These Examples Matter for Berkeley, CMU, and Georgia Tech

The three universities on your target list all emphasize applied computing and real technical work. Students who succeed in admissions often show evidence that they are already experimenting with the kinds of problems those institutions care about — complex systems, large datasets, or socially relevant technologies.

The examples above illustrate that successful applicants rarely rely on academic metrics alone. Instead, they show how their curiosity translates into technical artifacts and intellectual exploration.

For a student pursuing data science or statistics, the strongest applications typically communicate one simple message: this student already behaves like a data scientist.

06 Essay Strategy

Zara Okonkwo, your essays need to do one thing exceptionally well: reveal the mind behind the numbers. Your GPA (3.94) and SAT (1530) already establish academic strength. What admissions readers still need is evidence of how you think about problems in the real world—especially how your interest in data science intersects with human systems.

The committee repeatedly highlighted the narrative potential in one particular experience: analyzing a police use‑of‑force dataset and eventually presenting findings to the Atlanta City Council. Used correctly, this story can anchor your personal statement because it naturally combines technical curiosity, civic awareness, and intellectual growth. The goal of the essay is not to prove the importance of the project itself, but to show how the way you approach questions changed as you worked through the data.

The strongest essays about technical interests follow a recognizable arc: a small intellectual spark, a moment where the problem becomes more complicated than expected, and a realization that changes how the student sees the world. Your story already contains these ingredients.

Personal Statement: From Data Curiosity to Civic Perspective

The most effective structure for your main essay is a three‑phase narrative that mirrors how your understanding evolved.

  • Hook: The moment the dataset became interesting.
    Start with a vivid moment interacting with the police use‑of‑force dataset. Avoid abstract language about “justice” or “policy.” Instead, ground the reader in something concrete: a messy spreadsheet, an unexpected pattern, or the realization that the data represented real encounters between citizens and institutions.
  • Intellectual Turning Point: Curiosity becomes responsibility.
    This is the emotional center of the essay. At first, the work may have been purely analytical—testing methods, cleaning data, exploring correlations. The turning point occurs when you recognize that analyzing public data can influence real policy conversations. This shift—from technical exploration to civic engagement—is where admissions readers see maturity.
  • Resolution: Presenting the findings.
    End with the moment your analysis reached the Atlanta City Council. The focus should not be the prestige of the audience. Instead, highlight what it felt like to see a dataset transform into a public conversation. The insight might be something like realizing that data science is not just about prediction or optimization but about clarifying complex systems so communities can make better decisions.

This arc works because it shows a progression in how you think: from solving a technical puzzle to understanding the societal context around it.

How to Write the Essay So It Stands Out

Admissions readers encounter many “I analyzed data” essays. The difference between average and memorable essays is process. Focus on moments of thinking rather than achievements.

  • Zoom in on analytical moments. Describe the instant you noticed a pattern or inconsistency in the dataset. Specificity makes intellectual curiosity believable.
  • Show uncertainty. Strong essays include moments where the answer was unclear or the data complicated your assumptions.
  • Translate technical thinking into human language. The reader may not know statistics. Your ability to explain why a pattern matters demonstrates intellectual maturity.
  • Keep the spotlight on perspective. The essay should ultimately answer: How did this experience change the way you think about systems, institutions, or evidence?

Think of the dataset as the “lens” through which you view civic systems. The essay is not about policing itself; it is about how data analysis can shape accountability and public understanding.

School‑Specific Supplemental Strategy

Your target schools tend to value intellectually driven students who enjoy solving complex problems. Each school’s supplements should emphasize a slightly different dimension of the same intellectual identity.

School Essay Emphasis Strategic Angle
UC Berkeley Public impact of data Expand on how analyzing civic datasets can influence policy discussions and community accountability.
Carnegie Mellon Technical curiosity Highlight the analytical side of the project—how you approached messy data, built models, or refined methods.
Georgia Tech Problem‑solving mindset Frame data science as a tool for understanding complex systems and designing solutions.

Even though each essay emphasizes a different angle, they should all reinforce the same core identity: someone who uses statistical reasoning to understand real‑world systems.

Topic Ideas for Secondary Essays

Your supplemental essays should widen the picture beyond the main story. Because your application theme already centers on civic data analysis, the other essays should highlight different dimensions of your thinking.

  • The “Why This Major” essay: Describe what fascinates you about extracting meaning from complex datasets. Avoid generic statements about liking math; instead discuss the intellectual puzzle of translating raw information into explanations.
  • The community essay: Connect data analysis to public understanding—how clear evidence can improve discussions about complicated social issues.
  • The curiosity essay: Write about a question you pursued simply because it intrigued you. The emphasis should be the investigative mindset.

If there are other activities, research, or leadership experiences that shaped your interest in statistics or data science, they could be valuable here. However, you have not provided details about additional activities or projects yet. If they exist, consider weaving them into supplemental responses so your application shows breadth beyond a single project.

Common Pitfalls to Avoid

  • Turning the essay into a policy argument. Admissions readers care more about your intellectual journey than about the conclusions you reached.
  • Overloading with technical jargon. Clarity is more impressive than complexity.
  • Writing a résumé essay. The story should focus on one experience rather than summarizing many accomplishments.

The most compelling essays about data science reveal something subtle: the student enjoys wrestling with ambiguity. Your story already contains that element because civic data rarely produces clean answers.

Application Essay Timeline

Month Key Actions Target Outcome
August
  • Draft personal statement centered on the police use‑of‑force dataset story.
  • Identify 2–3 supplemental essay themes for each school.
Complete first full personal statement draft.
September
  • Revise personal statement to sharpen the intellectual turning point.
  • Write UC Berkeley PIQ responses and initial Georgia Tech supplements.
Second draft of all major essays.
October
  • Finalize UC application essays.
  • Draft Carnegie Mellon supplements.
Polished UC submissions.
November
  • Complete final revisions on remaining essays.
  • Proofread for clarity, voice, and narrative flow.
Submission‑ready essays across all applications.

If executed well, your essays will position you not simply as a strong student in statistics but as someone who sees data as a tool for understanding and improving civic systems. That perspective—combining analytical rigor with social awareness—fits naturally with the intellectual cultures of Berkeley, Carnegie Mellon, and Georgia Tech.

10. Application Execution: Turning a Strong Profile into a Clear, Credible Application

Zara, at this stage the focus is not adding new achievements but making sure every part of your application clearly communicates your quantitative strength and technical work. Admissions readers move quickly through applications, and the difference between a strong file and a confusing one is often execution: how clearly coursework, tools, and project outcomes are presented across the application platforms.

The committee noted that some of your strongest signals — advanced math preparation and technical projects — can easily get buried if they are not explicitly surfaced. The goal of this section is to ensure the Common Application, UC Application, and school‑specific portals all reinforce the same message: you are a technically capable student prepared for rigorous data science and statistics programs.

Make the Additional Information Section Work for You

The Additional Information section is one of the most underused spaces in the application. For you, it should serve two specific purposes: clarifying quantitative coursework and directing readers to technical work that cannot fit in the activity descriptions.

If your transcript does not make your full math progression obvious, use this section to list the highest math and quantitative courses you have taken. This is particularly important for programs like Berkeley, Carnegie Mellon, and Georgia Tech, where admissions readers are closely evaluating math preparation.

If your transcript formatting does not clearly show rigor, you can list coursework like this:

  • Highest math completed or in progress (for example: Calculus, Multivariable Calculus, Linear Algebra, or Statistics — if applicable)
  • Advanced quantitative electives or dual‑enrollment math courses
  • Any advanced statistics or data analysis coursework

If you have taken relevant courses but they are not obvious from the transcript titles, the Additional Information section is the correct place to clarify them.

If these courses are not yet listed in your materials, you have not provided them yet — and adding them is important for data science and statistics admissions.

Directly Link Technical Work (GitHub and Documentation)

Admissions readers rarely have time to search for student projects. If you want your technical work to be seen, you must link to it clearly.

For your civic data project and any open‑source contributions, include direct links to the repository or documentation.

Best practice:

  • Place the link in the activity description if space allows
  • Repeat the link in the Additional Information section
  • Use clean, readable URLs (GitHub repository page, project documentation, or demo page)

A simple format works well:

  • Project repository: github.com/username/projectname
  • Documentation or demo: projectsite.com

The goal is not to make admissions officers review the entire repository — it is to signal that the work exists, is real, and can be verified.

Strengthen Activity Descriptions with Technical Detail

The Activities section is one of the most constrained parts of the application, but it is also where many technically oriented applicants lose clarity by writing descriptions that are too general.

Instead of describing projects broadly, make sure each activity specifies the technical tools and analytical methods you used.

For example, activity descriptions should clearly mention:

  • Programming languages (e.g., Python, R, SQL — if applicable)
  • Data frameworks or libraries
  • Statistical methods or modeling approaches
  • Data visualization tools

For data‑focused work, admissions readers want to see evidence that you actually built or analyzed something, not just that you “worked on data.” Technical specificity signals competence.

If your current activity descriptions only describe goals or topics rather than methods, revise them before submission.

Show Evidence of Real Outcomes

Selective universities look for signals that projects extend beyond the classroom. Even small outcomes matter if they are clearly stated.

Where possible, briefly include evidence of impact within activity descriptions or the Additional Information section.

Examples of concise outcomes:

  • Presented findings to a community group or school audience
  • Project used by a local organization or community group
  • Referenced by local media or newsletters
  • Open‑source code adopted or starred by other users

The description does not need to be long — even a short phrase such as “presented findings to local stakeholders” or “repository publicly available for community use” can communicate that the project produced something tangible.

If your application currently describes the project but does not mention outcomes, this is a critical revision to make.

Platform-Specific Submission Tips

Platform Execution Priority
Common Application (Carnegie Mellon, Georgia Tech)
  • Ensure activity descriptions emphasize technical tools and methods
  • Use Additional Information to clarify advanced math coursework
  • Include links to GitHub or documentation if relevant
UC Application (UC Berkeley)
  • Use activity descriptions to highlight technical methodology
  • Include concise outcomes for projects
  • Link repositories in the description field when appropriate
School Portals
  • Double‑check that links remain clickable or easily copyable
  • Upload any optional materials only if they clearly add value

Pre‑Submission Quality Control Checklist

  • Every technical activity specifies programming languages, tools, or analytical methods.
  • The civic data project includes a direct repository or documentation link.
  • Open‑source contributions include a visible reference or link.
  • Advanced math or quantitative coursework is clearly listed or clarified.
  • Each major project includes at least one outcome (presentation, usage, publication, or citation).
  • All links are tested and open correctly.
  • Activity descriptions stay within character limits but remain technically specific.

Senior-Year Execution Calendar

Month Key Actions
September
  • Finalize activity descriptions with technical tools and analysis methods.
  • Prepare GitHub repository links and documentation for major projects.
  • Draft the Additional Information section listing highest math coursework.
October
  • Complete application entries for each platform.
  • Verify that project outcomes are included where possible.
  • Review essays and polish messaging (see §06 Essay Strategy).
November
  • Submit Early Action applications where applicable.
  • Confirm that links and formatting appear correctly in submitted previews.
December
  • Submit remaining applications.
  • Monitor applicant portals and complete any required updates.

If executed carefully, these steps ensure that admissions readers immediately see the strongest parts of your profile: rigorous math preparation, real technical work, and projects that demonstrate applied data skills. At highly selective programs in data science and statistics, clarity and precision in how you present those strengths can make a meaningful difference.

09 Backup Plans: Keeping Multiple Pathways Open

Zara Okonkwo, your target list includes three universities with extremely competitive admissions environments, particularly for data science and statistics pathways. Even with your strong academic metrics, outcomes at schools like UC Berkeley and Carnegie Mellon can be unpredictable. A smart strategy is to prepare parallel options that still advance your long‑term interest in data science while giving you flexibility if initial results do not land as hoped.

The goal of a backup plan is not simply “a safer college.” It is ensuring that wherever you enroll, you still gain access to strong quantitative training, applied data opportunities, and pathways into the kinds of civic or policy-oriented analytics work that the committee identified as a distinctive theme worth developing.

1. Broadening the Data Science School List

If admissions results from your current target schools are mixed, the most effective safeguard is expanding your application list to include additional universities with strong statistics or applied data science departments.

Rather than focusing only on schools with famous “Data Science” majors, consider programs built around statistics, applied mathematics, or analytics. These fields often provide nearly identical technical training and can sometimes offer more flexibility in coursework.

In particular, look for universities that highlight:

  • Applied data science curricula
  • Data science programs connected to public policy or social impact
  • Interdisciplinary analytics programs that combine statistics and civic decision‑making

This type of environment aligns well with the civic data analysis theme the committee flagged as promising. Even if the school’s program title differs slightly (statistics, analytics, data science, etc.), the key question is whether the curriculum emphasizes real‑world datasets and societal applications.

If you have not yet built a broader list beyond the three universities listed above, consider adding several additional options in the target and likely ranges that still have strong quantitative departments.

2. Programs Focused on Applied Data and Policy Analytics

Another useful backup strategy is targeting universities that intentionally connect data science with policy analysis, civic technology, or social systems.

Many universities now house interdisciplinary institutes that focus on:

  • Urban data analytics
  • Public policy data labs
  • Government technology and civic data
  • Statistical analysis of social systems

These environments can provide unusually strong undergraduate opportunities because the research often depends on real government or community datasets. If your applications emphasize interest in socially relevant data work, programs with these centers may respond particularly well.

As you review additional schools, look specifically for:

  • Public policy schools that collaborate with statistics or data science departments
  • Civic technology institutes
  • Urban analytics labs or public data research centers

The presence of these resources matters more than whether the undergraduate major is labeled “data science.”

3. Building Opportunities After Enrollment

A backup strategy should also consider what happens after you arrive on campus. Even if you attend a university that was not your original first choice, you can still build a strong data science profile during your first year.

Many universities allow first‑year students to work in research groups or data labs once they demonstrate quantitative ability through introductory coursework.

After enrolling, consider exploring:

  • Public policy research labs that analyze government data
  • Civic analytics centers studying transportation, housing, or public health
  • Faculty research groups working with large datasets

These opportunities can deepen your applied data experience and build relationships with faculty who may later supervise research projects or provide recommendations.

4. Internal Major Changes and Academic Flexibility

If admission into a specific data science major is limited at the university you attend, another pathway is entering through a related quantitative field and transitioning later.

Common starting majors include:

  • Statistics
  • Applied mathematics
  • Computer science
  • Analytics or quantitative social science

Many universities allow students to move into specialized tracks once they complete foundational coursework. Strong performance in introductory programming, probability, and statistics classes can open doors to internal transfers or advanced research placements.

If that situation arises, strengthening your technical artifacts during your first year—such as data analysis projects, coding portfolios, or research collaborations—can make those transitions more achievable.

5. Transfer Pathway (If Outcomes Are Unsatisfactory)

Another backup option is the transfer pathway. If your initial admissions cycle does not result in the environment you hoped for, transferring after your first or second year remains a viable route.

Successful transfer applicants typically demonstrate:

  • Excellent college grades in quantitative courses
  • Evidence of technical skill development
  • Research or applied data experience

For a student pursuing statistics or data science, this often means performing strongly in early courses such as calculus, linear algebra, statistics, and programming. Pairing that coursework with involvement in a data-focused research group or analytics lab can strengthen a future transfer application.

This pathway requires careful planning from the start of your first year, but it ensures that one admissions cycle does not permanently determine your academic trajectory.

6. Gap Year Considerations (Only if Circumstances Justify It)

A gap year is generally less common for students pursuing quantitative majors unless there is a clear plan for meaningful work or study during that time.

If you were to consider this option, it would only make sense if you could spend the year:

  • Developing substantial data analysis projects
  • Working with organizations that use civic or public datasets
  • Building a technical portfolio that significantly strengthens a reapplication

Because you are already a senior applying this cycle, this option should be viewed as a contingency rather than a primary plan.

Monthly Contingency Preparation Timeline

Month Backup Plan Actions
September
  • Finalize a broader school list that includes additional statistics or applied data programs
  • Research universities with civic data labs or policy analytics institutes
October
  • Ensure applications include a balanced range of reach, target, and likely schools
  • Confirm that each backup school offers strong statistics or applied data coursework
November
  • Submit Early Action applications where available
  • Prepare remaining applications before winter deadlines
December–January
  • Submit remaining applications
  • Research undergraduate research programs and civic analytics labs at applied schools
March–April
  • Compare admitted schools based on research access, statistics curriculum, and applied data opportunities
  • Identify faculty labs or institutes aligned with civic data analysis

Zara Okonkwo, the key idea behind this backup strategy is control. Even if outcomes at highly selective programs are uncertain, you can still ensure that every path available to you leads to strong quantitative training and meaningful real‑world data work. The right environment for applied statistics or civic analytics can exist at many universities—not just the most selective ones.

14. Recommendation Strategy

Zara, your recommendation letters need to do two very specific jobs for Data Science / Statistics programs: demonstrate that you can handle intense quantitative coursework and show that you already apply data analysis to real-world problems. The committee noted two existing elements of your profile that can accomplish this if your recommenders highlight them clearly: your quantitative academic ability and your civic data project that led to a presentation connected to the Atlanta City Council.

Strong recommendation strategy is less about collecting many letters and more about choosing writers who each illuminate a different dimension of your work. For your target schools — UC Berkeley, Carnegie Mellon, and Georgia Tech — the most persuasive combination will show (1) rigorous mathematical thinking and (2) real-world application of data analysis to public issues.

Primary Academic Recommender: Math or Statistics Teacher

Your first letter should come from a math or statistics teacher who has directly observed your analytical reasoning in a demanding course. Highly quantitative programs want confirmation from a classroom authority that you are prepared for proof-heavy math, statistical reasoning, and abstract problem solving.

This recommender should emphasize:

  • Analytical thinking — how you approach complex or unfamiliar problems.
  • Depth of reasoning — moments when you went beyond procedural answers and demonstrated conceptual understanding.
  • Intellectual curiosity in quantitative topics.
  • Readiness for rigorous coursework typical of data science, statistics, and machine learning programs.

You have not provided details about which specific math or statistics courses you have taken or which teacher knows you best. Choose someone who can describe your thinking process in detail rather than someone who simply gave you a high grade.

When preparing this teacher, give them concrete reminders of moments that show your reasoning style. For example:

  • A challenging assignment or project where you developed an unusual approach
  • Times you asked advanced or exploratory questions in class
  • Situations where you helped peers understand a difficult concept

The goal is a letter that makes an admissions reader believe you will thrive in mathematically demanding environments like Berkeley’s or Carnegie Mellon’s quantitative programs.

Second Recommender: Civic Data Project Supervisor

Your second key recommender should be someone who worked closely with you on the civic data project. According to the committee’s review, this project involved collecting data, building analysis tools, and publicly presenting findings.

This letter should focus on initiative and applied data work rather than classroom performance.

Ask this recommender to describe:

  • How you gathered and structured data for the project
  • The analytical tools or methods you used to interpret that data
  • Your initiative in shaping the project rather than just participating
  • Your ability to communicate data insights to non-technical audiences

Admissions readers value students who move beyond theoretical interest and actually use data to solve problems. This letter should show that you already think like a data scientist: identifying questions, gathering evidence, analyzing patterns, and presenting conclusions.

If possible, ask this recommender to include a short anecdote illustrating how you approached the project’s analytical challenges or how your findings influenced discussion or decision-making.

Third Perspective (If Allowed): Civic Impact Verifier

If a school allows an additional recommender, consider a mentor or partner connected to the civic impact of the project. This could be a teacher, advisor, or community collaborator who was involved when you presented your findings connected to the Atlanta City Council.

The purpose of this letter is credibility and impact.

This recommender should confirm:

  • The authenticity and significance of the Atlanta City Council presentation
  • The level of preparation and analysis required for the presentation
  • Your role in communicating the findings publicly
  • The project’s relevance to community issues

For admissions officers reviewing hundreds of applications, external validation matters. A mentor who can explain how your work engaged with real civic institutions signals that your data work had tangible relevance beyond school assignments.

If such a recommender exists, this letter could be especially valuable for schools that appreciate civic technology and applied analytics, such as Georgia Tech.

If you do not currently have a mentor or partner who can credibly describe this aspect of the project, do not attempt to force a third letter. Two strong recommendations are better than three generic ones.

How Each Letter Should Position You

Recommender Main Theme Evidence They Should Provide
Math / Statistics Teacher Quantitative rigor Problem-solving ability, depth of reasoning, readiness for advanced coursework
Civic Data Project Supervisor Applied data science Data collection, analysis tools, initiative, communicating insights
Civic Impact Mentor (optional) Real-world impact Atlanta City Council presentation, community relevance, credibility of project outcomes

Together, these letters create a coherent narrative: Zara Okonkwo as a student who not only excels in mathematical reasoning but also applies data analysis to civic problems.

Preparing Your Recommenders Effectively

Even excellent teachers write stronger letters when students provide helpful context. Prepare a concise recommender packet for each writer containing:

  • A one-page resume of your activities and academic interests
  • A short description of the civic data project and its outcomes
  • Deadlines for each school
  • A brief note explaining why you are interested in Data Science / Statistics

Do not attempt to script the letter. Instead, highlight the specific experiences you hope they might reference.

Because you are applying this cycle, timing matters. Teachers often receive many requests, and the earlier you ask, the more thoughtful the letter tends to be.

School-Specific Considerations

Your target universities emphasize slightly different aspects of recommendation letters.

  • UC Berkeley: values intellectual curiosity and evidence of independent thinking. Your math teacher letter will carry particular weight.
  • Carnegie Mellon: highly focused on quantitative ability and problem-solving depth. The academic recommender should clearly discuss your analytical reasoning.
  • Georgia Tech: often appreciates students who connect technical work with real-world impact. Your civic data project letters help here.

None of these schools require excessive numbers of recommendations, so focus on quality and specificity rather than quantity.

Recommendation Request Timeline

Month Actions
August
  • Confirm your math/statistics teacher recommender and civic project supervisor.
  • Ask both recommenders in person if possible and provide your recommender packet.
  • Enter recommenders into application portals once accounts are active.
September
  • Follow up with recommenders and confirm submission timelines for Early Action schools.
  • Provide any updates that may help them (see §06 Essay Strategy for positioning).
  • If using a civic impact mentor as a third recommender, confirm whether each school accepts additional letters.
October
  • Verify that recommendation submissions are complete for Early Action deadlines.
  • Send a brief thank-you note and update recommenders on application progress.
November–December
  • Confirm submission for any remaining regular decision schools.
  • Keep recommenders informed of outcomes and express appreciation.

Handled well, your recommendations will reinforce a clear story: a student with the quantitative mindset needed for advanced statistics and the initiative to use data in meaningful civic contexts. That combination is exactly what data science programs hope to see.

08 Creative Projects: Turning the Police Use‑of‑Force Dataset into a Flagship Data Science Portfolio

Zara Okonkwo, for Data Science and Statistics programs at Berkeley, Carnegie Mellon, and Georgia Tech, the most convincing evidence of readiness is a technically rigorous, publicly visible data project. The committee flagged the police use‑of‑force dataset you referenced as the strongest foundation for such a project. Right now, it likely reads as a data analysis or research activity. Your opportunity before application deadlines is to elevate it into a full, professional-grade data science artifact: an open dataset, reproducible pipeline, and technical analysis that demonstrates both statistical depth and software engineering maturity.

The goal is not simply to show that you analyzed data. The goal is to demonstrate how you think like a data scientist: how you collect, clean, model, document, and publish data so that other people can use it.

Project Vision: An Open Policing Data Platform

Instead of presenting a one-off analysis, structure the project as a reusable research resource. Admissions readers in technical programs respond strongly to projects that combine statistics, software engineering, and public transparency.

Your project can be framed as an open policing analytics platform that includes three layers:

  • Dataset: A clean, structured, downloadable dataset documenting police use-of-force incidents.
  • Reproducible analysis: Statistical modeling exploring patterns and disparities.
  • Public tools: An API or interactive dashboard allowing others to explore the data.

This structure signals exactly the type of thinking expected in modern data science programs.

Technical Architecture

To make the project credible at the level expected by Berkeley, CMU, and Georgia Tech, organize the repository like a professional data science project rather than a school assignment.

Component Purpose Suggested Stack
Data Collection Pipeline Automates acquisition and cleaning of use‑of‑force data Python, Pandas, Jupyter, possibly BeautifulSoup if scraping
Data Processing Standardizes fields, handles missing values, and documents assumptions Pandas, NumPy
Statistical Modeling Analyzes trends and potential disparities Python (statsmodels, scikit‑learn) or R
Interactive Dashboard Allows users to explore patterns visually Plotly Dash, Streamlit, or Observable
Public API Allows external researchers to query the dataset FastAPI or Flask
Documentation Explains methodology and limitations Markdown documentation and technical report PDF

The key signal here is reproducibility. Someone downloading your repository should be able to run the pipeline and recreate the analysis.

Advanced Statistical Modeling

Right now, the project likely focuses on descriptive analysis. To strengthen its academic credibility for Data Science and Statistics programs, extend the analysis with more sophisticated modeling.

Consider adding:

  • Regression analysis examining relationships between incident variables (for example, location characteristics or time trends) and the likelihood of use‑of‑force events.
  • Trend modeling to evaluate changes over time across jurisdictions or departments.
  • Fairness analysis exploring potential disparities across demographic groups where data allows.
  • Causal inference approaches (even exploratory ones) discussing whether policy changes appear associated with measurable shifts in outcomes.

Equally important is documenting limitations. Admissions readers appreciate students who acknowledge uncertainty, missing data, and bias in datasets. Transparency strengthens the credibility of the project.

The Technical Report

Your project should include a formal technical report that reads like a condensed academic paper. This report can be linked in your application and hosted in the GitHub repository.

Structure the report with sections such as:

  • Introduction and motivation
  • Data sources and collection methodology
  • Data cleaning and preprocessing decisions
  • Statistical models used
  • Key findings and visualizations
  • Limitations and ethical considerations
  • Future work

Keep the tone analytical rather than advocacy-oriented. Programs like CMU and Berkeley especially respond to students who treat social datasets with methodological rigor.

Making the Project Reusable

A major step that distinguishes standout portfolios is enabling other people to build on the work.

Consider incorporating at least one of the following:

  • Downloadable dataset with clear schema documentation.
  • Public API allowing queries by year, region, or incident type.
  • Interactive dashboard where users can filter and visualize trends.

This moves the project from “analysis” to “infrastructure.” That shift is extremely valuable for Data Science admissions.

GitHub Portfolio Strategy

Your GitHub repository should be structured like a professional open-source project. Many admissions readers—especially in technical departments—will glance at repository organization.

Suggested structure:

  • /data – processed datasets
  • /notebooks – exploratory analysis
  • /pipeline – scripts for cleaning and transformation
  • /models – regression or modeling code
  • /dashboard – visualization application
  • /docs – methodology and technical report

The README file should clearly explain:

  • What the project does
  • Why the dataset matters
  • How to reproduce the analysis
  • How to use the dashboard or API

A clear README alone dramatically improves how admissions readers perceive the project.

Demonstrating Real‑World Impact

If possible before application submission, track whether anyone actually uses the project. Even small signals of adoption strengthen credibility.

Examples include:

  • GitHub stars or forks
  • Researchers or students downloading the dataset
  • Users interacting with the dashboard
  • Mentions in community forums or data science communities

You do not need large numbers. Even limited external use demonstrates that the project has value beyond a class assignment.

How This Strengthens Your Application

For Data Science and Statistics admissions, this project demonstrates several qualities simultaneously:

  • Statistical reasoning
  • Data engineering ability
  • Software development skills
  • Ethical awareness around real-world datasets
  • Ability to publish and communicate technical work

A well-executed version of this project can function as the centerpiece of your technical portfolio.

Application‑Season Build Calendar

Month Key Actions Target Outcome
August
  • Finalize dataset structure and cleaning pipeline
  • Create GitHub repository and project documentation
  • Outline statistical modeling plan
Fully reproducible dataset and project framework
September
  • Implement regression and trend analysis models
  • Develop core visualizations
  • Draft the technical report
Complete statistical analysis and early report draft
October
  • Launch dashboard or API interface
  • Refine documentation and README
  • Prepare portfolio link for applications
Public-facing project ready for submission
November
  • Track usage or engagement metrics
  • Polish visuals and explanations
  • Align project narrative with application materials (see §06 Essay Strategy for approach)
Fully polished portfolio artifact

Zara Okonkwo, this project does not require inventing something entirely new. The leverage comes from elevating the work you already began into a rigorous, open, technically documented data science platform. Done well, it becomes a concrete demonstration of the type of analytical and engineering thinking programs like Berkeley, CMU, and Georgia Tech expect from future data scientists.

07 — School‑Specific Strategy

Zara Okonkwo, the key strategic task across your three target schools is not changing your profile at this late stage of senior year—it is framing your existing work so that each university sees the strongest version of its institutional fit. The committee discussion highlighted that your application narrative likely centers on civic‑oriented data work, but you have not provided details about the project itself in your profile. Because of that gap, the tactics below assume that such a project exists while emphasizing how to present it effectively. If the project details are not yet clearly written in your activities list or essays, you should add them immediately.

Each of these three universities evaluates “data science / statistics” applicants through a slightly different lens:

  • UC Berkeley: mission alignment and civic impact
  • Carnegie Mellon: technical depth and evidence of serious computing ability
  • Georgia Tech: applied systems thinking and real‑world engineering use of data

Your application should subtly shift emphasis for each school.

University of California, Berkeley — Lean Hard Into Public‑Mission Alignment

Berkeley is the one school in this group where institutional mission fit can become a major advantage. The committee noted that civic‑oriented data work naturally aligns with Berkeley’s culture around open data, public research, and technology serving society.

If your application includes a civic data project (as referenced in the committee discussion), your goal is to present it not just as a technical exercise but as an example of data science used for public good.

Angles worth emphasizing in the Berkeley supplements:

  • Public mission: frame your interest in statistics or data science as a tool for improving real systems (government, infrastructure, policy, community outcomes).
  • Open‑data culture: Berkeley has a strong ecosystem around open datasets, civic technology, and public research collaboration. Connect your project to this ethos if possible.
  • Curiosity about messy real‑world data: highlight how working with imperfect datasets revealed structural problems or inequities.

Because you have not provided details about your activities list or projects, double‑check that the application explicitly communicates:

  • What dataset you worked with
  • What statistical or computational methods you used
  • What insight or outcome resulted

If those elements are missing, admissions readers may interpret the project as policy commentary rather than data science work.

“Why Berkeley” essay direction:

  • Connect your civic data interests to Berkeley’s culture of public research and technology serving society.
  • Discuss curiosity about large‑scale public systems and how data can improve them.
  • Avoid generic references to Silicon Valley; focus instead on Berkeley’s intellectual culture and public mission.

Berkeley does not offer Early Decision or Early Action, so your advantage here comes entirely from mission fit and narrative clarity.

Carnegie Mellon University — Demonstrate Technical Depth

CMU is the most difficult admit in this list, and the challenge is not academic readiness—it is relative comparison to an extremely technical applicant pool.

Applicants to CMU programs related to data science or statistics often present artifacts such as:

  • published or preprint research papers
  • high‑level programming projects
  • major competition placements
  • widely used software or tools

You have not provided information about competitions, research publications, or software projects. If those exist, they must be clearly visible in your activities list and supplemental responses.

The committee flagged a key risk: if your civic data project is described mainly through policy implications or visualizations, CMU readers may question the underlying technical depth.

Your strategy should therefore shift emphasis toward methodology and computation.

In the CMU supplements and activities descriptions, make sure you explicitly communicate:

  • What programming languages or tools were used
  • What statistical models or algorithms were applied
  • How the dataset was processed or engineered
  • Any original technical decisions you made

If the project involved meaningful coding or statistical modeling, explain that clearly. If the technical side is understated, the application may appear more like policy analysis than serious computational work.

“Why CMU” essay direction:

  • Focus on technical curiosity and computational problem‑solving.
  • Describe what excites you about building rigorous data models.
  • Position yourself as someone motivated by complex quantitative challenges.

Because the committee categorized CMU as a low‑probability school, applying Early Decision here would carry risk. Unless CMU is unquestionably your first choice and your strongest materials align technically with their expectations, you should generally avoid committing your ED slot here.

Georgia Institute of Technology — Emphasize Applied Systems Thinking

Georgia Tech occupies a middle ground between the other two schools. Its programs tend to respond strongly to applicants who connect computing, statistics, and real‑world systems.

Your civic data interests—assuming they are part of your application—fit naturally into that framing.

For Tech, the emphasis should be:

  • Using data to analyze complex systems
  • Applying statistical thinking to infrastructure or societal problems
  • Building tools or models that improve decision‑making

Georgia Tech readers often respond well to applicants who see data science as an engineering discipline applied to real environments, rather than purely theoretical statistics.

Because you are a Georgia resident, Tech also offers an important strategic opportunity.

Early Action strategy:

  • Apply Early Action to Georgia Tech.
  • This signals strong interest and allows you to receive a decision earlier in the cycle.
  • It also preserves flexibility for Regular Decision schools.

“Why Georgia Tech” essay direction:

  • Highlight interest in applying data science to operational systems.
  • Emphasize curiosity about how quantitative models influence real decisions.
  • Avoid generic references to “innovation” or “technology leadership.”

Georgia Tech admissions readers often look for applicants who understand that data science sits at the intersection of computation, statistics, and large‑scale systems. Make sure your essays communicate that integrated perspective.

Application Timing Strategy

School Application Plan Strategic Reason
Georgia Tech Early Action Strong in‑state alignment and earlier decision timeline
UC Berkeley Regular Decision (UC deadline) Focus on mission fit and strong UC essays
Carnegie Mellon Regular Decision Preserves flexibility given high competition

Senior Fall Execution Calendar

Month Key Actions
August • Finalize activities descriptions with clear technical details for your data work
• Draft school‑specific essay angles (see §06 Essay Strategy for writing approach)
• Confirm Georgia Tech Early Action timeline
September • Complete Georgia Tech supplemental essays emphasizing systems‑level data thinking
• Refine UC essays to highlight civic impact and public mission alignment
• Ensure project descriptions clearly show statistical or computational methods
October • Submit Georgia Tech Early Action application
• Draft Carnegie Mellon supplements with strong technical framing
• Review activities section for clarity of tools, methods, and outcomes
November • Submit UC Berkeley application before UC deadline
• Finalize Carnegie Mellon essays
• Conduct final application audit for technical clarity in project descriptions
December • Submit Carnegie Mellon Regular Decision application
• Prepare for possible Georgia Tech Early Action decision
• Organize materials for any additional schools if needed

The most important takeaway: the same core work can appeal to all three schools, but the story you emphasize must change. Berkeley should see civic impact and public mission alignment, CMU must see technical rigor, and Georgia Tech should see applied systems thinking.

If your application materials currently emphasize only one of those dimensions, revising the framing before submission could meaningfully strengthen your chances.

12. What Not To Do

Zara Okonkwo, with deadlines approaching, the biggest risks in your application are not about grades or test scores. Your 3.94 GPA and 1530 SAT already show academic readiness. The real danger is how your work in data science or statistics is interpreted by readers who only spend a few minutes with your file. Admissions officers will look for clear evidence that you personally understand and apply technical methods. When that evidence is missing or vague, strong work can be discounted quickly.

The committee flagged several patterns that frequently weaken otherwise competitive data‑focused applications. Avoid the following pitfalls carefully as you finalize your materials.

Do Not Let a Civic Impact Story Replace Technical Evidence

Applications centered on social impact—especially data used for public good—can be compelling. However, one of the risks in this area is presenting a project primarily as a community or civic story without showing the statistical or computational work that produced the results.

If an admissions reader finishes your description knowing why the issue matters but not how the analysis was performed, they may assume the technical component was minimal. This is particularly risky for data science applicants to highly technical programs such as UC Berkeley, Carnegie Mellon, and Georgia Tech.

Common mistakes that weaken an application:

  • Describing the social problem in detail but mentioning the analysis only briefly.
  • Focusing on outcomes (“we helped the community understand X”) instead of the statistical process used.
  • Leaving out the models, algorithms, or analytical methods used.

The result is that a potentially strong project reads like advocacy rather than technical investigation. At highly selective technical programs, that distinction matters.

If you include civic‑oriented data work, avoid letting the narrative become purely about impact. The admissions reader must clearly see the analytical depth behind the results.

Do Not Leave Open‑Source Work Vague

If you plan to reference open‑source code, shared datasets, or collaborative repositories, vague descriptions can unintentionally weaken your profile.

Admissions reviewers often encounter applicants who claim “open‑source work” but provide almost no context. When the scope is unclear, readers frequently assume the contribution was small.

Risky phrasing to avoid:

  • “Contributed to an open‑source data project.”
  • “Worked on a GitHub repository with others.”
  • “Helped develop a data analysis tool.”

Without context, these statements raise more questions than they answer. Reviewers may wonder:

  • Was this a major contribution or a small fix?
  • Did you design the statistical approach or simply implement instructions?
  • Was the code actually used by others?

If open‑source work is included anywhere in your application materials and remains vaguely described, readers often default to assuming minimal impact. That is a preventable interpretation problem.

If you do reference this type of work, clarity about scope and ownership becomes essential. Otherwise it can quietly undermine what might otherwise be a strong technical signal.

Do Not Assume Team Competitions Prove Individual Skill

Team competitions—especially in data science, math, or analytics—are common activities among applicants interested in statistics or machine learning. However, admissions readers do not automatically interpret team results as evidence of individual technical ability.

If a competition result is presented without explanation, the reader has no way to determine what you personally did.

Problematic patterns include:

  • Listing a team placement with no explanation of your role.
  • Describing the competition outcome but not your contribution.
  • Using “we built” or “our team analyzed” without clarifying your responsibilities.

From the reviewer’s perspective, several possibilities exist:

  • You may have led the modeling work.
  • You may have handled data cleaning or visualization.
  • You may have had a non‑technical role.

If the application never clarifies this, readers cannot confidently attribute the technical achievement to you. For applicants to programs like CMU or Berkeley, that ambiguity can weaken the perceived strength of the activity.

Team work is valuable, but the admissions reader must understand your individual contribution.

Do Not Submit Data Projects That Look Like Simple Visualization

Another common mistake among data science applicants is presenting projects that appear to focus primarily on aggregation or visualization.

Dashboards, charts, and visual summaries are useful tools. But if the project description emphasizes visual output without mentioning deeper statistical analysis, admissions readers may interpret the project as introductory rather than advanced.

Signals that trigger this interpretation include:

  • Descriptions focused on charts, dashboards, or plots.
  • Mentioning data collection and visualization but not modeling or inference.
  • No explanation of statistical reasoning behind the results.

This can unintentionally place a project in the category of “basic data exploration” rather than serious analytical work.

For highly quantitative programs, readers typically look for evidence of:

  • statistical reasoning
  • modeling approaches
  • methodological choices
  • interpretation of results

If those elements are absent from the description, the project can appear superficial even if substantial work actually occurred.

Do Not Leave Technical Work Implicit

A broader theme connects all of these pitfalls: assuming the reader will infer technical depth without seeing it explicitly described.

Admissions officers reading thousands of applications rarely infer complexity that is not directly visible. When technical work is implied rather than clearly stated, the safest interpretation from their perspective is that the analysis was limited.

This is especially important for applicants targeting quantitative majors. Programs in data science and statistics expect clear evidence that applicants understand analytical tools and methods.

If the application narrative centers on outcomes, collaboration, or impact but leaves the analytical process unclear, the file may read as less technically rigorous than intended.

Application Execution Calendar (Avoidance Focus)

Month Actions to Prevent These Pitfalls
September
  • Audit every activity description for vague language about technical work.
  • Identify any project that currently emphasizes impact more than analytical method.
  • Cross‑check descriptions with your activity strategy (see §04 Activities Positioning).
October
  • Revise project descriptions to ensure statistical methods and analytical steps are clearly visible.
  • Clarify personal roles in any team‑based competitions or collaborative projects.
  • Ensure essays referencing projects include the analytical process (see §06 Essay Strategy).
November
  • Perform a final clarity check: remove vague phrases like “worked on,” “helped with,” or “contributed to.”
  • Confirm that open‑source or collaborative work clearly shows scope and ownership.
  • Ensure each major project reflects analytical reasoning rather than only visualization.

If you avoid these specific traps, your technical interests will come across much more clearly to readers at Berkeley, Carnegie Mellon, and Georgia Tech. The goal is simple but critical: make sure every reviewer can immediately see the analytical thinking behind your work.

Create Your Own Plan

This is a sample. Get your own personalized strategy.

Get Started →