Brian’s Notes If you’re an engineer

An open laptop on a table with five different coffee cups gathered around it like a team

It’s not just the code.

Attitude, drive and teamwork get people hired.

Years ago, an engineer named Jack worked alongside me. He had serious coding skills, but that isn’t what you noticed first. You noticed his attitude.

Jack was always the one offering to help, and never the one saying “that’s not my department” or “that’s probably not possible.” Some days I wanted to hand him something ridiculous, like curing the common cold, just because I knew he’d go at it with everything he had. His code was excellent. Honestly, it was an afterthought when I thought about what he brought to the team.

That’s the point of this note. There’s more to getting hired than your technical skills.

What do hiring managers notice first?

Your attitude. It arrives before your code does.

Before anyone digs into your work or reads past the top of your résumé, they’re quietly asking a few questions. Is this person glad to be here? Would I enjoy managing them? Would they fit with the team? Your attitude answers those in the first few minutes, whether you mean it to or not.

What’s drive, and how do they see it?

Drive is the engine under the attitude. Do you do what you’re asked and stop there? Or do you take responsibility for your work, and for your team’s?

It shows most in how you tell the hard stories. If you left a job because of a rough manager or a plan that didn’t work out, own your part. Others played a role, sure. But a hiring manager wants to hear what you did to make it better, and what happened. Those answers predict what you’ll do for them.

I’ve seen strong engineers passed over because every story ended with somebody else’s fault. Startups notice this most. They were usually founded by people with enough drive to run a small country, and they’re looking for more of it.

Why does teamwork matter so much?

Because the code is the easy part now. With agents writing a first draft of almost anything, what a team actually does together is decide what’s worth building, agree on how it should work, review what the tools produced, and own it when it breaks at two in the morning. You’ll do that with product people, designers, support, and the engineer who inherits your work next year.

Do you make those conversations better? Do you raise the level of the team, or drag it down? Nobody can see that in a repo, and no model can produce it for you. They hear it in how you talk about the people you’ve worked with.

Can I fix these?

A gap in experience is expected, understandable and usually fixable: you go build the thing you haven’t built yet. Attitude, drive and teamwork are harder to fake in an interview, and harder to fix in an afternoon.

The good news is that they’re mostly choices. You can choose to offer help, own your part and make the people around you better, starting Monday.

The short version

  • Your attitude arrives before your code.
  • Drive shows in how you tell the hard stories. Own your part.
  • The code is the easy part now. Show how you work with people.
  • Skill gaps are fixable. These are mostly choices.

Be the Jack on your team. When they get to your code, it’ll just be more good news.

Sound like you?

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.