01 / The Interview
I don’t do LeetCode anymore.
My technical interview is now one sentence long:
“Look out the window and tell me what you see.”
If they’re quiet like a dodo, I shake their hand goodbye.
It sounds like a joke. It isn’t. It’s the only interview question that still works in 2026.
02 / The Old Interview Is Dead
The old interview tested if you could memorise the answer. Invert a binary tree. Reverse a linked list. Explain Big O like you were in an exam.
That game is over. The agent can do all of that in 0.4 seconds, better than you, better than me, better than anyone in the room.
So what is left for the human to do?
To see.
Agents are blind, deaf, and literal. They don’t know what you mean. They only know what you say. If you can’t describe the world to a human sitting next to you, you will cost my company too many tokens explaining the agent what the job is.
03 / “A Tree”
That’s what most candidates say.
“A tree.”
And we’re done. Thank you, nice to meet you, good luck elsewhere.
Because “a tree” tells me everything about how you will write a ticket, write a prompt, write a spec.
“A tree” becomes:
Fix the bug.
Which becomes 5,000 tokens of the agent asking: What bug? Where? On what device? When does it happen? What did you expect? What did you try?
Every vague sentence you write is a tax my company pays in tokens.
04 / What I Actually Want To Hear
I want to hear this:
Cumulus building in the west, light dropping fast. Branches are moving south to north, so the wind is picking up. There’s a dead branch over the path — that’ll come down in the next storm. If we were deploying today, I’d wait two hours for the rain to pass.
That’s not poetry. That’s engineering.
That person just did four jobs at once: observed, prioritised, predicted, and communicated in a way that another mind — human or agent — can act on without asking a follow-up question.
That person will write this ticket:
Checkout button on mobile Safari overlaps the footer when the keyboard is open. iPhone 15, iOS 18.2, steps to reproduce: 1, 2, 3. Screenshot attached. Expected: button stays above keyboard. This blocks payment.
200 tokens. Done. No clarifying questions. No meeting.
05 / My Rubric
I score the Window Test like this:
0 — DODO: “A tree.” Quiet. Vague. Extinct.
1 — REPORTER: “There’s a tree with green leaves and a cloudy sky.” Accurate, but flat. No use.
2 — OBSERVER: “Cumulus building west, light dropping, branches moving south to north, wind picking up.” You see change. You see direction.
3 — SYSTEMS THINKER: “That dead branch will fall in the next storm. Clouds mean rain in two hours, so if we deploy now…” You see consequences. You see time.
4 — AGENT WHISPERER: You describe it so clearly a blind agent could draw it, file the ticket, and estimate the work without asking you anything back. That’s the hire.
Most engineers are 0s and 1s. They were trained to be quiet. To give the minimal answer. To not waste words.
In the age of agents, minimal is expensive. Precision is cheap.
06 / Why This Matters More Than Code
Code is now the cheap part. The expensive part is telling the machine what to build.
Your job is no longer to be the smartest person in the room. Your job is to be the clearest eyes in the room. To be the person who can walk into a messy, real-world situation — a bug, a customer complaint, a broken process, a cloudy sky — and turn it into language so precise that someone else, or something else, can act on it.
If you can’t tell me about the clouds and the branches outside, you’re gonna cost my company too many tokens explaining the agent what the job is.
BE LOUD. DODOS WERE QUIET.
Steal this interview if you’re hiring. Your future self, paying the token bill, will thank you.
To answer: send a letter, not a brief, to hello@notanothertechgenius.com. Subject line must contain the name of the bird that never sings.