Chief Software Architect

We are IceWarp. For 25+ years, we've been building a communication and collaboration platform that tens of millions of people open every morning. We've been cheerfully poking Google and Microsoft in the ribs the whole time, and honestly? It's been fun.

Now, the global collaboration market is experiencing massive growth, and we are accelerating to capture a much larger piece of it. To do that, our foundational technology needs a leader.

The Challenge & The Opportunity:

Let’s be radically honest: 25 years of a successful product means 25 years of accumulated engineering decisions. We carry heavy technical debt. We aren't hiding from it; we are looking for the person who sees it as a career-defining puzzle.

Our leadership team is increasingly focused on business strategy, scaling, and customers. What we need is someone to take absolute ownership of the platform's technical depth. Whether the right path forward is a systematic untangling of the past or a calculated, strategic rewrite. That will be your call to make based on evidence. We need a brilliant technical mind to clear the path, architect a highly scalable future, and push our engineering excellence to the absolute next level.

What You Will Own:

• The Modernization Strategy: You lead the charge in conquering our technical debt while the product keeps shipping. You dictate the sequence, the stack, and the approach, whether that means evolving what's there or building anew.
• Full-Spectrum Architecture: You oversee the entire board. Backend first and foremost, but also frontend, mobile, and infrastructure/DevOps. You understand what’s happening in all of them and how the pieces fit.
• Raising the Engineering Bar: You elevate our engineering standards. Not by micro-managing every commit, but by challenging designs, setting clear quality bars, and building an environment where great engineers thrive and want to do their best work.
• Strategic Innovation: You push new technologies into the platform because they solve real scalability problems and give us a competitive edge, not just because they are shiny.

What Success Looks Like:

No micromanaged KPIs. But you should know what good looks like here.

• Technical debt going down. Visibly, steadily, without stopping the roadmap.
• New technologies landing with a concept behind them and surviving contact with production.
• Architecture decisions that hold up six months later.
• First 3-6 Months Expectations: Assess the legacy state, provide technical leadership and guidance, establish the overarching technical direction, and define the roadmap that guides the company on the right path forward.
• Teams shipping faster because the platform fights them less.