Same here but no one hires for a DBA, just keep moving me between projects to put out fires or get them finished one-time or not later then they're already running. Few are actually interested in learning details of designing schema/indexes/queries to be good before there's a problem. I keep telling them to put example SQL queries in PR descriptions with EXPLAIN query plans hoping it will click for them.
My view is that the schema + queries is the essential performance consideration. The code that goes from one persisted state to another is largely plumbing implementation detail. Of course there also lots of precise logic there but it's a healthy alternate view. The first thing I do on any project I join is make a big ERD to know the names, cardinalities, and relations (and wonder how they keep changing that without an up-to-date picture).