Vitaly Sharovatov

Our Berlin Quality Engineering community came together for another evening, this time at a new venue, W3.Hub, which turned out to be a fantastic spot for the event. Around 70 people showed up, and the energy was as good as ever: three very different talks, great pizza, and the

Ages ago, I applied for a software developer job, and after a short briefing the recruiter sent me a link to an MBTI profiling service. I smiled and politely rejected the opportunity. Most engineers I know laugh at pseudo-scientific "psychological" profiling like MBTI / DISC, and laugh even harder at folks

Our Berlin QA community got together again for what was actually our 10th meetup. Ten evenings of talking about quality, risk, weird edge cases, all about the beautiful work of setting order in messiness. I keep saying this, but it is still true every time. I am really happy to

Many years ago, while working for a bank, I was a member of the techleads guild. Being a guild member in large companies often comes with the responsibility to interview people, and I interviewed a lot. Sometimes I had up to twelve interviews a week. I still shudder remembering these

Amsterdam gave us the usual November package: cold, grey, a bit of rain. But inside the JetBrains office it was warm, bright, and full of people who actually like talking about testing, which is all I really need. More than 40 folks showed up, grabbed some pizza, found their spots,

AI in software testing: real capabilities, real limits Artificial intelligence is already embedded in modern software testing, from generating test cases and stabilizing UI automation to prioritizing tests in CI/CD pipelines. At the same time, bold claims about autonomous AI testers and self-directed test agents continue to outpace reality.

Introduction Testing is one of the few engineering activities that directly determines whether a company survives or collapses. When testing fails, it’s not just bugs that slip through. This failure might incur financial, operational, and reputational damage that will devastate the entire organization. Consider just a few examples: * In

Our beautiful Berlin QA community gathered again in early October, and even with autumn in full swing, around 70 people showed up for another great evening of ideas, demos, and honest conversations about quality. I’m so damn happy to see how this community has grown: familiar faces who’ve

Test automation is often treated as a checklist item: if you have it, great; if not, build it. But too many teams automate without knowing what value they expect, or how to measure whether the investment is paying off. That’s a problem. Because automation is an investment. Like any