“We're Building This Together” - How Behnam Shapes Product and People Through Ownership and Openness
Behnam started coding when he was just 16. More than 20 years later – after earning a Master’s degree in Software Engineering and building his career across borders, he still lights up when he talks about starting something from scratch.
In 2025, he joined Conference Manager to lead the development of a brand-new event app – a greenfield project meant to replace the current app with something more powerful, scalable, and intuitive. For Behnam, the attraction was clear:
“I like creating. When you build something from the beginning, you’re part of every layer – from laying the foundation to seeing how users respond when it’s released. That’s impact. That’s ownership.”
Creating Isn't Just About Code - It's About Mindset
As team lead, Behnam doesn’t just guide the technical side of development. He also sets the tone for how the team works together. And his leadership style is anything but top-down.
“I’m not anybody’s boss. We’re building this together. If we succeed, it’s a team win. If we fail, we learn together.”
He sees his role as equal parts coder, mentor, and collaborator – someone who helps the team define goals, break down tasks, and stay on track, but who’s always in the trenches himself. This collaborative approach reflects one of Behnam’s core beliefs: that great software – and great teams – are built on trust, curiosity, and shared ownership.
When he’s not working, Behnam enjoys restoring and riding motorcycles – a passion that also speaks to his love of engineering, precision, and creative problem-solving. “It’s all connected,” he says. “Building something with your own hands – whether it’s a product or a bike – gives you a different kind of satisfaction.”
“The only thing I ask from the team is that they’re proud of what they do. That they enjoy it and take responsibility for it. Because when people care, the product becomes better.”
Flat Hierarchies, Open Minds
Behnam actively challenges traditional ideas about seniority and authority in tech. He doesn’t believe in dividing people by titles or years of experience.
“I’ve seen people with two months of experience do better than I did. Being senior doesn’t mean you know everything. What matters is how you think, how you learn, and how you contribute.”
This is why one of Behnam’s top criteria is mindset. He looks for people who are open, curious, and constantly looking to improve – not those who think they already have all the answers.
“When I’m hiring, I want people who’ve ‘read more than one book’. People who ask why. People who’ve looked beyond their own perspective. Because that’s how you grow. That’s how teams grow.”
He also believes that learning is a shared process – and that every team member brings something valuable to the table.
“Nobody knows everything. But everybody knows something. So, we have to learn from each other. That’s how we build collective knowledge and that’s what makes a great team.”
“I Encourage Failing. That's How We Learn.”
In Behnam’s world, failure isn’t something to avoid – it’s something to embrace. Trying, failing, learning, iterating: that’s how both code and people evolve.
“I encourage failing. That’s how we learn. None of us learned to walk without falling first. When you try something new, you’re going to fall – and that’s not just okay, it’s necessary.”
He believes this approach fosters ownership. When people feel safe to experiment, they’re more likely to take initiative – and more likely to care deeply about the outcome.
“If you never fail, you’re probably not trying hard enough. We should be proud of the effort. Proud of taking risks. That’s what drives innovation.”
Influence from Day One
Behnam encourages every developer to speak up, challenge ideas, and bring their own perspective to the table.
“I hope all team members have their own opinion – and that they’re not afraid to share it. As long as you can support your idea with arguments, I want to hear it.”
This attitude has a direct influence on how the app is built – in terms of user experience, scalability, and product direction. Every decision is a shared one. Every success is collective.
“You can’t build good software in isolation. We make better decisions when we build it together.”
