Knowledge of datastore considerations and best practices within the organization

1. Study and learn existing architecture documents used by the team. Participate in an architecture design review of a new or improved feature or system and document the results of the review.
2. Know the basic principles of software architecture design used in the team.
3. Explain the architecture for the team's major systems. Successfully contribute to a design review for a new or improved feature or system.
4. Study and learn existing specifications for the team's systems. Participate in a team review of system specifications for a new or improved feature or system. Independently propose changes to these document as needed during development.
5. Know how to review and provide input to system specifications for features and systems developed by the team.
6. Refer to appropriate system specifications for different aspects of the team's systems. Be able to augment or create specifications for existing or new systems.
7. Understand some predominant datastores used by the team's systems. Investigate internal and external platforms for data storage used by other teams.
8. Know of the organization's best practices around datastore choices and costs and benefits of each. Know how to organize and optimize data for common operations.
9. Be able to recommend appropriate datastores for new features or systems for the team. Propose drafts for new schema or changes to existing schema.

Knowledge of how to review code contributions as part of a peer group

1. Study and learn the basic coding languages used by the organization to develop software. Understand common patterns, libraries and artifacts used to expedite quality code development. Use these tools to develop new or existing features and systems.
2. Know the coding languages, libraries and artifacts used by the organization for efficient software development.
3. Features and systems developed are accepted. When applicable, able to contribute new features to shared codebases as well.
4. Participate on a software team that develops a new or enhanced software systems and learn basic concepts and procedures for developing software. Write and document some code, and refactor some code for a part of a software system.
5. Know the basic software development process used by the organization. Know effective ways to write efficient and correct code that extends on best practices within the codebase.
6. Successful and active participation on a software development team including writing quality code that is well documented and testable.
7. Participate in review of code contributions as part of a peer group. Document the group's findings and recommendations for changes to or reworking of the code.
8. Know how to participate in peer code review. Know how to give and receive constructive feedback to iterate on working solutions.
9. Able to submit code for review with adequate context and address feedback. Able to give feedback to peers on quality of code,

Experience performing load testing and benchmarking on systems

1. Independently identify positive and negative test vectors for all code contributions. Collaborate with team as needed for more complex dependencies and side-effects. Create test plans for code contributions.
2. Know team's best practices around designing and writing manual and automated tests and process to validate code contributions with test coverage.
3. Test cases accepted by team after minimal peer review. No additional recommendations made by team.
4. Understand the team's integration and end-to-end testing best practices. Augment those test suites as appropriate when contributing code to relevant systems.
5. Know the team's integration and end-to-end testing best practices.
6. Additional tests are accepted by team after minimal peer code review.
7. Interpret requirements for load testing existing or new systems. Use organization's best practices to write, perform and interpret load tests.
8. Know capacity limits and known bottlenecks of team's systems. Know ways to detect and eliminate them when applicable.
9. Effectively document findings of load tests and ways to reproduce them as needed. Ability to identify and mitigate bottlenecks when applicable.

Knowledge of team and organizational incident response procedures

1. Study and learn the organization's process for releasing new features and bugfixes. Understand source code convergence and validation principles within and across teams. Independently release new versions of code for deployment.
2. Know how to develop a release plan for an application. Know how to coordinate between peers within and outside team to effectively release changes.
3. Independently release and validate new code after peer review and testing.
4. Understand deployment best practices and feature rollout strategies within the team. Understand organization-level safeguards and tools in place to assist with deployments.
5. Know deployment and rollout best practices, tools and processes within the team and across the organization.
6. Propose and execute code deployments after new versions have been released for use.
7. Understand the role of on-call engineers, managers and support specialists in mitigating customer impact during operational incidents. Shadow a team member for one rotation to assist with response where appropriate. Study documentation and procedures that dictate plans of action.
8. Know incident response best practices for the team and organization. Know relevant documents that detail incident response procedures.
9. Be able to effectively shadow an on-call engineer on a rotation. Be able to contribute to incident response and post-mortems.

Knowledge to effectively instrument metrics, logging and tracing for software systems

1. Complete relevant organizational and team-level security trainings. Incorporate learnings into design and development practices.
2. Know of any existing security vulnerabilities in team's systems and best practices to mitigate introducing new vectors for attack. Know organizational policies around data privacy and security.
3. Successful completion of security and compliance trainings an ability to incorporate security best practices into designs and code.
4. Understand the organization's best practices to achieve resilience by avoiding single-points-of-failure, applying appropriate load balancing and developing multi-tenant systems.
5. Knows organization best practices to avoid common failure modes and critical design flaws in design and development of new features and systems.
6. Able to design and develop systems defensively against common performance pitfalls and failure conditions. Code accepted bv team after peer review.
7. Understand the organization's best practices for instrumenting software systems with appropriate metrics, logging and request tracing. Apply this to generate new metrics, logs and traces as needed during development.
8. Know best practices, tools and dashboards to instrument the team's software systems.
9. Be able to effectively interpret a team's operational dashboards. Be able to augment them by creating new instrumentation as needed.