Ask HN: Use KPIs in an Early Startup?

I just saw a software engineering job post for an early startup that listed what the KPIs for the role would be. The KPIs seemed to be niche-specific correctness/reliability.

I'm a big fan of correctness and reliability, but was surprised by KPIs. I'd expect everyone to be thinking holistically about the mission, like, well, an early startup. Not focused on big-company dynamics, like rigid compartmentalization, individual performance evaluations, optimizing for performance metrics, etc.

For any early startups that have done engineering KPIs, how did that work out for you? (Did you end up using them as the basis for performance evaluation? Did people focus on their KPIs? Was there strong alignment of ICs with the startup mission, or did it feel a bit like playing to evaluations in a big company? Were you seeing holistic thinking, and creative solutions across roles?)