When stuff like this happens, it's a process issue, not an issue with a particular engineer. It's human nature to try to assign blame to people and that's why it's so important to avoid that. Whatever process created the flawed product is where the blame lies.
Somewhere in the group that produced MCAS, there's a process to permit changes to be submitted, reviewed, accepted or rejected, implemented and tested along with the documentation produced at each stage.
Maybe that process is broken, maybe it isn't. From the outside we can't tell. However, as responsible professional software developers what we should do is understand that these are system problems and not just look around for someone to pin the blame on.
These are systems problems, I fully agree, but they aren't only systems problems. The systems in question are people. They have minds, personalities, and agency. Eliding this - sorry for saying so - makes phrases like "whatever process created the flawed product [...]" sound absurd, borderline callous.
I hate to resort to what by now is a web forum trope, but would you look the MAX victims' families in the eye and say, word for word, what you wrote above: "No, 'they' shouldn't" be held to account? Come on dude.
[0] https://www.seattletimes.com/seattle-news/times-watchdog/the...
For me, in a crisis with a lot of burning questions, one I haven't seen raised much is: who changed the MCAS behavior after the FAA "saw" the first version? Someone decided this should happen, and someone implemented it (perhaps the same person). Forget the C-suite for a moment; someone in middle management made this call. Shouldn't they answer for it?