Clarify developer's position responsibilities
Currently, at https://about.gitlab.com/positions/developer/, we have some responsibility items that could be improved/combined, e.g.:
Intermediate | Senior | Proposal |
---|---|---|
Qualify developers for hiring | Helps with recruiting | Keep only the one in the Senior list |
Begins to show architectural perspective | Drop the "Begins to" | |
Review merge requests from your coworkers + Manage and review code contributed by the rest of the community and work with them to get it ready for production | Provides thorough and timely code feedback for peers + Helps guide other merge requests to completion | We might want to combine some items and make the Senior ones more distinct from the Intermediate ones |
Excellent at writing production-ready code with little assistance + Able to write complex code that can scale with a significant number of users | Combine them into a single item |
What do you think @stanhu @edjdev @ayufan @DouweM @smcgivern?