
Ask an engineer how they got good at what they do, and the answer usually involves somebody else. A teammate who challenged them, a mentor who took a chance, or a conversation that changed how they saw a problem.
Early in my career, I was in a final interview with a CEO for a role leading something I'd never done before. He asked me one question: "Tell me about something you're interested in. It doesn't have to be about work."
I spent the next 30 minutes talking about wave structures and even- and odd-order harmonics.
His response? "You're hired."
Then came my first assignment: "I want you to automate yourself out of a job in six months."
Naturally, I asked, "Then why would I join?"
He said, "If you can do that, there's no limit to what else you can do."
That stuck with me. Engineers should be curious. We should want to understand how things work, why they work, and what could be better. Figure out the problem in front of you, solve what you can, then go figure out the next thing. And the next one.
But we don't have to do it alone.
1. Show Up
Go to the meetup. Attend the conference. Sit in on the demo. And don't just show up physically; participate.
Ask the question you think everyone else already knows the answer to. Somebody else is probably wondering the same thing. Talk to the engineer whose approach makes absolutely no sense to you yet. That's an opportunity.
You don't have to be an expert to contribute, and being an expert doesn't mean you're done learning. The goal isn't to collect business cards or prove you're the smartest person in the room. It's to leave knowing something you didn't know before and hopefully help somebody else do the same.
2. Listen to What Others Have Built
I love when somebody shows me something cool they've built, especially if it's different from how I would have approached it.
My first reaction isn't to explain how I'd do it. It's "That's cool. How did you do that?" Then I want to know why. What were you trying to accomplish? What constraints were you dealing with? What surprised you?
Now we get to the fun part: where do our ideas mesh, where are they different, and which approach actually gets us the outcome we're after? Maybe it's theirs. Maybe it's mine. Maybe it's something neither of us had considered before that conversation.
We shouldn't be trying to win an argument about architecture. We should be trying to get it right. And sometimes the most useful voice in that conversation isn't another engineer at all.
3. Share What You're Seeing, Even When it's Messy
I think a lot of engineers are afraid to share because they feel inadequate. Somebody has probably built a better version. Somebody might find a flaw. Somebody might ask a question they can't answer.
So what?
If somebody has a better approach, I want to hear it. That's how we learn. Share the half-finished project, the unexpected failure, the idea you're still working through. You don't need a perfect demo or a polished conclusion to start a useful conversation.
And please listen to the people you're building for. Some of the best ideas come from the people who actually live with the problem every day. They may not know what technology should solve it, but they can tell you what hurts, what matters, and whether your solution is making anything easier.
Sometimes the most valuable thing we discover together is that we were solving the wrong problem.
4. What Leaders Can Do
If you want people to share ideas and challenge assumptions, start by showing them you can be wrong.
I have no problem saying, "My bad." I've made decisions that looked great on paper and didn't work. We all have. Own it, communicate it, and learn from it.
When somebody catches something I've missed, I want them to hear: "I didn't think of that. Thank you." Then we can ask, "How do we prevent it next time? What else can we do?"
And when someone on my team builds something awesome, I want everybody to know. Tell me how you did it. What else are you working on? Seriously, this is cool stuff.
People shouldn't have to guess whether it's safe to speak up. Leaders can make that obvious by admitting mistakes, welcoming better ideas, giving credit, and making time for people to learn and share.
If somebody on your team builds something better than you would have, that's not a threat. Celebrate it.
Keep Learning. Keep Helping.
None of us got here alone. Somebody gave us an opportunity, answered a question, shared a failure, or helped us see a possibility we hadn't noticed.
Fred Rogers often shared advice from his mother: "Look for the helpers." There are always people helping. And when you can, be one of them.
Share what you know. Listen to what you don't. Get excited when somebody shows you a better way. The fun of technology isn't just building things. It's getting better, together, and making people's lives easier along the way.
There's always another problem to figure out.
So, show up. Share what you're learning. And keep freaking learning.
About the author
Brian Cerchio is Vice President of Engineering and Professional Services at Encore Talent Solutions, where he leads engineering, technology strategy, and custom software initiatives. Throughout his career, he has led multidisciplinary teams of engineers, product owners, UX designers, and implementation specialists, delivering solutions for organizations ranging from small businesses to Fortune 100 companies. He enjoys mentoring others, exploring new ideas, and building things that make people's lives easier.