First was a 15-minute call with the recruiter.

Followed by a 30-minute tech call about experience and some QA questions.

Received an on-site interview about two weeks later, with four rounds. The first round was with a new PM, followed by two different QA Analysts, and lastly the person who would be my manager.

A few days later, I received the final steps email, to answer some QA questions and try to find a bug or issue within their application.

Submitted, everything was good; I was told they loved my response. Just had to submit two references for them to speak with.

About a week later, I got a call saying that they could not offer me the position at that time because they didn't have the budget or whatever. They said they would keep in contact. I followed up two months later and was told they don't have the right position for me at the moment. I left it at that and never reached back out. I don't know what happened over there, but they could have been 100% honest as to why they didn't offer after almost two months of back and forth.

How do you get an understanding of how users interact with the features your team builds?

How do you use that information to provide input back into the product development process to help improve future features/products?

Identify and explain a flaw you see within QA as a discipline.

Write a test case for a piece of functionality that you find on https://vimeo.com. For example, verify that a user can upload a video and view the video on the "manage videos" page.

Identify a significant usability problem in one of Vimeo's features/products. Why do you think it’s a problem?

If you were to write up a Jira ticket describing the problem and suggesting a solution, what information would you include? Use the problem you identified to write out an example.

Describe an inconsistency in Vimeo’s creator tools, as well as why you think this inconsistency should be addressed. This could be related to discrepancies in messaging, the UI, the cross-platform experience, etc.