Ask HN: How well are requirements defined for you at work?

I'm a "junior" software engineer at a seed-stage startup. I've been working here for about 6 months.

I'm working with a lot of data, mainly working on ETL jobs to prepare data for Data Scientists. In my role, I typically define requirements and all of the business logic. Is this typical at a larger company, or would this be the goal of a project manager or someone similar?

I feel like I'm gaining a lot of understanding in defining what's important and what's not, but this means less time spent in the code. So I'm not sure if it's positive or negative.

I'd be interested to hear how it differs for members of the HN community.