Driven by impact, not titles
Two candidates, one impressive title, and why I hire the person who can tell me what got better because of their work.
I once interviewed two engineers on the same day.
The first had a title that barely fit on a business card. He talked for twenty minutes about the size of his last team, the tools on his resume, and the architecture he had "owned". When I asked what had changed for the people using his software, he paused. "That was more of a product question."
The second had a much smaller title. When I asked about his favorite project, his eyes lit up. A tiny internal tool that cut a two-hour weekly report down to five minutes. He knew exactly who used it, what they did with the time they got back, and what he would build differently next time.
I hired the second one. It wasn't close.
Titles describe a chair
A title tells you where someone sat. It doesn't tell you what they did there.
Job ads still ask for rockstars, ninjas, and 10x engineers. I've never needed any of those. What I need are people who care: about the work, about the team, and about what our work changes for real people.
That kind of care is easy to spot once you look for it. It shows up in how people talk about their work. Not "I was responsible for", but "this is what got better".
What impact looks like day to day
On the teams I enjoy most, a few things are always true:
- We prototype in days, not quarters. Speed beats a perfect plan.
- We stop fast when something isn't working. No ego, no attachment to our own ideas.
- We bring strong opinions and leave the ego outside. Good debate makes better decisions.
- The best idea wins, not the loudest voice. And not the biggest title in the room.
- We share our numbers. All of them. The wins, the misses, and what we learned.
- When we ship, we own the outcome. Success and failure belong to the whole team.
None of these depend on what's written under your name.
Chase the change, not the label
Titles aren't bad. They help people understand how a team is organized. But they make a poor goal. If you chase a title, you can get it and still not have helped anyone.
If you chase impact, the titles tend to follow. And even when they don't, you'll have something better to talk about in your next interview than the size of your last team.
So the next time someone asks what you do, try answering with what changed because of your work.
That's the story worth telling.
Keep reading
More from the notebook.
Nobody deletes an app because of its framework
A friend asked whether to build native or use Flutter. Why AI may bring big companies back to native apps, and why a new product should still ship first.
Phishing in minutes, not weeks
A fake bank text that almost got me, a deepfake video call that cost a company millions, and why the answer to AI-powered scams is to get sharper, not to stop AI.