Staff Archetypes
Metadata
- Author: staffeng.com
- Full Title: Staff Archetypes
- Category: articles
- URL: https://staffeng.com/guides/staff-archetypes
Highlights
- Tech Leads are the most common Staff archetype and lead one team or a cluster of teams in their approach and execution. They're comfortable scoping complex tasks, coordinating their team towards solving them, and unblocking them along the way. Tech Leads often carry the team's context and maintain many of the essential cross-team and cross-functional relationships necessary for the team's success. They're a close partner to the team's product manager and the first person called when the roadmap needs to be shuffled. (View Highlight)
- Earlier in their career, they will have implemented their team's most complex technical projects, but at this point, they default to delegating such projects across the team. They do this both to grow their teammates and in acknowledgment that the team's impact grows as the Tech Lead's coding blocks shrink. (View Highlight)
- Note: Tech Leads
- Indeed, you'll find non-Staff engineers acting with the behaviors of every archetype. Being a Staff-engineer is not just a role. It's the intersection of the role, your behaviors, your impact, and the organization's recognition of all those things. (View Highlight)
- Architects are responsible for the success of a specific technical domain within their company, for example, the company's API design, frontend stack, storage strategy, or cloud infrastructure. For a domain to merit an Architect, it must be both complex and enduringly central to the company's success. (View Highlight)
- Influential architects dedicate their energy to maintaining an intimate understanding of the business' needs, their users' goals, and the relevant technical constraints. They use that insight to identify and advocate for effective approaches within their area of focus, and do it with organizational authority that they've earned by demonstrating consistently good judgment. (View Highlight)
- The Solver is a trusted agent of the organization who goes deep into knotty problems, continuing to work on them until they're resolved. Folks in this role are moved onto problems identified by organizational leadership as critical and either lacking a clear approach or with a high degree of execution risk. (View Highlight)
- The Right Hand is the least common of the archetypes, showing up as an organization reaches hundreds of engineers and is akin to operating as a senior organizational leader without direct managerial responsibilities. Rick Boone compared his role to the Hand of the King in Game of Thrones and Leo McGarry from The West Wing, operating with the borrowed authority of a senior leader. However, borrowing authority comes with the obligation of remaining deeply aligned with that leader's approach, beliefs, and values. (View Highlight)
- Right Hands often dive into a fire, edit the approach, delegate execution to the most appropriate team, and then pop over to the next fire elsewhere in the organization. The joy of these roles is that you only work on essential problems. The tragedy is that you're always on to the next issue by the time those problems are solved. (View Highlight)
Staff Archetypes
Metadata
- Author: staffeng.com
- Full Title: Staff Archetypes
- Category: articles
- URL: https://staffeng.com/guides/staff-archetypes
Highlights
- Tech Leads are the most common Staff archetype and lead one team or a cluster of teams in their approach and execution. They're comfortable scoping complex tasks, coordinating their team towards solving them, and unblocking them along the way. Tech Leads often carry the team's context and maintain many of the essential cross-team and cross-functional relationships necessary for the team's success. They're a close partner to the team's product manager and the first person called when the roadmap needs to be shuffled. (View Highlight)
- Earlier in their career, they will have implemented their team's most complex technical projects, but at this point, they default to delegating such projects across the team. They do this both to grow their teammates and in acknowledgment that the team's impact grows as the Tech Lead's coding blocks shrink. (View Highlight)
- Note: Tech Leads
- Indeed, you'll find non-Staff engineers acting with the behaviors of every archetype. Being a Staff-engineer is not just a role. It's the intersection of the role, your behaviors, your impact, and the organization's recognition of all those things. (View Highlight)
- Architects are responsible for the success of a specific technical domain within their company, for example, the company's API design, frontend stack, storage strategy, or cloud infrastructure. For a domain to merit an Architect, it must be both complex and enduringly central to the company's success. (View Highlight)
- Influential architects dedicate their energy to maintaining an intimate understanding of the business' needs, their users' goals, and the relevant technical constraints. They use that insight to identify and advocate for effective approaches within their area of focus, and do it with organizational authority that they've earned by demonstrating consistently good judgment. (View Highlight)
- The Solver is a trusted agent of the organization who goes deep into knotty problems, continuing to work on them until they're resolved. Folks in this role are moved onto problems identified by organizational leadership as critical and either lacking a clear approach or with a high degree of execution risk. (View Highlight)
- The Right Hand is the least common of the archetypes, showing up as an organization reaches hundreds of engineers and is akin to operating as a senior organizational leader without direct managerial responsibilities. Rick Boone compared his role to the Hand of the King in Game of Thrones and Leo McGarry from The West Wing, operating with the borrowed authority of a senior leader. However, borrowing authority comes with the obligation of remaining deeply aligned with that leader's approach, beliefs, and values. (View Highlight)
- Right Hands often dive into a fire, edit the approach, delegate execution to the most appropriate team, and then pop over to the next fire elsewhere in the organization. The joy of these roles is that you only work on essential problems. The tragedy is that you're always on to the next issue by the time those problems are solved. (View Highlight)
Staff Archetypes
Metadata
- Author: staffeng.com
- Full Title: Staff Archetypes
- Category: articles
- URL: https://staffeng.com/guides/staff-archetypes
Highlights
- Tech Leads are the most common Staff archetype and lead one team or a cluster of teams in their approach and execution. They're comfortable scoping complex tasks, coordinating their team towards solving them, and unblocking them along the way. Tech Leads often carry the team's context and maintain many of the essential cross-team and cross-functional relationships necessary for the team's success. They're a close partner to the team's product manager and the first person called when the roadmap needs to be shuffled. (View Highlight)
- Earlier in their career, they will have implemented their team's most complex technical projects, but at this point, they default to delegating such projects across the team. They do this both to grow their teammates and in acknowledgment that the team's impact grows as the Tech Lead's coding blocks shrink. (View Highlight)
- Note: Tech Leads
- Indeed, you'll find non-Staff engineers acting with the behaviors of every archetype. Being a Staff-engineer is not just a role. It's the intersection of the role, your behaviors, your impact, and the organization's recognition of all those things. (View Highlight)
- Architects are responsible for the success of a specific technical domain within their company, for example, the company's API design, frontend stack, storage strategy, or cloud infrastructure. For a domain to merit an Architect, it must be both complex and enduringly central to the company's success. (View Highlight)
- Influential architects dedicate their energy to maintaining an intimate understanding of the business' needs, their users' goals, and the relevant technical constraints. They use that insight to identify and advocate for effective approaches within their area of focus, and do it with organizational authority that they've earned by demonstrating consistently good judgment. (View Highlight)
- The Solver is a trusted agent of the organization who goes deep into knotty problems, continuing to work on them until they're resolved. Folks in this role are moved onto problems identified by organizational leadership as critical and either lacking a clear approach or with a high degree of execution risk. (View Highlight)
- The Right Hand is the least common of the archetypes, showing up as an organization reaches hundreds of engineers and is akin to operating as a senior organizational leader without direct managerial responsibilities. Rick Boone compared his role to the Hand of the King in Game of Thrones and Leo McGarry from The West Wing, operating with the borrowed authority of a senior leader. However, borrowing authority comes with the obligation of remaining deeply aligned with that leader's approach, beliefs, and values. (View Highlight)
- Right Hands often dive into a fire, edit the approach, delegate execution to the most appropriate team, and then pop over to the next fire elsewhere in the organization. The joy of these roles is that you only work on essential problems. The tragedy is that you're always on to the next issue by the time those problems are solved. (View Highlight)
Staff Archetypes
Metadata
- Author: staffeng.com
- Full Title: Staff Archetypes
- Category: articles
- URL: https://staffeng.com/guides/staff-archetypes
Highlights
- Tech Leads are the most common Staff archetype and lead one team or a cluster of teams in their approach and execution. They're comfortable scoping complex tasks, coordinating their team towards solving them, and unblocking them along the way. Tech Leads often carry the team's context and maintain many of the essential cross-team and cross-functional relationships necessary for the team's success. They're a close partner to the team's product manager and the first person called when the roadmap needs to be shuffled. (View Highlight)
- Earlier in their career, they will have implemented their team's most complex technical projects, but at this point, they default to delegating such projects across the team. They do this both to grow their teammates and in acknowledgment that the team's impact grows as the Tech Lead's coding blocks shrink. (View Highlight)
- Note: Tech Leads
- Indeed, you'll find non-Staff engineers acting with the behaviors of every archetype. Being a Staff-engineer is not just a role. It's the intersection of the role, your behaviors, your impact, and the organization's recognition of all those things. (View Highlight)
- Architects are responsible for the success of a specific technical domain within their company, for example, the company's API design, frontend stack, storage strategy, or cloud infrastructure. For a domain to merit an Architect, it must be both complex and enduringly central to the company's success. (View Highlight)
- Influential architects dedicate their energy to maintaining an intimate understanding of the business' needs, their users' goals, and the relevant technical constraints. They use that insight to identify and advocate for effective approaches within their area of focus, and do it with organizational authority that they've earned by demonstrating consistently good judgment. (View Highlight)
- The Solver is a trusted agent of the organization who goes deep into knotty problems, continuing to work on them until they're resolved. Folks in this role are moved onto problems identified by organizational leadership as critical and either lacking a clear approach or with a high degree of execution risk. (View Highlight)
- The Right Hand is the least common of the archetypes, showing up as an organization reaches hundreds of engineers and is akin to operating as a senior organizational leader without direct managerial responsibilities. Rick Boone compared his role to the Hand of the King in Game of Thrones and Leo McGarry from The West Wing, operating with the borrowed authority of a senior leader. However, borrowing authority comes with the obligation of remaining deeply aligned with that leader's approach, beliefs, and values. (View Highlight)
- Right Hands often dive into a fire, edit the approach, delegate execution to the most appropriate team, and then pop over to the next fire elsewhere in the organization. The joy of these roles is that you only work on essential problems. The tragedy is that you're always on to the next issue by the time those problems are solved. (View Highlight)
Staff Archetypes
Metadata
- Author: staffeng.com
- Full Title: Staff Archetypes
- Category: articles
- URL: https://staffeng.com/guides/staff-archetypes
Highlights
- Tech Leads are the most common Staff archetype and lead one team or a cluster of teams in their approach and execution. They're comfortable scoping complex tasks, coordinating their team towards solving them, and unblocking them along the way. Tech Leads often carry the team's context and maintain many of the essential cross-team and cross-functional relationships necessary for the team's success. They're a close partner to the team's product manager and the first person called when the roadmap needs to be shuffled. (View Highlight)
- Earlier in their career, they will have implemented their team's most complex technical projects, but at this point, they default to delegating such projects across the team. They do this both to grow their teammates and in acknowledgment that the team's impact grows as the Tech Lead's coding blocks shrink. (View Highlight)
- Note: Tech Leads
- Indeed, you'll find non-Staff engineers acting with the behaviors of every archetype. Being a Staff-engineer is not just a role. It's the intersection of the role, your behaviors, your impact, and the organization's recognition of all those things. (View Highlight)
- Architects are responsible for the success of a specific technical domain within their company, for example, the company's API design, frontend stack, storage strategy, or cloud infrastructure. For a domain to merit an Architect, it must be both complex and enduringly central to the company's success. (View Highlight)
- Influential architects dedicate their energy to maintaining an intimate understanding of the business' needs, their users' goals, and the relevant technical constraints. They use that insight to identify and advocate for effective approaches within their area of focus, and do it with organizational authority that they've earned by demonstrating consistently good judgment. (View Highlight)
- The Solver is a trusted agent of the organization who goes deep into knotty problems, continuing to work on them until they're resolved. Folks in this role are moved onto problems identified by organizational leadership as critical and either lacking a clear approach or with a high degree of execution risk. (View Highlight)
- The Right Hand is the least common of the archetypes, showing up as an organization reaches hundreds of engineers and is akin to operating as a senior organizational leader without direct managerial responsibilities. Rick Boone compared his role to the Hand of the King in Game of Thrones and Leo McGarry from The West Wing, operating with the borrowed authority of a senior leader. However, borrowing authority comes with the obligation of remaining deeply aligned with that leader's approach, beliefs, and values. (View Highlight)
- Right Hands often dive into a fire, edit the approach, delegate execution to the most appropriate team, and then pop over to the next fire elsewhere in the organization. The joy of these roles is that you only work on essential problems. The tragedy is that you're always on to the next issue by the time those problems are solved. (View Highlight)
Staff Archetypes
Metadata
- Author: staffeng.com
- Full Title: Staff Archetypes
- Category: articles
- URL: https://staffeng.com/guides/staff-archetypes
Highlights
- Tech Leads are the most common Staff archetype and lead one team or a cluster of teams in their approach and execution. They're comfortable scoping complex tasks, coordinating their team towards solving them, and unblocking them along the way. Tech Leads often carry the team's context and maintain many of the essential cross-team and cross-functional relationships necessary for the team's success. They're a close partner to the team's product manager and the first person called when the roadmap needs to be shuffled. (View Highlight)
- Earlier in their career, they will have implemented their team's most complex technical projects, but at this point, they default to delegating such projects across the team. They do this both to grow their teammates and in acknowledgment that the team's impact grows as the Tech Lead's coding blocks shrink. (View Highlight)
- Note: Tech Leads
- Indeed, you'll find non-Staff engineers acting with the behaviors of every archetype. Being a Staff-engineer is not just a role. It's the intersection of the role, your behaviors, your impact, and the organization's recognition of all those things. (View Highlight)
- Architects are responsible for the success of a specific technical domain within their company, for example, the company's API design, frontend stack, storage strategy, or cloud infrastructure. For a domain to merit an Architect, it must be both complex and enduringly central to the company's success. (View Highlight)
- Influential architects dedicate their energy to maintaining an intimate understanding of the business' needs, their users' goals, and the relevant technical constraints. They use that insight to identify and advocate for effective approaches within their area of focus, and do it with organizational authority that they've earned by demonstrating consistently good judgment. (View Highlight)
- The Solver is a trusted agent of the organization who goes deep into knotty problems, continuing to work on them until they're resolved. Folks in this role are moved onto problems identified by organizational leadership as critical and either lacking a clear approach or with a high degree of execution risk. (View Highlight)
- The Right Hand is the least common of the archetypes, showing up as an organization reaches hundreds of engineers and is akin to operating as a senior organizational leader without direct managerial responsibilities. Rick Boone compared his role to the Hand of the King in Game of Thrones and Leo McGarry from The West Wing, operating with the borrowed authority of a senior leader. However, borrowing authority comes with the obligation of remaining deeply aligned with that leader's approach, beliefs, and values. (View Highlight)
- Right Hands often dive into a fire, edit the approach, delegate execution to the most appropriate team, and then pop over to the next fire elsewhere in the organization. The joy of these roles is that you only work on essential problems. The tragedy is that you're always on to the next issue by the time those problems are solved. (View Highlight)
Staff Archetypes (Readwise)
Interactive graph
On this page
Staff Archetypes
Metadata
Highlights
Staff Archetypes
Metadata
Highlights
Staff Archetypes
Metadata
Highlights
Staff Archetypes
Metadata
Highlights
Staff Archetypes
Metadata
Highlights
Staff Archetypes
Metadata
Highlights