May 25 (edited) • 🎓 Strategy Posts
đź“Ś Mock Personal Statement #2 (Based on Everyday Life)
Earlier this week, I invited you to answer four simple questions about your life, with the goal to show you that even "ordinary" experiences can create powerful personal statements.
Here is your second mock personal statement narrative 🤍
🎯 What I pulled from student #2's answers:
- Childhood interest: Using my computer
- Personality traits: Helpful, intelligent, good listener
- Dream job (one of several): Create impactful tech tool
- Hard small moment: Embarrassment from dressing competition at age 5 (included below)
❗Disclaimer: Everything beyond these details is imagined—this isn’t a full essay nor is it a final draft (more like a first draft / outline!). But that’s the point: I’ve filled in the gaps to show how your everyday experiences already hold the potential for a compelling story.
❕Take note of the depth of emotions shared—vulnerability is crucial and what most students miss. It's called a "personal" statement for a reason.
- Direction I imagined: Computer Science / Data Science major
__________________________________
✏️ Hook
They say “go”—and everyone moves.Four-year-olds are yanking shirts over their heads, slipping into graduation gowns, laughing as they race to get dressed. I’m still holding one sleeve. I can feel the eyes on me. My fingers won’t work. I don’t understand the buttons. My face burns. I’m the last one standing still.
🔍 Intro
- A teacher helps me off stage. My dad hands me a Sprite. I don’t cry, but something locks in: I never want to be caught unprepared again.
- That wasn’t just one moment. I’ve always been wired that way—anxious when things feel out of my control, quick to imagine everything that might go wrong.
- I started noticing the warning signs—small breakdowns before they happened. If I could understand how something failed, maybe I could stop it from failing at all.
đź’Ą Heart / Conflict
- When my bike chain jammed in front of my friends, I froze. I told them I’d catch up, then walked it home—face hot, jaw tight. It wasn’t just that I didn’t know how to fix it. It was being seen not knowing.
- That weekend, I took it apart and rebuilt it again and again. Not to impress anyone—just to quiet the panic. Understanding how something worked gave me a way to feel steady.
- I started doing it with everything. Noticing patterns. Catching problems early. Fixing what I could. It wasn’t just for me anymore. I didn’t want anyone I cared about to feel that same kind of helpless.
- I began listening more carefully, too. To what people repeated, skipped, avoided. I didn’t always have answers—but I could notice what mattered, sometimes before they said a word.
🌱 Resolution / Growth
- The shift came quietly—me on the floor with an old fan motor, trying to figure out why it buzzed. No panic this time. Just curiosity. I wanted to understand how each piece worked.
- That feeling stuck. I started building quiet tools—simple automations, stripped-down study guides, scripts that solved small problems before they got loud.
- Whether I’m debugging code or mapping out a data structure, it’s the same instinct: listen closely, notice early, build something that holds. I don’t just want to be ready. I want to design systems that help others feel steady—even in the moments that almost fall apart.
💬 Curious how I built this? Let me know below 👇
Final mock personal statement (#3) tomorrow đź’ś
8
3 comments
đź“Ś Mock Personal Statement #2 (Based on Everyday Life)
powered by
skool.com/the-ivy-wizard-2876
🎓 Free group for students applying to U.S. colleges — run by The Ivy Wizard (Harvard x2, Oxford). Strategy made accessible.
Suggested communities
Powered by