Brian’s Notes If you’re hiring

A corkboard with a job post cluttered with stars, sparkles and a rocket next to a plain, clean job post held up by a red gem push pin

Rock$tar$ only?

How to write a job post senior engineers actually read.

Years ago I wrote a fake job ad for our old blog. It has aged a little too well. Here it is, updated for today:

The Best Company Ever is now hiring! This is a once-in-a-lifetime opportunity.

About us: Our founders hail from Harvard, Mars, MIT and Atlantis, and helped invent Google, America and the wheel. Other startups let you in on the ground floor. We’re offering the basement. The only way from here is up!

Required: 10+ years with a framework that launched last spring. 5+ years building with AI agents. 4 years living on a raft in the Pacific. 2 years achieving world peace. It is absolutely imperative that you use good grammar and write good.

Nice to have: You own a yacht. Your favorite color is cement gray. You can eat fire. You enjoy 70-hour weeks.

Compensation: Why make millions when you can make... EQUITY! Plus a $25 gift card.

To apply: Email your résumé, your Social Security number and your mother’s maiden name.

Made you look.

Every line in that ad is an exaggeration of something real, and I still see versions of all of them. Here’s what I’d tell anyone writing a job post for a senior engineer.

What should a good job post say?

  • What the person does on day one. Not every technology you’ve ever touched. What will they actually work on in their first month? What’s broken? What’s keeping you up at night?
  • Who you are. How long you’ve been around, what you’ve built, who’s on the team and where you’re headed. Real numbers, honestly stated, beat big adjectives. Skip “the next big thing.”
  • The pay, honestly. Post the range, and make sure the role really sits inside it. “We can’t actually pay the top of that” is a hard way to begin.
  • What matters to engineers. How decisions get made. How the team works together. Remote, on site or both. What gear they’ll get.

What should it leave out?

  • Requirements that don’t matter. Every “must have” scares off someone good. Ask what’s truly needed on day one, and what a strong engineer would pick up in a month.
  • Years of anything. Asking for ten years with a framework that’s eight years old tells every engineer who reads it that nobody on the team looked at the post. The 2010 version of my ad asked for “10+ years of Rails.” Rails is old enough now that someone might actually have that, so the joke had to move.
  • ”Rock star,” “ninja” and friends. To a lot of engineers, those words read as “we’ll overwork you and call it culture.”

Who should write it?

The person the new hire will work for, with help from the engineers already on the team. Ask them why they said yes. Whatever drew them in will draw in people like them. If someone outside the team writes the first draft, have the team read it before it goes out.

What can a good job post do?

Something quietly wonderful: the wrong people skip it, and the right people lean in. Your pile gets smaller and better.

But even a great post mostly reaches people who are looking, and the senior engineers you most want usually aren’t. They’re happy where they are, and they answer when someone they trust sends a text. That part, I can help with.

Hiring a senior engineer? Tell me about the seat.

Talk to Brian

Tell me what you need. I’ll think of someone.

Skip the formal job description. The more honest you are about the seat, the stack and the room, the faster a warm intro shows up. If I can help, great. If not, I’ll point you in the right direction.

Brian MarianiI read these myself. Jonathan Soo Hoo, my partner at Mirror, does the first outreach on some searches; if you hear from him, that’s why.

When do you need someone in the chair?

No sequence, no platform. A person reads this. Questions first? Read the FAQ.