Brian’s Notes If you’re an engineer

A résumé with a folded corner, a coffee ring and one crossed-out line, still looking fine, with a pencil beside it and an empty office chair waiting

You don’t need a perfect résumé.

Five myths that keep good engineers from moving.

You read the posting twice. Seven years in the exact framework. A computer science degree. “A strong presence in the community.” You close the tab and decide it isn’t for you.

Over the years, I’ve watched a lot of good engineers rule themselves out before anyone else had the chance. It usually comes down to one of five myths.

Do I need years in the exact stack?

It’s nice if you have them. It’s rarely the whole story.

What a hiring manager really wants to know is whether you can do the work. Something real you can point to often says more than a line on a résumé: a side project, an open-source fix, a tool you built because your team needed it. Plenty of teams would rather hire a strong engineer who’ll pick up their stack quickly than a so-so one who already knows it.

Can I really switch stacks?

Yes. Even back in my Rails-only days, companies were happy to meet “raw athletes”: engineers with deep fundamentals who’d learn the framework on the job. If you’ve spent ten years in Java and you’re curious about something else, that isn’t a gap. It’s range.

Languages and frameworks come and go. Good engineering travels. It’s a big part of why I look for full-stack athletes.

Do I need a following?

No. It’s lovely when people know your name, and I enjoy working with engineers who are well known. But most excellent engineers aren’t famous, and most hiring managers don’t care how many followers you have.

A thoughtful profile and a few things worth reading can help. In the end, though, the seat goes to talent and fit, not to an audience.

Do I need a computer science degree?

It helps. It’s rarely required. I’ve placed engineers without one, and many teams care far more about what you’ve built than where you studied.

Some companies do insist on a degree, and that’s their call. Just let them make it. Don’t rule yourself out of a seat that never asked.

Will a startup cost me my salary?

Not necessarily. Plenty of young companies are well funded, or already profitable, and pay a competitive salary alongside the equity. Others really are a trade: less cash now for a bigger stake later.

It’s fair to ask which kind you’re talking to. Ask about runway and revenue out loud, and if equity is part of the offer, learn what it’s actually worth. I wrote about that in Equity, in plain words.

So what do I actually need?

Usually less than you think. Something real to show. A clear idea of what you want next. And someone who knows you and can make the introduction.

Most of the time, what stands between a good engineer and a great seat isn’t a missing credential. It’s a missing conversation.

The short version

  • Real work you can show beats years on a line.
  • Switching stacks is range, not a gap.
  • A following is nice. Talent and fit decide.
  • A degree helps. It’s rarely required.
  • Many startups pay well. Ask about runway, and know what the equity is worth.

Don’t be the first person to tell yourself no. Let the people hiring decide. You’ll be surprised how often they say yes.

Talked yourself out of a move lately?

Talk to Brian

Say hello. Or just tell me where you’re headed.

You don’t have to be looking. Most of the people I’ve placed weren’t. Tell me what you’re working on and what would make you pick up, and I’ll keep you in mind for the right thing, not the next thing.

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.

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