Yep. It's part of your job to tell managers "yes, it's possible, but it'll negatively affect performance in a significant way because of such and such hardware limitations, so it's not the most valuable feature to implement at this time".
And it's part of the manager's job to tell you "I agree but don't care. Do it anyway or I will find somebody else to do it. For cheaper." Always remember that you are replaceable.
When the newborn is crying and wants food you do what you've got to do. And there are many people like that.
Most of the time the hardware team doesn't get to choose their hardware. There is usually a budget and in automotive you can select only hardware that has some specific certifications for use in a car so that narrows the list even further.
And once that hardware is selected for a given range of vehicles, it's literally impossible to change. Updates to some parts of the software stack are also basically impossible at a certain point.
It’s your job to tell them if the requirements cannot be met and that something’s gotta give. It’s his job to decide what, and it looks like he’s choosing latency When push comes to shove.
