QA framework

Starting to understand the technical, business, and UX story behind software development. Gets incredibly excited each time a new bug is found. Usually works in tandem with a mentor, especially at the beginning. Tests web and mobile apps, works on test docs, and joins all project processes.

Can hold their ground on larger projects. Their technical skills should allow them to test APIs, fully support devs during debugging, and debate technical decisions to a certain degree. Happy about new bugs but wants to understand why they happened. Can work completely independently or in a team. Maintaining the board, collaborating with other teams, and improving processes become important aspects of the job.

Has multiple large projects under their belt. Can autonomously coordinate all testing activities. Gets suspicious when too many bugs are found and wants to implement processes that would prevent some of them. Can mentor and organize a team of several testers on a project. Should be deeply involved in decision-making on the project.

Wants to make an impact on quality via test automation and is starting to figure out the programming languages, tools, and processes around it. Gets incredibly excited when the tests find a bug instead of a false positive. Usually works in tandem with a mentor, especially at the beginning. Mostly writes UI tests for web and mobile apps, but is still fully involved in the project.

Can develop testing strategies for large projects and use the right tools to implement them. Gets angry at false positives and wants to eliminate them immediately. Can mentor and organize a team of several Test Automation Engineers on a project. Technically proficient enough to be able to contribute beyond their own test code.

Has honed their testing and organizational skills to an impressive degree. Gets excited when new colleagues find a nasty bug. Mentors several people and helps them find their way on projects. Should be responsible for the quality of delivery along with software engineering leads and other project members.

Has worked on multiple large projects and worked on building teams of automation engineers. Gets excited when new colleagues deploy their first tests. Mentors several people and helps them find their way on projects. Should be responsible for the quality of delivery along with software engineering leads and other project members.

Manages between 4 and 6 people. This is considered a subteam if part of a larger team that multiple TLs are managing. Still performs hands-on work. Focuses on individuals and their careers. Has a good overview/ownership of the projects that their directs are working on. The entry-level position for the management track; the position has a lot of new ground to cover. It is expected that one moves from this position to TL2 within 12-18 months. Senior-level technical expertise, but not necessarily the most senior person in the team.

Manages between 4 and 15 people. This is considered a subteam if part of a larger team that multiple TLs are managing. Still performs hands-on work if managing less than 12 people. Has grown accustomed to the management role and is efficient in all aspects needed for their team/subteam.

Has significant experience managing people. Recognized for developing expert Individual Contributors. Mentors other Team Leads in the team. Pushes cross-team initiatives, i.e. not focused on just their team. Recognized by other Team Leads for their leadership skills. Very efficient at removing blockers.

Manages Team Leads and Technical Leads. Responsible for one entire team. Develops careers for all tracks in a team with experience and ease. Implements best practices from other teams. Has a good overview of all strategic projects in the team. Recognized for technical excellence but also high leadership capacity.