If so, that's the first takeaway here: A non-technical manager is a red flag that should not be ignored.
If so, that's the first takeaway here: A non-technical manager is a red flag that should not be ignored.
Between those two: I'll take the non skilled every time.
That's why you need IC tracks with Principal and above engineers, so that the person that _knows_ stuff is in charge of technical decision and the manager can be in charge of people problems / communications / strategy / scheduling, none of which strong technical people are particularly known to be good at.
Think about this, what good does having a SVP of a big company be an engineer that hasn't coded a line of code in 20+ years? These people probably don't even remember what it means to be a programmer.
I would much rather have a manager that is good at being a manager and doesn't know anything about coding, rather than a mediocre manager that also knows coding but they are not in the loop and think they knows better than me.
Bad managers are the red flag - update your heuristic accordingly.