QA Wolf logo

QA Wolf Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 5 interview experiences · FREE TO READ

2.2 Rounds average
Average Typical difficulty
40% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at QA Wolf.

Showing 3 of 5
QA Wolf logo
QA Wolf

Software Engineer

Engineering · a year ago

Entry Average Negative experience No offer 3 rounds
Interview process
Take home Presentation Recruiter call
Interview formats
Coding Presentation Behavioral

I was asked to do a coding challenge using Playwright. The task was to scrape and sort 100 articles from newest to oldest. After that, I had to make a 2-minute video using Loom where I answered why I want to work at QA Wolf and did a code walkthrough. I completed the coding challenge, made the video, and even put in a current employee's name for a referral. The next day, I got a generic rejection email saying I did a 'great job' but other candidates were a 'better match,' with no further details. Based on the Loom view count, it seems like my video wasn't even watched. I don't feel my time was respected.

Confirmed questions1 question
  • What makes you want to join QA Wolf?
QA Wolf logo
QA Wolf

Software Developer

Engineering · more than a year ago

Mid Average Positive experience No offer 3 rounds
Interview process
Take home Recruiter call Onsite
Interview formats
Other Behavioral Technical

First, there was a take-home project where I used their product, and I was paid for it. Then, I had a quick behavioral chat with the founder. After that, I had a 'virtual onsite' which was half a day and paid. I thought the onsite meant working with the team for a few hours to see how I'd fit in, but it was actually another assessment by the founder. They kept an eye on my progress and chatted with me on Slack.

Confirmed questions1 question
  • Onsite, I was asked to use the product to test a specific feature on a page.
QA Wolf logo
QA Wolf

QA Software Engineer

Engineering

Entry Difficult Positive experience No offer 2 rounds
Interview process
Take home Technical screen
Interview formats
Technical Coding

There were two main parts to the interview. First, an at-home assignment which was not timed and had no specific due date. They didn't even ask for my resume, just to complete the assignment, record an intro and explanation, and send it back. Second, a sample project that took place during the interview itself. It was a 2-hour session where the first 5-30 minutes were for introductory questions, and the rest of the time was dedicated to producing work on their platform. They provided a tutorial and suggested using online resources like AI agents and Playwright best practices documentation for preparation. They paid for this part of the process, which was a nice gesture. I haven't heard back yet, and given my performance, I'm assuming I didn't get the job.

Confirmed questions1 question
  • What inspired you to pursue software engineering?

QA Wolf Software Engineer Interview Questions

Quoted word for word from QA Wolf interview reports.

Would you consider including assertions in your Playwright tests? It's highly recommended for moving forward.

Read reports

For the take-home assessment, could you test Netflix's login and password security using Playwright?

Read reports

Onsite, I was asked to use the product to test a specific feature on a page.

Read reports

Formats, difficulty and experience

Across all 5 QA Wolf interview reports.

Interview formats

Technical 27.3%
Coding 27.3%
Other 18.2%
Behavioral 18.2%
Presentation 9.1%

Interview difficulty

Easy 0%
Average 80%
Difficult 20%

Candidate experience

Positive 40%
Neutral 40%
Negative 20%