Joe Wolski, CTO
From Junior to Principal: Leading Work Across AI Initiatives
Hanna Domnich on growth, AI, and what it really takes to lead
Hanna Domnich started in QA at a time when the focus was simple – learn the tools, understand the product, and figure things out as you go. Over time, that practical, hands-on approach turned into something broader: working with systems, making decisions with impact, and helping shape how teams approach complex problems.
We sat down with Hanna to talk about her path from junior QA to a Principal role, the moments that shaped her thinking, and what it means to grow alongside fast-changing technology and AI-related work today.
Absolutely not. I was 20. Honestly, I was just thrilled that the kitchen had free cookies and that no one was yelling at me. That already felt like winning at life. What was on my radar back then was simple: learn, adapt, survive. And, as it turned out, those instincts became my superpower. I thrive in environments that shift faster than you can finish your coffee – new tools, new methodologies, new challenges. Instead of scaring me, they energise me.
I love that in tech, you’re never “finished.” There’s always something new to understand, some system to stress-test, some idea to chase. That constant motion is exactly what pushed me forward.
“I thrive in environments where everything changes faster than you can finish your coffee.”
For me, this transition means even more new challenges and opportunities. As we see an increasing number of experiments and AI‑driven initiatives emerging across different departments, it becomes difficult to operate effectively without a clear plan and strategy. My role now involves ensuring alignment by helping to build and continuously adapt our approaches to meet the needs of both current and new clients.

Oh yes. One hundred percent.
I still remember my very first client interview. They asked me all sorts of questions about automation and best practices – and I confidently said I knew everything. Which was technically true. In theory.
In reality, I had zero commercial hands-on experience. Not a single line of automation code was deployed anywhere except my laptop. Then came the moment: they asked how I’d implement Page Object, and where asserts should live. I had no idea what the “right” answer was. So, I said the most honest thing I could: “Wherever it’s convenient.” Full confidence. As if it were an established industry standard.
And the crazy part? It went great. They hired me. That story perfectly captures how my career grew: say yes, figure it out, learn fast, adapt even faster. That strategy hasn’t failed me yet.
The hardest shift was moving from “checking if things work” to truly understanding how systems behave – architecture, integrations, edge cases, real risk. I had to stop thinking like a user and start thinking like an engineer. Not “does it work?” but “why does it work, when might it fail, and what’s the real impact if it does?”
Emotionally, it meant learning to sit with discomfort: asking questions that felt basic, owning decisions with real consequences. But that’s exactly where growth lives. Once you cross that threshold, QA stops being a job and becomes a craft.
“Say yes, figure it out, learn fast, adapt even faster. That strategy hasn’t failed me yet.”

I was lucky. My first tech lead was an extraordinary mentor. She never handed me answers – she taught me how to find them myself. Giving me the fishing rod instead of the fish. Head of QM Volha Khudzinskaya taught me to think beyond test cases – toward product value, risk, and real business impact. That mindset still shapes how I work today.
And my Team Manager pushed me to take ownership and make independent decisions. Instead of ready-made answers, he guided me toward building my own solutions. What made all three so valuable was the same thing: high expectations paired with genuine trust. As a junior, it’s easy to doubt yourself – but they built an environment where it felt safe to grow, make mistakes, and improve. I’m endlessly grateful for that start.
Yesterday, probably. Kidding. Learning never really stops – and that’s kind of the point. The shift happened when I moved from focusing on my own execution to owning direction and strategy. Today, I lead a complex project alongside people who constantly raise the bar, and I also lead the AI Practice across several global R&D initiatives. That’s probably when the mindset really changes – when you’re not just delivering but influencing how the whole thing evolves.
Excitement – and honestly, a sense of inevitability. Humanity has navigated shifts like this before. Every major technological leap looked disruptive at first, and every time, we learned to integrate it. Writing, books, digitalisation, software, algorithms. And now AI.
I’m not afraid of it. I want to help shape how we get there – not by resisting the change, but by guiding it wisely. And being at the frontier where no one has a ready-made blueprint? That’s exactly the kind of challenge I thrive on.

If there’s a problem, there’s a solution – and I’ll find it. At some point in your career, you stop looking for someone else’s blueprint and start building your own. You research, experiment, break things, and rebuild them better. It’s not always easy – but it’s empowering. Because once you trust your own ability to figure things out, you stop waiting for guidance and start leading.
“Once you trust your own ability to figure things out, you stop waiting for guidance – and start leading.”
Run regular retrospectives with yourself. What worked, what didn’t, where’s your next growth point? Be honest – but kind. Growth is rarely loud or dramatic. Most of the time, it feels quiet, incremental, and slightly uncomfortable. That discomfort is the signal, not the warning.
No one starts out ready. What matters is consistency: show up, stay curious, learn from mistakes, and don’t demand perfection from yourself on day one. Big careers are built from small, repeated steps. If you keep moving, you’ll get much further than you think.
Joe Wolski, CTO
Sr. JavaScript Software Engineer Robert Oleksza