Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>are almost completely arbitrary? What constitutes a "senior", "lead", "principal" and "staff" X, respectively, has so much overlap that it really depends on the organisation

Titles at least useful to understand the hierarchy, but roles truly mean nothing. Sometimes the adult in the room is a PO, sometimes it's EM, sometimes they are responsible for the timelines and "project stuff", sometimes it's a Senior Engineer. In some places a QA is effectively doing PO stuff.



> In some places a QA is effectively doing PO stuff.

Or your support team could wind up owning it without even knowing that they own it.

Plan for who's gonna own the product because someone will, and that task will just settle somewhere random if you don't specifically assign it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: