1 | Key Area | Attribute / Value | Competency | ||||
---|---|---|---|---|---|---|---|
2 | Associate [Role] DR1 | Mid-Level [Role] DR2 | Senior [Role] DR3 | Principal [Role] DR4 | |||
3 | Scope & Impact | within task | within project + community | within team + community | across several teams + communities | ||
4 | Functional Skills How knowledgeable are you in your particular focus area, with regard to the product/ project/ program as well as the other stakeholders? | Product Knowledge | Is aware of the overall architecture of the product(s), project(s), or program(s) they're responsible for. Quickly learns who the appropriate stakeholders are throughout the company for their particular product(s), project(s), or program(s) . | Is aware of the overall architecture of the product(s), project(s), or program(s) they're responsible for and has a good working relationship with the appropriate stakeholders for their particular product(s), project(s), or program(s). | Is the "go to" person for at least one product, project, or program within the company and/or the community, bridging the gap between departments and disseminating knowledge among teammates and the community with empathy and professionalism. | Is the "go to" person for multiple products, projects, or programs within the company and/or the community, bridging the gap between departments and disseminating knowledge among teammates and the community with empathy and professionalism. | |
5 | Feedback | Quickly learns how to source feedback from the community and/or coworkers. | Is able to source and evaluate feedback about a particular product, project, or program from the community and/or coworkers, and with some assistance, can present this feedback to various stakeholders in a clear and concise manner that exhibits its business value. | Is able to source and evaluate feedback about a particular product, project, or program from the community and/or coworkers and present this feedback to various stakeholders in a clear and concise manner that exhibits its business value. | DR3 + when asked for feedback about specific products, projects, or programs, is able to quickly identify key people who can provide said feedback. | ||
6 | Delivery Are you able to deliver topics of an appropriate level of complexity in an autonomous way? | Implementation | As DRI, implements already-scoped topics of linear complexity, meeting delivery expections. | As DRI, consistently scopes and implements topics of linear and structural complexity, meeting delivery expectations. | As DRI, consistently scopes and implements topics of linear, structural, and foundational complexity, meeting delivery expectations. | DR3 + efficiently supports members of own and other teams to implement the most challenging of topics, including structural and foundational complexity. | |
7 | Transparency | Makes progress transparent on a daily basis, clearly communicating achievements, goals, and impediments. Autonomously escalates in a timely manner when stuck and in need of help from more senior teammates. Documents decisions and makes impacted parties aware in a timely manner. | DR1 + proactively clarifies expectations and commits to a realistic amount of work. | DR2 | DR2 | ||
8 | Teamwork Do you know how and when to ask for and offer assistance? Are you able to clearly communicate decisions and status updates? | Communication | Understands the importance of communication in written and verbal form and actively works to improve their written and verbal communication skills. Looks to senior teammates for recommendations on professional development opportunities. | Able to effectively communicate with non-DevRel roles and functions within the company. Actively pursues and seeks to implement feedback that will help improve written and verbal communication skills. | DR2 + actively seeks opportunities to demonstrate these verbal and/or written communication skills inside the company as well as in the broader technical community. | DR3 + actively trains others in written and verbal communication skill development. | |
9 | Collaboration | When requested, helps their teammates overcome relevant obstacles of linear complexity. | When requested, helps their teammates and coworkers overcome relevant obstacles of linear or structural complexity. Documents decisions and makes impacted parties aware in a timely manner. | Is able to help teammates and coworkers overcome relevant obstacles of any complexity and proactively seeks opportunities to do so. Actively seeks commitment from other departments for specific tasks. Documents decisions and makes impacted parties aware in a timely manner. | DR3 | ||
10 | Leadership How are you using your influence, both internally at Camunda and also in the broader technical community? | Mentoring | Accepts mentorship to grow their own experience. | Actively works to improve in areas where they receive feedback and sometimes mentors their teammates. | Actively works to improve in areas where they receive feedback and regularly mentors their teammates or community members. | DR3 + mentors DevRel professionals from other companies. | |
11 | Empathy | Expresses a desire to represent the company as well as the community with respect and compassion. Quickly learns the difference between a one-on-one conversation with a trusted coworker or community member and a public statement (whether online or in person) that could undermine either the company or the community. | Actively represents the company as well as the community with respect and compassion. Knows the difference between a one-on-one conversation with a trusted coworker or community member and a public statement (whether online or in person) that could undermine either the company or the community. | DR2 + efficiently supports members of own or other teams to navigate challenging situations within the company or community, providing clarity and perspective that brings stability to the situation at hand. | DR3 + efficiently supports members of the broader technical community to navigate challenging situations, providing clarity and perspective that brings stability to the situation at hand. | ||
12 | Influence | Actively engages with their coworkers and/or technical community, building and fostering relationships with relevant parties. | DR1 + actively engages with other teams at Camunda, communicating feedback | DR1 + proactively seeks opportunities to collaborate with other companies on projects that will help the larger tech community. | DR1 + is often sought after to collaborate with other companies on projects that will help the larger tech community. |
1 | DR1 Summary | ||||||
---|---|---|---|---|---|---|---|
2 | DR1 | ⟶ | DR2 | ⟶ | DR3 | ⟶ | DR4 |
3 | |||||||
4 | |||||||
5 | Associate [Role] | Mid-Level [Role] | Senior [Role] | Principal [Role] | |||
6 | |||||||
7 | |||||||
8 | Profile | Often a graduate starting their professional career. | |||||
9 | Expected years in level | Typically Developer Relations professionals will stay in this level for 1-2 years and then get promoted to the next level (assuming required talent and ambition). | |||||
10 | Overview | Solves scoped problems | |||||
11 | Functional Skills | Quickly works to become knowledgeable about their specific focus area and begins to build successful relationships with stakeholders. | |||||
12 | Delivery | Quickly learns how to work on topics of linear complexity and delivering them in an autonomous way. | |||||
13 | Teamwork | Quickly learns how to ask for help, document decisions, make impacted parties aware and help others when asked. | |||||
14 | Leadership | Quickly learns what's expected of them and actively seeks opportunities to grow their skills as well as relationships. | |||||
15 | |||||||
16 | DR1 Specifics |
1 | DR2 Summary | ||||||
---|---|---|---|---|---|---|---|
2 | DR1 | ⟶ | DR2 | ⟶ | DR3 | ⟶ | DR4 |
3 | |||||||
4 | |||||||
5 | Associate [Role] | Mid-Level [Role] | Senior [Role] | Principal [Role] | |||
6 | |||||||
7 | |||||||
8 | Profile | Usually a professional that is 2-3 years into their career. | |||||
9 | Expected years in level | Typically Developer Relations professionals will stay in this level for 1-3 years and then get promoted to the next level (assuming required talent and ambition). | |||||
10 | Overview | Contributes to projects without close supervision | |||||
11 | Functional Skills | Consistently works on topics of linear complexity and seeks mentorship on topics of structural complexity, relying on more senior members of the team for guidance and feedback. | |||||
12 | Delivery | Consistently delivers on all topics of linear complexity and interacts with more senior teammates in a way that allows them to work on topics of structural complexity in an increasingly autonomous way. | |||||
13 | Teamwork | Knows how to ask for help, clearly and effectively document decisions, make impacted parties aware, and help others when asked. | |||||
14 | Leadership | Represents the company and/or community in a way that garners respect from those around them and actively looks for ways to share their experience as well as learn from others. | |||||
15 | |||||||
16 | DR2 Specifics |
1 | DR3 Summary | ||||||
---|---|---|---|---|---|---|---|
2 | DR1 | ⟶ | DR2 | ⟶ | DR3 | ⟶ | DR4 |
3 | |||||||
4 | |||||||
5 | Associate [Role] | Mid-Level [Role] | Senior [Role] | Principal [Role] | |||
6 | |||||||
7 | |||||||
8 | Profile | Usually a professional that is at least 3 years into their career and has a minimum of 2 years experience in Developer Relations | |||||
9 | Expected years in level | Indefinitely - Many Developer Relations professionals will remain in this level for the remainder of their career | |||||
10 | Overview | Owns and defines projects from beginning to end | |||||
11 | Functional Skills | Is knowledgeable about their specific focus area and serves as a successful bridge between the community and/or various departments in one or more ways | |||||
12 | Delivery | Is able to consistently work on any topic within the general purview of the team in a highly autonomous way | |||||
13 | Teamwork | Can participate in any discussion that is necessary to scope and deliver topics including with people in non-DevRel roles. Proactively helps others (in the DevRel team as well as other departments) overcome obstacles. | |||||
14 | Leadership | Uses their influence internally as well as externally to foster a culture of collaboration and growth | |||||
15 | |||||||
16 | DR3 Specifics |
1 | DR4 Summary | ||||||
---|---|---|---|---|---|---|---|
2 | DR1 | ⟶ | DR2 | ⟶ | DR3 | ⟶ | DR4 |
3 | |||||||
4 | |||||||
5 | Associate [Role] | Mid-Level [Role] | Senior [Role] | Principal [Role] | |||
6 | |||||||
7 | |||||||
8 | Profile | Exceptionally talented Developer Relations professionals that have a significant sphere of influence, both internally at Camunda and externally among multiple technical communities. | |||||
9 | Expected years in level | Indefinitely - Most Developer Relations Professionals will not reach this level, nor are they expected to. | |||||
10 | Overview | Responsible for strategically important projects or top relationships (either by leading others or demonstrating extraordinary individual ownership) | |||||
11 | Functional Skills | Is able to consistently tackle and be the DRI for even the most complex topics within the general purview of the teams they work with. | |||||
12 | Delivery | Can consistently work across their own and other teams to enable the completion of the most challenging of tasks, yet works according to the process and does not think it beneath themselves to work on smaller topics as well. | |||||
13 | Teamwork | Can participate in any discussion that is necessary to scope and deliver topics including with people in non-DevRel roles. Proactively helps others (in the DevRel team as well as other departments) overcome obstacles. | |||||
14 | Leadership | Uses their influence and experience to impact the greater Developer Relations industry, bringing significant value to their coworkers as well as the DevRel community. | |||||
15 | |||||||
16 | DR4 Specifics |