College Application Diagnostic · Example

An anonymized applicant analysis.

This is what a whole-application diagnostic looks like in practice: one anonymized student file — school list, academics, activities, a full Common App essay — read together, with the diagnosis that follows. Identifying details are removed so you can see the analysis, not the person.

The file

Selective U.S. applicant · CS / HCI

Balanced school list. Strong academics. Competitive activities. A polished Common App essay. Nothing looks broken on its own — which is why the whole-file read matters.

College list

Reach · Target · Likely — intended Computer Science / Human-Computer Interaction

  • Cornell University

    CS · HCI interest

    Reach
  • Duke University

    Computer Science

    Reach
  • Northwestern University

    CS + communication

    Reach
  • University of Michigan

    CS · LSA / Eng

    Target
  • University of Washington

    Computer Science

    Target
  • University of Texas at Austin

    Computer Science

    Target
  • Northeastern University

    CS · HCI track

    Likely
  • University of Pittsburgh

    Computer Science

    Likely

List balance looks intentional. The open question is whether the application story matches the CS / HCI direction these schools will read for — not whether the schools themselves are wrong.

Academics

Transcript · testing

Strong

3.92

GPA (UW)

4.55

GPA (W)

1510

SAT

9 AP / advanced

APs

780 Math · 730 EBRW

Highlighted coursework

  • AP Calculus BC
  • AP Computer Science A
  • AP Physics C: Mechanics
  • AP Statistics
  • AP English Language
  • Strongest subjects: mathematics and computer science
  • Course rigor competitive for the intended list
  • No academic red flags in the current file

Extracurriculars

As they currently read in the file

Competitive
  1. 1

    Robotics Team — Software Lead

    12 hrs/wk · 40 wks/yr · 4 years

    Lead a 6-person programming subteam. Built part of the team's autonomous navigation stack. Team qualified for state-level competition.

  2. 2

    Peer Coding Tutor

    4 hrs/wk · 30 wks/yr · 3 years

    Teach younger students Python and introductory CS (~120 hours). Created beginner lesson materials later used by other peer tutors.

  3. 3

    Accessibility Navigation App

    6 hrs/wk · 18 wks · 1 year

    Co-built a school navigation prototype for students with mobility limitations. Interviewed users before defining features; ran a small school pilot.

  4. 4

    Family Café — Weekend Staff

    8 hrs/wk · 48 wks/yr · 2 years

    Weekend shifts handling orders, difficult customer moments, and closing routines.

  5. 5

    Math Club · NHS · Recreational Tennis

    Ongoing

    Consistent but secondary to the four experiences above.

Essays

The Common App essay — read the whole draft.

A café story about noticing what people need. Strong writing. Almost no bridge to robotics, tutoring, accessibility, or HCI — which is exactly the diagnostic tension.

Common App personal statement

Saturday mornings at the counter · 585 / 650

The espresso machine starts complaining before anyone else does. On Saturday mornings I unlock the café, flip the lights, and listen for the low grind that means the day has officially begun. My parents trust me with the opening shift now — not because I make the best latte art, but because I notice when something is about to go wrong. A clogged portafilter, a milk pitcher left overnight, a delivery slip that never made it onto the whiteboard: small failures that only become visible once a line of people is already waiting.

Most people think customer service is about speed. I learned it is about reading the room. The regular who always orders a drip coffee but stares at the pastry case for a full minute is not deciding between croissants. She is waiting to see whether anyone will ask how her week went. The dad with two kids in soccer jerseys is not impatient; he is calculating whether he can get everyone seated before the game. The teenager who orders the cheapest drink and sits by the window for two hours is not loitering. He is looking for a place where nobody asks him to leave.

I used to rush. I would finish an order and move to the next ticket without looking up. Efficiency felt like competence. Then one afternoon a woman left her drink untouched and walked out. My dad asked what happened. I said I did not know. He pointed at the cup: oat milk, extra hot, no foam — her usual — except I had given her the standard latte. She had not corrected me. She had simply decided it was not worth explaining again. That silence taught me more than any complaint would have.

That stuck with me. People rarely announce what they need. They show it in small frictions: a pause before speaking, a second glance at a menu, a question asked twice, a cup set down a little too hard. Working the counter taught me to slow down enough to catch those signals before they turn into frustration — mine or theirs. It also taught me that a good system is invisible. When the flow is right, nobody thanks you for the cup lids being stocked. They only notice when the system fails.

Closing is quieter. I wipe tables, restock sleeves, and check that the tip jar notes still say thank you in my mom's handwriting. The work is repetitive, but it is also a system with dependencies. When one step breaks — the wrong milk, a forgotten allergen note, a queue that doubles because nobody restocked cups — everything downstream gets harder for someone else. I started writing tiny reminders on painter's tape behind the counter: oat beside almond, allergen flags on the pastry tongs, a second stack of lids before the rush. None of it was dramatic. All of it reduced the number of times a stranger had to ask for help.

I do not write about the café because it sounds impressive. I write about it because it is where I learned to pay attention. The skill is not making coffee. It is noticing what makes a small interaction easier or harder for another person — and adjusting before they have to ask. That habit followed me out of the shop. I still listen for the early complaint in a machine, a classroom, or a conversation: the sound that means something is about to go wrong for someone, if nobody notices in time.

Nothing looks broken on its own.

The problem appears when the pieces are read together.

Whole-application diagnosis

The application contains a stronger story than the student is currently communicating.

The individual parts are strong enough. The major opportunity is making them reinforce one another — so the file communicates the through-line already latent in the experiences.

Goals & narrative

Evidence already exists

Developing

Study Computer Science with an interest in making technology easier and more useful for people.

  • RoboticsTechnical problem solving
  • Coding tutoringMaking difficult ideas understandable
  • Accessibility projectTechnology designed around user needs
  • Family caféObserving what people need in real situations

Latent through-line: using technical skills to solve practical problems for people

How the file currently reads

Strong student + robotics + tutoring + café job + CS interest

Good pieces, listed side by side.

The stronger story already in the file

A technically strong student who repeatedly uses technology and teaching to make complicated things more useful for people.

Same accomplishments — clearer through-line.

Highest-impact opportunity

Connect activities to what the essays communicate.

Not a rewrite-about-coding mandate. A sharper read of the same café story — noticing friction, understanding needs, making systems easier — that already shows up in tutoring, accessibility work, and HCI interest.

Highest-impact opportunity

What most improves how the whole application reads

Strengthen the connection between the student's activities and what the essays communicate.

The café essay does not need to become a robotics essay. Keep the personal story — sharpen what it reveals about noticing friction, understanding needs, and making systems easier. That trait already shows up in tutoring, accessibility work, and HCI interest.

Application priorities

Ordered by leverage, not by severity

Focus first
Academics locked in

Rigorous CS/math record — maintain, don't over-invest.

  1. 1

    Application narrative

    High

    Clarify the recurring idea connecting technical work, teaching, and attention to people's needs. The strongest experiences currently appear more separate than they need to.

  2. 2

    Essay positioning

    High / medium

    Keep the café story. Strengthen the underlying idea — observing problems, understanding users, reducing friction — without bolting an artificial CS paragraph onto the end.

  3. 3

    Extracurricular positioning

    Medium

    Make leadership, scale, initiative, and impact more explicit — especially in robotics, tutoring, and the accessibility project.

  4. 4

    Academics

    Maintain

    Already a strength. Don't spend disproportionate effort chasing a higher SAT while more important application-level work remains.

Priority stack

What to improve first — and what can wait.

Severity is not the same as leverage. Academics are already a strength; chasing a higher SAT while the narrative stays disconnected would miss the point.

Extracurricular positioning example

Before

Taught students Python every week.

After positioning

Designed beginner Python lessons and tutored younger students for 120+ hours; materials adopted by other peer tutors.

Next steps

From diagnosis to a sequence you can run.

Define the through-line, rework essay positioning, strengthen activity descriptions, then check supplements as one system.

  1. Now

    Define the through-line

    Internal positioning principle: “I like using technical skills to make complicated things easier for people.” It does not need to appear verbatim — it organizes the file.

  2. Next

    Rework essay positioning

    Keep the café experience. Make the instinct to notice and solve human problems clearer.

  3. Then

    Strengthen activity descriptions

    Especially robotics, tutoring, and the accessibility app — make contribution and impact more concrete.

  4. Finally

    Review supplements as a system

    Why Major, Why Us, and other supplements should support the same intellectual direction without repeating the Common App essay.

Clearer application

Same accomplishments. Clearer story.

Before
  • Robotics
  • Coding tutoring
  • Accessibility app
  • Family café
  • Computer Science

Good experiences. Weak connection.

After diagnosis
  1. Noticing what people need

  2. Teaching beginners to code

  3. Designing technology around users

  4. Accessibility project

  5. Computer Science + HCI

The accomplishments haven't changed. The application now communicates what they add up to.

Find what your application needs most.

Evaluate the pieces together, surface the gaps, and know what to work on next.