QA Automation Engineer

We are IceWarp. For 20 years weve been building a communication and collaboration platform that tens of millions of people open every morning. Weve been cheerfully poking Google and Microsoft in the ribs the whole time and honestly Its been fun.

Now were looking for someone to make quality a first-class engineering discipline at IceWarp. Someone whos ready for whats 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 doesnt 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.

Youll 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 youre who they call. You dont 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 isnt a generalist tester role. It isnt a lead role either. Were hiring for a specific shape.

• Strong automation engineering instincts. Youve 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 youve 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 whats worth automating and what isnt.

• A product brain. You read a feature spec and already know whats load-bearing whats decoration and whats 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 were not married to it - if you see a better way make the case. Well 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 shouldnt. Were honest about where we are.

Who you are:

If two or more of these dont land this probably isnt the right fit. Better to know now.

• You take ownership. You spot a quality risk you take it on. No waiting around for someone else to flag it.

• You think I want users to trust this product before I want to use the trendiest framework.

• Partner not gatekeeper. You build quality in alongside developers not at the end not as a checkpoint.

• You disagree well. You push back on lets ship it anyway when theres real risk and you do it without drama.

• Feedback culture is second nature. Clear reproducible bug reports. Positive intent assumed. We focus on how things broke not who broke them.

• You default to async. Write it down. Document the why. Public channel over DM so the whole team can find what was decided.

• You commit. Push hard before the call. Execute cleanly after.

• You speak English and Czech. Most of the team runs in Czech day to day but our docs code reviews and product communication are in English. Youre comfortable switching between the two without anything getting lost.

Who you will be working with (and climbing with):

• A quick note about the team youd join. Our founder is a serious climber. Tomáš who leads the QA team loves climbing too. Were not saying theres a pattern. Were not not saying it either. :)

• And its not just talk. Every Wednesday (at least) someone from the office goes climbing at Hudy sport right around the corner. Whoever is around and feels like it just comes along. No sign-up no pressure everyones welcome.

• So if you enjoy climbing too thats a big plus probably our least serious hiring criterion but still a plus. Youd have people to climb with and maybe even someone who belays you and reviews your code (not at the same time).

• Never climbed before No problem at all. You dont need to be good at it to get the job your tests just need to be green. But dont be surprised if someone invites you along on a Wednesday.

What we are not asking for:

• Not a management role. Youll be hands-on in automation yourself - no team leading no mentoring load.

• Not X years with a specific tool. If youve built serious automation and can pick up our stack quickly thats enough.

• Not a ticket-executor. If youre looking for a backlog of test cases to work through this isnt it.

• Not email/messaging domain experience. IMAP and SMTP are learnable. Taking users trust seriously isnt. We do expect that from day one.

What we offer:

Were a Czech company challenging giants 100x our size. We cant match Big Tech comp packages and we dont pretend to. Heres what we do offer:

• Work on a Czech product used by millions worldwide (your work has a real impact)

• Freedom to bring new ideas and ship them right now

• Hybrid: 3 days/week in-office flexible hours

• Office in Karlín directly at Křižíkova metro station

• 20 days of vacation (4 via KPI System)

• 5 Personal days

• Daily snacks and office-paid lunches twice a week