← Mia Zhang's one-pager

Purdue University-Main Campus

Cybersecurity / Computer Science · Committee analysis for Mia Zhang
Full breakdown →
Admit potential
High
High confidence
4 support 0 concern

The committee had unusually strong agreement about the core of your application: you look like a real cybersecurity practitioner. CyberPatriot national finals and actual bug bounty disclosures are credible signals that you are already working inside the security ecosystem. Your GPA and 1510 SAT place you above the typical Purdue CS admit benchmarks, which removed most academic concerns. The only real debate among reviewers was about ceiling: some felt the profile would become truly standout with a visible technical creation such as an open‑source security tool. Even without that, the authenticity and alignment of your cybersecurity work place you solidly in the competitive range for Purdue. If you add one tangible technical artifact or clearer evidence of advanced math/CS coursework, the case becomes significantly stronger.

Committee reads
Academic Reviewer Support
A genuine cybersecurity builder — not just a CS applicant — with national competition credibility and real vulnerability research.
Watch: You have not provided your math/science course rigor, which is a critical signal for Purdue CS.
Major Gatekeeper Support
A rare applicant whose cybersecurity interest is backed by real vulnerability discovery and national competition success.
Watch: Lack of visible programming or research artifacts (GitHub projects, tools, or formal CS coursework) in the provided profile.
Fit Reader Strong support
A real defensive-security practitioner who already lives in the CyberPatriot/bug‑bounty world Purdue’s applied CS culture rewards.
Watch: You have not provided math/science coursework rigor (AP/advanced CS, calculus, etc.), which Purdue readers rely on to confirm technical readiness.
Devil's Advocate Support
A real cybersecurity spike with national competition credibility — strong for Purdue, but one tangible technical creation would make it airtight.
Watch: Whether the student has demonstrated creator-level technical output versus mainly excelling in competitions and structured programs.
▲ Override condition
Release a meaningful open‑source cybersecurity tool or framework (for example a vulnerability scanner, CTF training toolkit, or Linux hardening automation script) with public documentation and real GitHub engagement before application review.
Top actions for this school
10
Publish a tangible cybersecurity project (open‑source tool, security automation script, or CTF training platform) on GitHub with documentation and demonstration of real use.
⚙ Medium effort 🕒 within the next 2–3 months
9
Explicitly document your highest math and CS coursework (AP/advanced CS, AP Calculus, dual‑enrollment math, etc.) in the application activities or additional information section if not obvious on the transcript.
⚙ Low effort 🕒 before submitting applications
8
Write a short technical blog or GitHub README explaining one of your vulnerability discoveries and the security concepts behind it (without revealing sensitive exploit details).
⚙ Low effort 🕒 within 1–2 months
Want the full committee debate, fixability scoring, and reviewer transcripts?
Open full breakdown →