I went through some similar situations. Early on, one of the very senior developers -- and one of the smartest guys at the place -- figured out that I knew what I was talking about. Sometimes I might raise a concern out of ignorance, but even then, I was asking good questions.

When things moved from simply "compromise" or "somewhat ugly" to an outright risk, occasionally I'd have to escalate past a senior developer or architect to this guy.

It rubbed some people the wrong way, but over time, when they learned that I wasn't doing it out of ego but simply out of concern, most of them at least partially got over this.

P.S. Fortunately, many of them were already fairly seasoned and "battle scarred" and had themselves learned to focus on what mattered. As often as not, my concern was an irritant as much as anything because of the additional time and attention it would demand of already loaded schedules. I reserved escalations for real risks and/or long term implications, to minimize this.