u/Big-Economist9616

Hey everyone,

I recently joined a spirits company as their first QA hire. The product is quite large, but there’s very little documentation, and up until now, developers have been responsible for testing.

Right now, things feel unstructured. I often find out about new features or deployments after they’ve already happened, and testing requests come in randomly. Most of my work ends up being exploratory, without a defined process or clear expectations.

I’d like to introduce some structure and improve how testing is handled, but I don’t want to overwhelm the team or disrupt their current workflow too much.

Where would you recommend starting in a situation like this?
I’d really appreciate any advice or experiences you can share.

Hey everyone,

I recently joined a spirits company as their first QA hire. The product is quite large, but there’s very little documentation, and up until now, developers have been responsible for testing.

Right now, things feel unstructured. I often find out about new features or deployments after they’ve already happened, and testing requests come in randomly. Most of my work ends up being exploratory, without a defined process or clear expectations.

I’d like to introduce some structure and improve how testing is handled, but I don’t want to overwhelm the team or disrupt their current workflow too much.

Where would you recommend starting in a situation like this?
I’d really appreciate any advice or experiences you can share.