Key Results/Outcomes

This enablement lead is responsible for those fulfilling the following assignments (Tech Leadership domain):

• {{Back-end architect}}
• {{Front-end architect}}

ENGAGEMENT:

• The people taking on the assignments listed above, agree or strongly agree to the following statements:
  • I know how I’m being evaluated on these roles.
  • I receive actionable (meaning timely, frequent, specific, and observation-based) constructive feedback on my performance within the roles identified above.
  • I receive actionable (meaning timely, frequent, specific, and observation-based) recognition (public or private) on my performance within the roles identified above.
  • I believe I have the tools to meet or exceed the outcomes listed within the roles in question.
  • I believe I have the processes and environment to meet or exceed the outcomes listed within the roles in question.
  • I believe we are continuously improving in how we go about taking on these roles.
  • Note: This SHOULD have a direct impact on the NPS score of engineers (where they select 8+ on a 10-point scale to the question; “I’d recommend a friend come to work here”). However, given that full engagement is more inclusive than their primary roles, it doesn’t feel right to have that as a part of the measure of enablement leads.

Things you might deliver/do

• Though you won't be exclusively responsible for engineers having the best tools and processes to do their best work, you will be heavily relied upon to ensure this is happening.
• You'll search for the “multiplicative effect”: impact multiplied by the number of people
• You'll be proactive by identifying and coordinate meeting common needs across the engineering team such as standards and conventions, documentation, etc.
• You'll be reactive by helping coordinate solutions to problems you hear about from the team, such as on-call support being frustrating, or waiting on reviews taking too long.
• You'll contribute to continually iterating on and improving the Engineer Growth Framework

---

Success:

• You are responsible for setting the tone for how the software architecture is set up. This spans many concerns, such as;
  • Performance
  • Scalability
  • Security
  • Privacy
  • Reliability
  • Overall supportability.

AKA

• Architecture policy definition/enforcement officer