| JetBrains - Chat Business Logic| group: editor extensions |
#### Responsibilites
#### Responsibilities
1. Simple Component Updates: The UI component group (group: duo chat) is responsible.
2. Complex Feature Integrations: The UI component group (group: duo chat) drives the integration, creating stubs for extension communication with dummy data. group: editor extensions supports the integration effort into IDE plugins.
@@ -46,7 +46,7 @@ The following members of other functional teams are our stable counterparts:
## Shared Responsibilities
The Global Search team shares responsibilites with the AI Framework team in the area of (RAG). Specifically, we will collaborate in the data preparation stage and information retrieval stage of the RAG process.
The Global Search team shares responsibilities with the AI Framework team in the area of (RAG). Specifically, we will collaborate in the data preparation stage and information retrieval stage of the RAG process.
## AI Context Infrastructure and Advanced Search data stores
@@ -195,7 +195,7 @@ If you still have more questions, feel free to ask for guidance in the
Yes, being on-call for incident management is considered `vital to position` for [expenses](/handbook/finance/expenses/) purposes.
### My direct report is serving as Incident Manager. What are my responsibilites as their manager?
### My direct report is serving as Incident Manager. What are my responsibilities as their manager?
Adding Incident Manager responsibilities to a direct report's role requires cooperation with their manager. The manager should support them when they are assigned Incident Manager duties, particularly
when shifts overlap with weekends. Please make sure Incident Managers are empowered to delegate, postpone or drop some responsibilities given these additional responsibilities.
@@ -28,7 +28,7 @@ description: "Job families are organized by function at GitLab and we use them t
Anyone can create or edit a job family, but generally it is the responsibility of the person who will manage the position or job family to kick off the approval process. They may enlist help from others as necessary. After a merge request is created for an existing or new job family, **the merge request must follow the approval flows below**:
1.**Your manager**: Your direct manager is responsible for clarifying the scope of responsibilities and level of roles, ensuring clear differentiation between levels, and checking responsibilities and requirements and ensuring the job family follows the template logic and **has all of the required areas**. Mangers should validate business need for the role with their direct manager. Any review after this should be quick so the manager is the gatekeeper.
1.**Talent Management**: Talent Management will review for job level expecations consistency with other similarly leveled roles across the organization, alignment to our [GitLab Job Frameworks](https://docs.google.com/spreadsheets/d/1FX4NBwF099uMBm7mGBtf1orIJZuHEjtiEa3jSbg9jJs/edit?gid=0#gid=0), and overall structure, then notify your People Business Partner (PBP).
1.**Talent Management**: Talent Management will review for job level expectations consistency with other similarly leveled roles across the organization, alignment to our [GitLab Job Frameworks](https://docs.google.com/spreadsheets/d/1FX4NBwF099uMBm7mGBtf1orIJZuHEjtiEa3jSbg9jJs/edit?gid=0#gid=0), and overall structure, then notify your People Business Partner (PBP).
1.**Your Department Head and People Business Partner**: Your Department Head (typically at the VP level) is responsible for confirming there is a business need for the role and will review department/division structure and levels in partnership with the aligned People Business Partner. If the role is being created due to headcount planning, please ensure your Talent Acquisition partner has visibility for recruiting purposes.
1.**Total Rewards**: The Total Rewards Team, `@gl-total-rewards`, is the final approver for job families on the merge request ensuring.:
