Dev, thanks for trusting us with your draft. Before the scores: the rule you made for your Saturday sessions - nobody watches, you hold the hex key - is the single best line in this essay. It tells a reader who you are faster than any achievement list could. Everything below is small, specific polish on an essay that is already working.
At 23, nothing here is structurally wrong. The remaining work is refinement: one ending to earn, one opening line to show instead of tell, and one paragraph to tighten. And as always, this score only measures the draft, not you and not your story. Drafts are fixable; that is the whole point of an audit.
What’s already working
Your six scores
-
Does it sound like you?
Does the essay sound like a real 17-year-old?
Natural and funny throughout. One stiff patch where “the job changed” does a lot of lifting for you.
4 / 5 -
Did you show, or just tell?
Is every claim based on concrete scenes and details?
Cheerios, the BIG BRACKET, the hex key - all real. “Machines have moods” is the one claim you tell instead of show.
4 / 5 -
Does it hold together?
Does one clear idea carry the whole essay?
Fixing machines to teaching fixing is a clean spine. The “project problems” paragraph sits slightly beside it.
4 / 5 -
Did you actually do something?
Does it show initiative and impact, or just showing up?
Saturday sessions, six kids trained - real impact. The scale is one club, which reads as honest, not padded.
4 / 5 -
Could anyone else have written this?
Will the reader remember it two days later?
The hex-key rule is memorable. The makerspace setting is familiar, but your angle on it is fresh.
4 / 5 -
Did you earn the ending?
Does the reflection grow out of the story?
“The whole point of building anything” is a moral the story did not quite earn. The ending tells where the essay should show.
3 / 5
The big picture
This is a top-of-the-pile essay. A reader finishes it knowing exactly who you are: the kid who hands over the hex key. Nothing here needs rethinking. The remaining fixes are small, and each one is about trusting the scenes you have already written to do the talking.
Your 3 polish fixes, in order
- Earn the ending. Cut the moral. “The whole point of building anything” is bigger than the story - it is the one place the essay preaches. Try ending inside the scene instead: the left Prusa running its warm-up while six kids work the farm without you. Let the reader draw the conclusion you are currently handing them.
- Show the moods; don’t announce them. “Machines have moods” tells the reader what the Cheerios paragraph could show. Open with one cranky-morning scene - the left Prusa failing its warm-up while a freshman waits - and the reader feels the moods without being told about them.
- Tie the “project problems” paragraph to the spine. Right now it reads as a separate insight (design vs. machine). One sentence linking it forward - something like “that is when I started handing over the hex key” - folds it into the teaching arc instead of leaving it beside it.
What happens next
Our honest take: this essay does not need a full edit. The three fixes above are within your reach - you can handle them with what this audit gave you.
If you would rather we handle the polish, that is exactly what the Personal Statement Edit ($149) is for - a two-pass edit built directly on this audit, where we do the fixing together.
Book the Personal Statement EditYour $79 audit fee applies in full - you pay only $70 - when you book within 30 days.
One more thing worth knowing: this audit scored one essay. If you are wondering how the whole application holds together - essays, activities, all of it as one story - that is what our Application Package review ($349) is for.
Book the Application Package ReviewYour $79 audit fee applies in full - you pay only $270 - when you book within 30 days.
You got this, Dev! We are cheering for you and want to help you get this done!
– ClearThread Studios team
Sample for illustration only.