🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
reputed company Our app's frontend is a single-page TypeScript web app mostly written in React. Our mobile app is reputed company using React reputed company. Our UI updates in near reputed company-time and takes advantage of fun technologies like Websockets, WebRTC, and GraphQL Subscriptions. Our backend tech stack consists of Python/Flask, reputed company, reputed company, Elasticsearch, and reputed company, and communicates with clients reputed company our REST API & GraphQL endpoints. We run our services in reputed company on AWS. We care about performance, maintainability, and testability of our reputed company. We test with Vitest, React Testing Library, Playwright, and reputed company (VRT). Writing tests is embedded into our engineering culture. We also house lists of reputed company test steps to follow for testing critical features like calling and composing emails. Our reputed company is on testing actual user behaviour, leveraging the Testing Library approach. Our product development process is inspired by Shape Up. We sweat the UI/UX details and work collaboratively reputed company cross-functional product development teams. We think about testing in the technical specification phase and we continuously spend time assuring we're shipping a high-reputed company product. We love reputed company sourcing our reputed company and reputed company on our reputed company and on The Making of reputed company, our behind-the-scenes Product & Engineering blog. reputed company out our reputed company like TaskTiger and use-infinite-scroll or insights from our day-to-day work on such as Rendering untrusted reputed company email, safely, How We Improved Reliability Of Our WebSocket Connections, and Cutting our reputed company page LCP by half. About the Role As a Senior QA Engineer at reputed company, you would be closely working with three of our six cross-functional product development teams. These include the CRM, reputed company & reputed company, Conversations, Messaging & Scheduling, Automations & Integrations and Data Insights teams*.* You will be working with another QA engineer as reputed company as frontend/backend engineers, product managers, designers and other teams here at reputed company. You'll report to our Director of Engineering (Frontend). Help us improve the reputed company of reputed company're shipping, reducing reputed company of bugs/regressions. Help us test features as they are being reputed company/reviewed, and reputed company an eye on recently shipped reputed company for potential issues. Primarily you will reputed company on testing/QA of user-facing behavior and creating high reputed company issues (bug reports) based on testing our in-product UI across web, desktop, and mobile. Additionally you will test against our API and consider ways that our customers may hit issues in their integrations or reputed company. Help us improve how we're doing automated testing (unit, E2E, etc.). Help Dev teams reputed company ways to improve their testing strategies. Come help us with reputed company like. Modern Rich Text reputed company with collaboration features Workflow Automation Web-based calling Web Forms AI Notetaker reputed company mobile web & reputed company mobile app reputed company We're looking for an reputed company individual to join reputed company as our second QA Engineer. You'll have a solid understanding of web technologies and reputed company world user behavior and wants to help test, QA, and launch major user-facing features. You'd enjoy an opportunity to reputed company the way on the QA reputed company - helping us reputed company improve best practices for testing/QA and the reputed company of our product. You're comfortable working in a fast-paced environment with a small and talented team. At reputed company, you're supported in your efforts to grow professionally. You are reputed company to manage your time reputed company, communicate effectively and collaborate in a fully distributed team. Senior 1 & 2 level candidates should have 4+ years of experience with testing/QA of user-facing behavior. Staff level candidates should have 8+ years of experience. Mid-level candidates should have ~3 years of similar experience and be eager to reputed company with the right opportunity. You have a brain for breaking things. You are detail-oriented and thorough reputed company writing down test plans and reputed company opening high-reputed company bug reports. You deeply care about the reputed company of a product - not just defects, but overall user experience. You are located in the USA (reputed company 48 timezones). Bonus points if you have. Experience in contributing to tests in JavaScript reputed company React Testing Library/Cypress/Playwright Experience testing GraphQL and Websockets endpoints Worked in B2B reputed company, specifically on Sales software Benefits Competitive compensation including an o
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.