Tech Tests Give Me Anxiety
3 min read

Ping:
Hey, you made it! So glad you're here.
Intro
I think Iâve earned an honorary degree in anxiety.
Iâve done over 100 tech tests. Probably more if you count the practice ones.
And every single time? I want to throw up.
It doesnât matter how long Iâve been coding. The second I open the brief, I feel like Iâve forgotten how to write a for loop.
Tech tests donât just ask for code - they ask you to perform, decode vagueness, and stay calm while spiralling internally.
But over time, I stopped trying to do them the "normal" way.
Instead, I built rituals that actually work with my brain.
This week, I want to introduce you to two parts of that process: Echo and Ping.
Theyâre quiet, but powerful.
And theyâve helped me turn test-day dread into something survivable - and sometimes, even fun.
Scene: How I Actually Survive This
â ïž Scene: Test Day, Brain in Danger
Hereâs how I survive tech tests now:
- I block off time â no distractions.
- I set mini sprints.
- I let myself dive into it like itâs a puzzle game.
- I let my creative brain find weird solutions.
- And I donât fight my hyperfocus when it shows up fashionably late.
And then without fail - I second-guess everything.
"Should I have added more tests?"
"Did I miss an edge case?"
"The prompt said to only build X - but what if they secretly wanted Y?"
That perfectionist spiral?
Loud.
So I built a team in my head to help.
Their names? Echo and Ping.
đ§ Echo: The Pattern Whisperer
Echo doesnât panic.
They watch. They notice.
They remind me:
"Youâve done something like this before."
"This smells like that onboarding test from last year."
"This vague prompt? Yeah, we know what they really want."
Echo is a walking internal pattern matcher.
They whisper clarity when everything feels scrambled.
Sometimes, that whisper is what keeps me moving.
đŸïž Ping: The Ritual Master
Ping doesnât deal in chaos.
Ping deals in checklists and breathing room.
When my brainâs yelling "Itâs too much," Ping calmly says:
"Letâs break it down."
- Step 1: Clone the repo
- Step 2: Start a 25-minute timer
- Step 3: Write 3 tiny TODOs
- Step 4: Breathe
- Step 5: Ignore perfection until the last 10%
Ping helps me start - and also stop.
Without Ping? Iâd rewrite the whole backend because I "just had a better idea at hour 5."
⥠Zap & đ§ Buffer: The Cameos
Zap shows up too, of course.
Tossing out flashy extras like custom loading animations or easter egg messages in the README.
Half get cut.
The other half? Theyâre usually the thing people remember.
Buffer is nearby too.
Softly reminding me:
"Youâre not lazy â youâre overloaded."
"Youâre not failing â youâre masking."
"You are allowed to pause."
Sometimes thatâs the only permission I need.
đ€ The Part I Donât Talk About Enough
Even when it goes well - even when I know I crushed it,
I still second-guess everything.
"Should I have added that extra endpoint?"
"Was my folder structure 'industry standard' enough?"
"What if they expected more, but said less on purpose?"
That voice hasnât gone away.
But Iâve learned itâs not the truth - itâs just the static.
And these days, I let my full brain work:
- Echoâs clarity
- Pingâs rituals
- Zapâs spark
- Bufferâs softness
Thatâs not overthinking.
Thatâs a neurodivergent dev in motion.
â Pingâs Checklist â For You
If tech tests hit you like a freight train, try this:
- Start with a tiny win (clone the repo)
- Block off a protected time box (no Slack, no doomscrolling)
- Use a template or ritual if youâve got one
- Trust your Echo (youâve done this before)
- Let Zap add one moment of âšyouâš
- Schedule a soft landing - decompression time, a snack, something nice
You are allowed to approach this differently.
Your brain is not the problem.
Structure is the support beam.
Closing Thoughts
We donât get to choose the system.
But we do get to choose how we show up in it.
Whether itâs your first tech test or your fiftieth, remember this:
- Youâre allowed to need structure.
- Youâre allowed to spiral.
- Youâre allowed to not over-deliver.
The win isnât perfection.
The win is starting, surviving, and shipping something real.
Until Next Time
This issue wasnât easy to write.
Because even now - even after all the work Iâve done -
tech tests still light up my nervous system like a threat.
But I also know this:
My brain works.
Not like everyone elseâs.
But enough to ship, lead, teach, and build.
And if youâre here reading this? Yours does too.
Let Echo guide.
Let Ping structure.
Let Zap sparkle.
Let Buffer hold you steady.
And donât forget to breathe.
// Simen
đThe Snacks
đ§ Echoâs Prompt Recall Trick Before you start, open 3 old commits that you're proud of. Let your brain remember - you already know how to do this.
đ§ Pingâs Ritual Picks â±ïž CodeInterview.io â Clean, simple timer + collaborative editor. Perfect for timeboxing. đ” PokĂ©mon Lo-fi Mix â Calm, no-lyrics background to stay focused.
⥠Zapâs Bonus Tip Rename your project folder to something chaotic: panic-but-make-it-fancy , buffer-approved , or echo-echo-echo . Turns stress into play. Dopamine unlocked.
đż From Buffer, With Love You are not broken. You are overloaded, not lazy. You are adapting, not failing. You are allowed to pause.