What a Junior } should know

Understands HTTP/HTTPS, DNS basics, TCP vs UDP. Knows what ports, IP addresses, localhost are. Can use curl for API testing.

Understands the fundamentals of Chaos Engineering. Applies basic practices in daily work. Follows recommendations from the team and documentation.

Understands E2E testing fundamentals from a performance perspective: user journey-based load scenarios, end-to-end response time measurement, and bottleneck identification across system layers. Writes basic E2E performance tests using tools like k6 or Gatling. Follows team practices for test environment configuration.

Understands load testing fundamentals: user journey-based scenario design, tools configuration (k6, Gatling, JMeter), and basic metrics interpretation (response time, throughput, error rate). Writes simple load test scripts and executes predefined test plans. Follows team standards for test result reporting.

Understands fundamentals of test data management for performance testing. Prepares basic datasets to simulate realistic load conditions. Follows documented procedures for generating and cleaning up test data between benchmark runs.

Understands fundamentals of test environment management for performance testing. Sets up basic load testing environments with tools like JMeter or Gatling. Follows team guidelines for provisioning isolated environments to ensure consistent benchmark results.

Understands the test pyramid and how performance tests fit within the overall testing strategy. Knows when to apply micro-benchmarks vs load tests vs stress tests. Follows team guidelines for balancing performance test coverage across component and system levels.