メインコンテンツへスキップ
SDETRole
SDETRole

キャリア

QA・SDET スキルギャップ・チェックリスト

目標の QA/SDET 職と比べて自己評価し、ギャップを順位付け。

すべてブラウザ内で動作 登録不要

Writes production-quality test code inside an existing framework and pipeline.

Rate yourself honestly: 0 None · 1 Aware (can explain it, needs help to use it) · 2 Working (does it alone on real work) · 3 Expert (designs it, reviews others, teaches it).

Testing fundamentals

  • Test design techniquesexpected: Working

    Boundary values, equivalence partitions, decision tables and state transitions applied to real requirements.

  • Exploratory testingexpected: Working

    Chartered sessions with notes, heuristics (SFDPOT, tours) and findings others can act on.

  • Defect reporting and triageexpected: Working

    Minimal reproduction steps, evidence, severity vs priority, and root-cause conversations with developers.

  • Risk-based test planningexpected: Aware

    Choosing what not to test, estimating effort and writing a test plan stakeholders read.

  • SQL for test data and verificationexpected: Working

    Joins, aggregates and safe updates to set up data and verify persistence.

Programming

  • One language in depth (Java, TypeScript or Python)expected: Working

    Types, collections, error handling, async code and reading stack traces without help.

  • Clean code and design patternsexpected: Working

    Composition over inheritance, page objects/screenplay, builders and factories for test data, small functions.

  • Git and code reviewexpected: Working

    Branches, rebasing, resolving conflicts and giving useful review comments on test code.

  • Unit and component testingexpected: Working

    Writing and reviewing unit tests with mocks and fakes, and knowing where they beat end-to-end tests.

UI automation

  • Playwright, Selenium or Cypressexpected: Working

    Stable locators, auto-waiting vs explicit waits, fixtures/hooks, screenshots and traces.

  • Framework designexpected: Aware

    Layering, configuration per environment, test data management, reporting and parallel safety.

  • Flaky test diagnosisexpected: Working

    Using traces, retries data and timing analysis to fix root causes instead of adding sleeps.

  • Mobile automation (Appium, Espresso, XCUITest)expected: Aware

    Device/emulator setup, capabilities and gestures; knows the trade-offs of each tool.

API testing

  • HTTP, REST and auth fundamentalsexpected: Working

    Methods, status codes, headers, idempotency, OAuth 2.0 and JWT basics.

  • API automation (REST Assured, Playwright request, pytest + requests)expected: Working

    Request builders, schema assertions, chained calls and data cleanup.

  • Contract testing and mockingexpected: Aware

    Consumer-driven contracts (Pact) and service virtualization (WireMock) to test in isolation.

CI/CD and DevOps

  • CI pipelines (GitHub Actions, Jenkins, GitLab CI)expected: Working

    Running suites on pull requests, sharding, caching, artifacts and failure notifications.

  • Docker and test environmentsexpected: Aware

    Dockerfiles and Compose for dependencies, ephemeral environments and seeded databases.

  • Logs, metrics and observabilityexpected: Aware

    Finding failures in logs and dashboards; using trace IDs to connect a test to backend behaviour.

Non-functional testing

  • Performance testing (k6, JMeter, Gatling)expected: Aware

    Workload models, percentiles, thresholds and interpreting results with the team.

  • Security testing basicsexpected: Aware

    OWASP Top 10 awareness, input validation probes, auth/authorization checks and safe use of scanners.

  • Accessibility testingexpected: Aware

    WCAG 2.2 basics, keyboard and screen-reader checks, and automated axe scans in CI.

Strategy and leadership

  • Test strategy and the test pyramidexpected: Aware

    Deciding what belongs at unit, API, contract and UI level for a system, and defending it with data.

  • Quality metricsexpected: Aware

    Escaped defects, change failure rate, suite duration and flakiness rate; avoiding vanity metrics.

  • Mentoring and stakeholder communicationexpected: Aware

    Coaching juniors, release sign-off conversations and explaining risk to non-testers.

  • Agile delivery and shift-left practicesexpected: Working

    Three-amigos sessions, acceptance criteria review, definition of done and testing in the sprint.

AI in testing

  • AI-assisted testing toolsexpected: Aware

    Using code assistants for test code and data with review, and knowing their failure modes.

  • Testing AI/LLM featuresexpected: None

    Evaluation sets, non-deterministic outputs, guardrails and regression of model-backed features.

Readiness

0%

Sum of your levels (capped at each expectation) ÷ sum of expected levels for SDET 1. 27 of 27 expected skills below target.

  • Testing fundamentals0/5
  • Programming0/4
  • UI automation0/4
  • API testing0/3
  • CI/CD and DevOps0/3
  • Non-functional testing0/3
  • Strategy and leadership0/4
  • AI in testing0/1

Biggest gaps

  1. Agile delivery and shift-left practices0 → 2
  2. API automation (REST Assured, Playwright request, pytest + requests)0 → 2
  3. CI pipelines (GitHub Actions, Jenkins, GitLab CI)0 → 2
  4. Clean code and design patterns0 → 2
  5. Defect reporting and triage0 → 2
  6. Exploratory testing0 → 2
  7. Flaky test diagnosis0 → 2
  8. Git and code review0 → 2

Where to start

  • Testing Fundamentals11 gap pts

    Agile delivery and shift-left practices, Defect reporting and triage, Exploratory testing, SQL for test data and verification, Test design techniques, Risk-based test planning

  • Programming for Testers8 gap pts

    Clean code and design patterns, Git and code review, One language in depth (Java, TypeScript or Python), Unit and component testing

  • Advanced Quality Engineering6 gap pts

    Accessibility testing, Mentoring and stakeholder communication, Performance testing (k6, JMeter, Gatling), Quality metrics, Security testing basics, Test strategy and the test pyramid

  • Automation Frameworks6 gap pts

    Flaky test diagnosis, Playwright, Selenium or Cypress, Framework design, Mobile automation (Appium, Espresso, XCUITest)

  • API Testing5 gap pts

    API automation (REST Assured, Playwright request, pytest + requests), HTTP, REST and auth fundamentals, Contract testing and mocking

  • DevOps for QA4 gap pts

    CI pipelines (GitHub Actions, Jenkins, GitLab CI), Docker and test environments, Logs, metrics and observability

  • AI in Testing1 gap pts

    AI-assisted testing tools

Start rating

Unrated skills count as 0. Your ratings stay in this browser.

このツールについて

テスト分野の職種名は会社によって意味が異なりますが、その背後にあるスキルはかなり一貫しています。このチェックリストは、QA エンジニア、SDET、テストアーキテクトの仕事を、テストの基礎、プログラミング、UI 自動化、API テスト、CI/CD、非機能テスト、戦略とリーダーシップ、テストにおける AI にわたる 28 の具体的なスキルに分解しています。目標とする職種ごとに、「Aware」(知っている)から「Expert」(エキスパート)までの典型的な期待レベルを示します。自己評価すると、ツールがギャップを大きさ順に並べ、明示された計算式で求めた準備度をパーセンテージで表示し、どこから始めればよいかわかるようにギャップを学習パスごとにまとめます。期待レベルはプロダクト企業における現実的なデフォルトであり、正式な基準ではありません。次の 1on1 での話のきっかけとして読んでください。

使い方

  1. 現在の職種ではなく、目指している職種を選びます。
  2. リストの上にある定義に従って、各スキルを 0〜3 で評価します。厳しめに評価してください。「Working」(実務レベル)とは、実際のプロジェクトで一人でできることを意味します。
  3. 右側に表示される最大のギャップと、おすすめの学習パスを確認します。
  4. マネージャーやメンターと共有するために計画をコピーします。評価はこのブラウザに保存されます。

QA・SDET スキルギャップ・チェックリスト のよくある質問

準備度はどのように計算されますか?

職種が求める各スキルについて、あなたの評価を期待レベルで頭打ちにし、その合計を期待レベルの合計で割ります。職種が知識程度しか求めないスキルでエキスパートであっても、別のギャップを埋め合わせることはできません。

ここでの SDET 1 と SDET 2 の違いは何ですか?

SDET 1 は、既存のフレームワークとパイプラインの中で良いテストコードを書きます。SDET 2 は、フレームワークの一部、CI 連携、チームのテスト戦略を担うことが期待され、それがフレームワーク設計、フレーキーテストの診断、CI、コントラクトテストに対するより高い期待レベルとして表れています。

これらのレベルは業界標準ですか?

いいえ。QA のキャリアレベルに単一の標準はありません。これらはプロダクト企業における典型的な期待値です。お勤め先にキャリアフレームワークがある場合は、そちらが優先されます。

キーワードを入力すると SDETRole 全体を検索できます。

Pagefind による全文検索 · ブラウザ内で動作します 検索ページを開く →