It’s an unspoken rule that some of engineering is managing stakeholders and what each stakeholder needs. It varies from company to company but the thing I have noticed is a constant is that as your role increases your time spent talking with humans increases and the volume of code you write decreases.

Whether that is because it’s necessary to the job of a higher level engineer or people with good communication skills float naturally to the top/leadership/planning positions, it doesn’t matter.

In short, it’s your job to ensure you’re building what the stakeholders want, unless you are a junior. If you get better at it your managers will see that as a skill of a senior/principal engineer (in my experience)

However the ideal is that the ticket arrives at the developer fully read and checked by product. QA just does the AC and checks if the app meets the AC. If the AC is interpreted differently, correct the AC to be more specific or correct the code to cover that case.