There’s a version of executive leadership that works fine in most industries but falls apart the moment you’re in a room full of engineers. It relies on authority, on title, on the assumption that the person at the top of the org chart is also the most qualified person to make decisions. In technical environments, that assumption gets tested fast — and leaders who can’t pass the test lose credibility quickly, sometimes permanently.
Sam Miri started his career as a computer engineer. He earned his degree in Computer Engineering and Mathematics from Santa Clara University and spent his early years working in the startup ecosystem, getting close to the product, understanding how things were actually built. That foundation has shaped how he approaches leadership in every technical role he’s held since — at InvenSense, Xicato, Bally’s Interactive, Mimik Technology, and now Atmosic Technologies.
The distinction he’s come back to throughout that career: there’s a real difference between managing a technical team and actually leading one.
What Managing Looks Like in a Technical Environment
Managing, at its core, is about process and output. It’s about ensuring deliverables land on time, resources are allocated correctly, and the right information reaches the right people. These things matter. Without them, even the best technical team loses direction.
But management in a technical environment can become a ceiling if that’s all it is. Engineers and product teams are exceptionally good at identifying when an executive is operating purely at the process level — coordinating without truly understanding, making decisions based on summaries rather than substance. They’ll comply. They’ll hit their deadlines. But they won’t bring their best thinking to the table, because they’ve concluded it won’t be understood or valued.
That’s the gap between a team that executes and a team that innovates. And it’s a leadership problem, not a talent problem.
What Leading Actually Looks Like
Leading a technical team requires something different: enough genuine understanding of the work to ask the right questions, challenge assumptions credibly, and recognize the difference between a real obstacle and an engineering instinct toward perfectionism that’s slowing things down.
It doesn’t require knowing more than the engineers. In fact, one of the most useful things an executive with a technical background can do is get comfortable saying “walk me through that” or “help me understand why this is the constraint” — and actually mean it. Not as a power move. Not as a test. As a real attempt to understand something that will inform a better decision.
That posture — curious, direct, willing to engage with the technical detail without pretending to own it — is what earns credibility in product and engineering environments. It signals that the leader respects the craft, understands its complexity, and isn’t going to make decisions that ignore it.
When Knowing Less Is Actually an Advantage
Here’s something that takes most technically trained executives a while to accept: there are moments when knowing less about the product than the people you’re leading is genuinely useful.
When you’re not the deepest expert in the room, you’re free to ask the questions that experts stop asking because they’ve already answered them in their own heads. You can challenge a technical assumption not because you know it’s wrong, but because you need it explained in terms that connect to the customer, the market, or the business case. That outside pressure — the leader asking “why does this matter to the buyer?” or “what’s the simplest version of this that actually solves the problem?” — is often exactly what a deeply technical team needs to stay connected to the real world.
Sam Miri has been in rooms where he was the least technical person present and rooms where he was the most. The dynamic that produces the best outcomes is neither. It’s a leader who understands enough to engage meaningfully, asks questions that push the team to think beyond the product itself, and creates an environment where the technical experts feel genuinely heard — not managed around.
The Credibility You Can’t Fake
In technical environments, credibility isn’t granted by title. It’s earned through demonstrated understanding — of the product, of the market, of the real constraints the team is working within. Executives who lack that understanding and don’t make the effort to develop it eventually find themselves isolated from the teams they’re supposed to be leading, getting polished summaries instead of honest assessments and making decisions with less information than they think they have.
The engineers aren’t withholding. They’ve just concluded it isn’t worth the effort to explain.
Building that credibility takes time and genuine curiosity. But once you have it, it changes everything about how a technical team operates — because the people doing the hardest work believe the person leading them actually understands what they’re doing and why it matters. That belief is the difference between a team that manages its way through a product cycle and one that drives something genuinely new into the world.
About Sam Miri
Sam Miri is Vice President of Marketing & Business Development at Atmosic Technologies, where he leads global marketing and BD strategy for a company dedicated to ultra-low-power wireless chip design. With more than 20 years of experience leading sales, business development, and product management across hardware, software, and connected device markets, Miri has held executive roles at InvenSense (TDK), Xicato, Bally’s Interactive, and Mimik Technology. He writes about AI, IoT, emerging technology, and executive leadership at SamMiri.com.
Leave a Reply