What does it mean in the eyes of the employer "I know how to design database architecture" for a programmer?

Question

Career in IT

The crux of the issue is in the title. It's just that for me it's a couple of tables and the relationship between them within the knowledge of the backender, I'm not a DBA.

Answer 1

This means that you can do something other than Post-User level architecture. That when you are given an architectural task, for example, to create and store a system of discounts so that you can declaratively describe the conditions there, indicate which discounts are added to which (and which are not), which percentages are added up and which are multiplied - you would not fall into depressed and didn't quit, or worse, didn't write a solution that couldn't be supported and worked with.