Back to Jobs

Quality Test Engineer

Not Disclosed

Job Description & Details

This is a hands‑on QA role focused on Java/Spring Boot services, based fully onsite in Illinois. You’ll be writing and executing tests, hunting bugs, and making sure the code ships clean.

What You'll Actually Be Doing

You’ll spend most of your day writing unit and integration test cases in Java, pulling data from SQL databases, and exercising Spring Boot endpoints. Expect to own defect tracking from discovery to closure, work closely with developers to reproduce issues, and help improve the testing framework as the product evolves. The role is 100 % onsite, so you’ll be in the same room as the engineering team, doing rapid feedback loops.

The Core Tech Stack

The team lives in a Java‑centric world: Spring Boot back‑ends, relational databases accessed via SQL, and a test suite built around JUnit/TestNG (sometimes Selenium for UI). You need to be comfortable writing code‑level tests, mocking services, and understanding how Spring’s dependency injection affects test isolation. Those skills matter because the product’s reliability hinges on catching regressions before they hit production.

Interview Expectations

  1. Design a test strategy for a Spring Boot microservice that talks to a PostgreSQL database. The interviewer wants to see if you can separate unit, integration, and end‑to‑end layers, decide what to mock versus what to spin up in a test container, and articulate coverage goals.
  2. You have a flaky test that passes 80 % of the time. How do you diagnose and fix it? They’re probing your debugging process: looking for race conditions, external resource dependence, or non‑deterministic data, and whether you use logs, retries, or test isolation techniques.

Application Advice

Tailor your resume to mirror the JD: lead with “2‑4 years of QA experience” and list “Java, SQL, Spring Boot” as core competencies. Mention concrete achievements like “Reduced critical bugs by 30 % through automated regression suite” and include the exact tools (JUnit, TestNG, Selenium, JIRA) to hit ATS keywords. Highlight that you thrive in an onsite environment and can collaborate face‑to‑face with developers.