Verloop.io is the world's leading customer support automation platform. It helps businesses deliver delightful support experiences to their customers, across channels.

Verloop.io

About Verloop: We are the world's leading customer support automation platform. We help B2C businesses automate their conversations with customers and make them highly personalized. This enables them to run an automated 24×7 customer engagement platform. Businesses use Verloop as an end-to-end chat platform to automate customer support, generate more leads, qualify leads, push relevant offers, and more. Verloop’s conversation chatbot is trained with our home-grown natural language processing and understanding layers that are built using advanced language models.
Verloop processes 60 M+ messages/day and achieves 94.56% accuracy, 92% support queries resolved, 100+ million unique users reached.&nbsp;

Our Values: At Verloop.io, we believe that the internet was the single largest revolution for global communication. It’s how you can talk to your friends and family across the globe in seconds, and how we’re talking to you right now. But even as technology was built to make it quicker and easier for people to talk to each other, businesses didn’t buy in – using old tools and older ideas. Verloop.io aims to achieve a single mission – to help enterprise businesses help their customers better. From creating easier outreach to building more meaningful relationships, our technology-first focus empowers businesses to get the most out of every interaction.
In chasing this goal, we hold four key values close to our heart: Passion, Commitment, Leadership, Customer Fixation. What you'll work on
<ul>
<li>
Own the test strategy across backend services, APIs, and user-facing flows — deciding what gets automated, what gets load-tested, and what genuinely needs a human eye.
</li>
<li>
Own and evolve our Playwright (Java) UI automation suite — the QA team maintains it end-to-end: framework architecture, selectors and fixtures, parallelization, and keeping it fast and flake-free as the product UI changes.
</li>
<li>
Build and maintain automation frameworks for API and integration testing (REST/gRPC-style RPC services), with coverage that runs in CI on every change.
</li>
<li>
Design end-to-end test suites for real-time conversation flows — chat and voice — including the messy parts: retries, timeouts, out-of-order events, and provider failovers.
</li>
<li>
Run performance and load testing against tight latency budgets (k6, Locust, JMeter, or similar) — establish baselines, catch regressions before they ship, and publish results engineers actually read.
</li>
<li>
Test event-driven and asynchronous systems — message queues, idempotency, deduplication, exactly-once vs at-least-once semantics, and clock-skew edge cases.
</li>
<li>
Verify integrations with third-party providers behind mocks and contract tests, so vendor quirks are caught in CI rather than in production.
</li>
<li>
Define and track quality metrics — escape rate, flaky-test burn-down, coverage per service, time-to-detect — and use them to drive where testing effort goes next.
</li>
<li>
Reproduce and triage production issues that span application logic, infrastructure, and third-party services; turn every incident into a regression test.
</li>
<li>
Gate releases with clear, documented criteria — and have the judgment (and standing) to hold a release when the data says to.
</li>
<li>
Mentor engineers on testability — push for designs that are observable and verifiable, and review test plans in design reviews, not after the code lands.
</li>
</ul>
What we're looking for
<ul>
<li>
5–8 years in QA/test engineering, with at least 2–3 years owning test strategy or automation for backend/distributed systems — not just executing someone else's test plan.
</li>
<li>
Strong programming skills in Java — our Playwright UI automation suite is Java-based, and you'll own it. You write automation as production code: reviewed, versioned, and maintained.
</li>
<li>
Hands-on Playwright experience (or deep Selenium experience with willingness to ramp up on Playwright quickly) — page-object design, handling dynamic waits properly,&nbsp;
and running suites in parallel without cross-test interference.
</li>
<li>
Hands-on experience testing APIs and asynchronous/event-driven systems — you know why "it passed locally" means nothing for a system with queues and retries.
</li>
<li>
Real performance-testing experience: designing load profiles, interpreting percentile latencies (p95/p99, not averages), and distinguishing an app regression from an infra blip.
</li>
<li>
Comfort with the operational layer — reading Kubernetes manifests, tailing pod logs, querying metrics dashboards, and using traces to localize a failure.
</li>
<li>
CI/CD fluency — you've wired test suites into pipelines (GitHub Actions, GitLab CI, Cloud Build, or similar) and fought flaky tests to near-zero.
</li>
<li>
Strong written communication — clear bug reports with reproduction steps, test plans that scope risk before code is written, and post-release quality summaries. This is the signal we care about most at this level. Nice to have
</li>
<li>
Working understanding of Go and TypeScript — our backend services are Go and the frontend is TypeScript, so being able to read the code you're testing helps you localize failures faster and write sharper bug reports.
</li>
<li>
Experience testing conversational AI, chat, or voice/telephony products (SIP, WebRTC, ASR/TTS pipelines).
</li>
<li>
Exposure to contract testing (Pact or similar) or chaos/fault-injection testing.
</li>
<li>
Experience testing billing, payments, or other correctness-critical financial flows where "mostly right" is a bug.
</li>
<li>
Prior experience mentoring QA engineers or bootstrapping a QA function/practice from scratch.
</li>
</ul>