Senior QA Automation Engineer

We are IceWarp. For 20+ 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 we're looking for someone to make quality a first-class engineering discipline at IceWarp. Someone who's ready for what's coming with AI or without it.

Why we are hiring

When you run a platform at our scale, quality is the product. "It mostly works" doesn't fly when 50+ million mailboxes depend on you.

Right now our testing is roughly 60% manual, 40% automated. We want to fix that ratio and we want you to be the one who fixes it.

You'll join as a peer to our developers. No ticket queue to grind through. Just a real, meaty challenge: push automation coverage up across the pipeline and help the whole team ship faster, with confidence.

What you will own

Outcomes. Not outputs.

•

Automated test coverage. UI, API, integration across the full product, from web client to backend. Stable, readable, maintainable. Not a flaky pile that nobody trusts.

•

Shifting the 60/40 balance. You own moving that line. Automate the regression and critical paths that eat the most time. Make the manual work surgical.

•

Test automation in CI/CD. Suites wired into GitLab and TeamCity, kept fast and green. A red build should mean something real — not "probably fine, let it go."

•

Unblocking developers. When a dev needs a test harness, a tricky integration covered, or help reproducing a nasty bug — you're who they call. You don't write their features; you make it safe for them to ship.

•

Keeping automation honest. Flake-rate cleanup, test maintenance, environment setup, reporting. Not the headline, but absolutely part of owning quality.

Where you spike

This isn't a generalist tester role. It isn't a lead role either. We're hiring for a specific shape.

•

Strong automation engineering instincts. You've built test suites other engineers actually depend on. You think about maintainability, structure, and second-order effects. You enjoy the work most people find boring (flake hunting, pipeline reliability, test infra), because you've seen what happens when nobody owns it.

•

Manual + automation depth. Your core is automation, but you know manual and exploratory testing well enough to decide what's worth automating and what isn't.

•

A product brain. You read a feature spec and already know what's load-bearing, what's decoration, and what's going to bite someone in six months.

•

Tool-pragmatic. Our current stack is Python for backend, Playwright + TypeScript for frontend, and Python + Appium with emulators for mobile. It works well, and we're not married to it - if you see a better way, make the case. We'll listen.

What the team watches

No personal scorecard. But you should know what good looks like here.

•

Automation coverage - and how it moves over time.

•

Pipeline health on master - green is the default, not a quarterly achievement.

•

Flake rate - because bad signal is worse than no signal.

•

Change failure rate - how often a merge breaks something a user notices.

•

Escaped bugs - how much slips through that shouldn't. We're honest about where we are.