次の仕事の機会を見つけましょう

職種、スキル、勤務地で求人を検索できます。応募書類を準備する前に募集要件を確認しましょう。

魅力的な職種名を見つけることは、仕事探しの出発点です。業務内容、応募条件、働き方を自分の経験と照らし合わせましょう。このガイドでは、候補の絞り込み、応募書類の準備、提出先の確認を順番に進めるためのポイントを紹介します。

操作画面は日本語です。企業が掲載した求人の職種名や説明文は原文のまま表示され、英語の場合があります。

条件をクリア

検索結果: 11,128

← 検索結果に戻る

Production Quality Control Specialist

Drips

リモート勤務

勤務地
Remote (United States)
勤務時間
Full Time
掲載日
2026年10月10日

応募する前に、企業のウェブサイトで現在も募集中かどうかと詳しい条件を確認してください。

仕事内容

操作画面は日本語です。企業が掲載した求人の職種名や説明文は原文のまま表示され、英語の場合があります。

Quality Control Specialist Department: Production Location: Remote (U.S.) Employment Type: Full-time (40 hours/week) About Drips Drips engages people in two-way, compliance-governed SMS conversations — the kind that get responses, drive action, and close the gaps traditional outreach leaves open. In practice, that means Drips helps organizations connect with their customers through large-scale, automated text and phone campaigns. Our proprietary platform lets clients design conversations, schedule outreach, and route responses so the right messages reach the right people at the right time. The Quality Control Specialist role is what confirms those campaigns actually work the way they're supposed to before real customers ever see them. Role Overview As a Quality Control Specialist, you test our product. You take completed builds and verify, end to end, that they behave the way they're supposed to in real-world conditions — not just that the settings look right on screen, but that messages send on time, calls route correctly, and the experience holds up once it's live. You'll manage a steady queue of cases moving through QC, prioritizing your work so nothing sits and nothing slips through untested. You will: Run functional and regression tests on completed builds to confirm they perform as intended — checking timing, routing, message content, and call behavior against real-world scenarios. Own a queue of QC cases from intake through completion, picking up work once Build has finished configuring it and seeing each case all the way through to a clean, documented close. Identify, document, and communicate defects clearly, so the right fix gets made by the right team without back-and-forth guessing. This role calls for a bit more technical depth than some other Production roles — you'll want a real grasp of how the system behaves and why, not just how to click through it. What You’ll Do Execute Functional & Regression Testing Test completed campaign builds end to end: message timing and sequencing, call routing, audio playback, and digit-press behavior. Verify that changes behave correctly across real-world conditions — different carriers, devices, and time zones — not just in an idealized test case. Run regression tests to confirm that a fix or change hasn't broken something else in the process. Own a Queue of QC Cases Manage a steady flow of cases moving into QC once Build has finished its work, prioritizing based on urgency, launch dates, and complexity. See each case through from intake to a fully tested, documented close — you're the last check before something goes live. Keep the queue moving without letting cases stall or pile up. Partner with Build and Product Engineering Coordinate directly with the Build team when a case needs rework, giving them clear, specific detail on what didn't pass and why. Work with Product Engineering when an issue traces back to the underlying system rather than a specific campaign configuration. Translate technical findings into plain language so both technical and non-technical partners understand what was found and what it means. Document and Report on Quality Document test cases and results in a test management platform, so there's a clear record of what was tested and how it performed. Maintain a dashboard of defect results to track trends and flag recurring problem areas. Deliver regular reports to leadership summarizing findings, risks, and improvement opportunities. Examples of Day-to-Day Tasks On a typical day, you might: Pick up a case handed off from Build after a new campaign has been configured and run it through end-to-end functional testing — confirming routing, timing, audio, and message delivery all behave as intended before closing it out. Investigate a reported defect, reproduce it, document the steps clearly in our test management platform, and route it to Build or Product Engineering depending on where the issue actually lives. Test message delivery across a few different carriers and devices to confirm consistent real-world performance. Review your queue, reprioritize based on an upcoming launch date, and clear through routine cases so nothing sits untested. What You’ll Need to Succeed This role blends strong queue management with real technical depth — you're not just running through a checklist, you're verifying that a live system behaves the way it's supposed to. Strong queue management: you can manage a steady flow of QC cases, prioritize by urgency and launch date, and keep work moving from intake to completion without letting cases stall. Comfort with test management tools: experience with a test management platform to document test cases, execute test suites, and track results. Strong analytical skills and attention to detail: you catch the inconsistency or edge case that others miss, and you can spot a trend across a batch of defects, not just a one-off issue. Good communication skills: you can document a defect clearly enough that someone else can reproduce and fix it, and explain findings in plain language to non-technical partners. Work Environment This is a remote role; you’ll collaborate daily via chat, video calls, and shared documentation. You’ll spend most of your time in our internal testing and configuration tools, in our test management platform tracking test cases, and in our ticketing system managing your QC case queue. You’ll work closely with the Build team and Product Engineering, in a team that values accuracy, thoroughness, and clear documentation. How to Apply If this sounds like you, please apply via the Drips careers page and include: Your resume. A brief summary of why you think you’d be a good fit for this role in a cover letter. We look forward to reviewing your application. Originally posted on Himalayas

検索して比較し、応募を準備しましょう

次の仕事で活かしたい職種やスキルから検索を始めましょう。勤務地と職種の条件を調整し、求人を開いて担当業務を比較してください。結果がない場合は、短い検索語を試すか、条件を一つずつ外してみましょう。

必須条件と歓迎条件を分けて確認し、勤務時間、報酬、勤務地が掲載されている場合は目を通しましょう。リモート勤務でも、居住国、就労資格、勤務時間帯が指定されることがあります。現在の募集状況と詳しい条件は企業に確認してください。

募集要件に関連する実際の経験を選び、自分の役割と貢献を説明しましょう。数値は根拠がある場合にのみ使ってください。企業の応募方法に従い、送信前に連絡先、内容、PDFの表示を確認しましょう。

応募前の確認リスト

仕事探しに関するよくある質問

英語の求人が表示されるのはなぜですか?

職種名や説明文は企業が作成したものです。条件や要件を変えないように原文を掲載しています。操作画面とこのガイドは日本語です。日本語の検索で見つからない場合は、「software engineer」のように、掲載言語の職種名やスキル名でも検索してみてください。検索語が自動翻訳されるわけではありません。

リモート求人なら、どの国からでも働けますか?

必ずしもそうではありません。居住国、就労資格、勤務時間帯が指定されている場合があります。元の求人ページで条件を確認してください。記載がない場合は、自分の居住地から応募できると判断する前に企業へ確認しましょう。リモートという表示だけでは、勤務地の制限がないことは分かりません。

検索結果が出ない場合はどうすればよいですか?

より一般的な職種名や一つのスキルで検索し、条件を一つずつ外してみてください。同じような仕事でも企業によって呼び方が異なります。特定の求人が見つからなくなった場合は、企業の採用ページで求人番号を探しましょう。検索条件を広げても、終了した募集が再開するわけではありません。

ResumizeAIから応募が送信されますか?

応募ボタンは外部サイトを開きます。企業または採用サービスの案内に従い、そのサイトで送信を完了してください。ResumizeAIで応募書類を作成しただけでは応募は送信されません。リンク先が企業のトップページの場合は、該当する募集を探してから手続きを進めましょう。

応募書類とカバーレターはどう調整すればよいですか?

募集要件と、自分が説明できるプロジェクト、業務、成果を結び付けます。経験していない技術や実績を加えず、関連する経験を分かりやすく示してください。カバーレターでは応募理由を具体例とともに伝えます。指定された言語とファイル形式に従い、送信前に両方の書類を確認しましょう。