t-shaped engineer

Burn After Reading

My manager ruined a perfectly good beer at an open air brewery in Richmond by telling me the truth about my career. The advice aged better than the beer. Here’s the T-shaped engineer pitch nobody gave you, and six prompts worth burning tokens on at the end.

The T-shaped engineer idea was first called out for me at an office happy hour, over beers at an open air brewery called Hardywood in Richmond. Careers came up, the way they do when engineers drink near their manager, and mine made a point I couldn’t shake: depth alone doesn’t carry you. The engineers who go furthest are deep in one thing, conversant in everything around it, and able to explain their work to anyone in the building.

I nodded, went home, and kept doing exactly what I was doing. Going deeper and calling it growth. It took me embarrassingly long to admit he was right.

The machine took the easy half

For years the deal was simple. Be great at the craft and the craft carries you.

That deal is being renegotiated by a machine that writes code faster than you, never sleeps, and costs less than your coffee habit. The vertical part of your skill set, the part we spent a decade sharpening, is now shared with anything that has an API key.

Here’s what the machine can’t do. It can’t notice the VP checked out two slides ago. It can’t tell a product manager no in a way that makes them feel heard. It can’t repair a relationship after a tense meeting or read the silence after a bad demo.

That’s the half you were told was optional. It’s now the half that’s left.

The T, minus the LinkedIn version

The vertical bar is one area where you are genuinely deep. Not “familiar with.” Deep. You’re the person people ping when that thing is on fire.

The horizontal bar is working knowledge of everything around it. Product. Design. Data. Infra. Security. The business itself. Enough to be dangerous in any meeting.

Soft skills aren’t a third thing bolted on. They’re what the whole letter is made of. Communication is what lets your depth travel outside your own head. Depth that can’t travel is a diary.

“My code speaks for itself”

Say “I’m bad with databases” in an interview and you’d fix it by Friday. Say “I’m bad with people” and somehow it’s a personality.

Your code has never spoken for itself. Code doesn’t attend calibration meetings. Your promotion case is written in English and decided by tired people reading it on their phones.

The engineer who quietly fixes the outage at 2am gets a thank you emoji. The one who fixes it and writes a postmortem people understand gets a reputation. Same fix. Different career.

Nobody gets promoted for elegant recursion. People get promoted because someone in a room they weren’t in could explain their impact. Your job is to arm that person.

How to build the T

  1. Pick your vertical and commit. You can’t be T-shaped without the stem. Take your strongest area and go embarrassingly deep. Depth earns you the right to be heard on everything else.
  2. Steal the horizontal from meetings you don’t need to attend. Sit in the product review. Ask the finance partner what moves their number. Ask the dumb question. Half the room was too proud to.
  3. Write like your reader is busy. Answer first, context second. If your status update needs a scroll, it needs an edit.
  4. Explain your work at three altitudes. To an intern, to a peer, and to a VP with thirty seconds. If you can only do one, you’re deep. Not T-shaped.
  5. Handle feedback like a production incident. Acknowledge fast, skip the defensiveness, fix the root cause. Arguing with the alert doesn’t clear it.
  6. Do the human maintenance. Follow up. Give credit by name. Disagree in private, defend people in public. It compounds slower than code, which is why impatient people skip it and plateau at senior.

Now, about the title

Burn After Reading is an instruction.

The same AI that commoditized your vertical bar is the cheapest soft-skills coach ever built. No ego, no calendar, and it’ll run the awkward rep a hundred times for pennies. You’ve read. Go burn some tokens:

  1. Paste your last design doc: “Rewrite the summary so a VP with thirty seconds gets why this matters. Then tell me what I buried.”
  2. “Interview me about Document OCR like a curious product manager. Interrupt me every time I use jargon.”
  3. “Play a director who wants to cut my project. Push back hard. Afterward, grade how I defended it.”
  4. Paste the spicy Slack message before sending: “Tell me how this reads to someone having a terrible day. Then fix it without losing the point.”
  5. “Ask me five questions a security engineer, a designer, and a finance partner would each ask about my current project. Score my answers.”
  6. Paste your self-review draft: “Find every sentence describing activity instead of impact. Rewrite one so I see the difference.”

An hour of your life, a few cents of compute. Cheaper than the beer that started this.

The point from that brewery still holds. Depth gets you into the room. The crossbar keeps you there.

Burn accordingly.