List of Expectation from Team Members - template

	A	B	C	D	E
1	Level	Expectation	Team member A	Team member B	C

2	Entry	Be able to present and discuss what they have done, and their progress.
3	Entry	Be interested in and perform learning and exploration of the tools they work with (Level up opportunity).
4	Entry	Be able to reproduce bugs and to fix UI layout issues.
5	Entry	Learn and practice clean code (Level up opportunity).
6	Entry	Manually test the flows / bug-fixes created by them (to have full accountability for commits).
7	Entry	Given heavy mentoring, execute tasks outside of their level (Level up opportunity).
8	Entry	Understand the CI/CD tools and flows, and with mentoring can deploy to production.
9	Entry	Contribute to code documentation and readability (by renaming or adding comments in unclear places. Level up opportunity).
10	Entry	Be able to improve after feedback (given constructive and specific feedback. Baseline).
11	Entry	Be able to ask for help when needed — use the team to deliver.
12	Entry	Review and understand code reviews of others.
13	Junior	Can plan and take responsibility for their own time.
14	Junior	Be able to solve a bug from production (reproduce from report, investigate, fix and deploy).
15	Junior	Write unit tests, given the framework is in place (Level up opportunity).
16	Junior	Share knowledge — by writing in a channel, giving an internal talk, recording a short video, writing a blog post (Level up condition).
17	Junior	Communicate about status of tasks daily.
18	Junior	Attend tech meet-ups and forums (Level up opportunity).
19	Junior	Understand the team members’ updates in the stand-ups and if not — follow-up offline and make sure to understand in high level.
20	Junior	Understand the time expectations, raise flags about blockers or delays daily.
21	Junior	Estimate tasks by time that takes me to fulfil (e.g. 1.5 days). Not including breaking a story to tasks. The precision isn’t important, rather engaging in estimating and improving over time.
22	Junior	Engage with their personal growth plan (identify with help what are areas of improvements and work towards it).
23	Junior	Assists in setting up CI/CD (Level up opportunity).
24	Junior	Pair or Mob with more experienced colleagues (Level up opportunity).
25	Junior	Be able to maintain (as a single developer, but with mentoring) a small project after it’s been released to production (Level up opportunity).
26	Junior	Participate in the documentation of the solution, such as repository README, process descriptions and system descriptions.
27	Junior	Perform code review — according to the team’s review guidelines.
28	Junior	Be proactive in making sure they get enough code reviews.
29	Mid	Can deal with reasonable context switches.	3	2
30	Mid	Implement a story (incl. breaking the story to tasks and estimate).	3	2
31	Mid	Has good grasp of implications of architecture decisions (Level up opportunity).	2	3
32	Mid	Complete devOps tasks related to their features: adding monitors, modifying CI/CD pipelines, changing DB backup.	1	2
33	Mid	Can execute tasks independently (incl. asking for suggestions from the team when needed).
34	Mid	Be familiar with best practices, like design patterns. Know to identify them in the code and use them when writing new code.
35	Mid	Assist in system architecture design (Level up opportunity).
36	Mid	Be a source of information to the team in (at least) one subject (one library, one practice, etc).
37	Mid	Setup tests framework and write tests with little to no mentoring.
38	Mid	Lead Pair or Mob programming sessions with more junior developers (I disagree with this one being in a mid level, I think it should be in senior. Level up opportunity).
39	Mid	Coaching of junior developers.
40	Mid	Can setup a development environment on their own (level up condition).
41	Mid	Can refactor code modules for readability and maintainability.
42	Mid	Perform code review to others.
43	Mid	Understand the full lifecycle of an application.
44	Senior	Can design a software solution from scratch within their field.
45	Senior	Can implement CI/CD Tooling incl. selection and setup of infrastructure.
46	Senior	Be accountable for readability, scalability and maintainability for a platform in a project.
47	Senior	Choose a stack for a project after research and consideration with their team.
48	Senior	Mentoring mid and junior developers.
49	Senior	Tests: choose stack, decide what should be tested.
50	Senior	Have knowledge of modern software architecture patterns and can work with them within their field.
51	Senior	Can capture requirements and discuss implementation details externally and internally.
52	Senior	Be active in the API specs (contracts) creation (both ends).
53	Senior	Analysis of complex bugs within their domain.
54	Senior	Can think about the software solution in general outside the scope of their tasks.
55	Senior	Define code reviews standards.
56	Senior	Keen to learn new technologies, follow trends and incorporate best practice (baseline).
57	Senior	Will feed into the devOps tasks and be familiar with the internal model.
58	Senior	Be able to research and present a solution for an identified business or technical problem.
59	Senior	Understand the whole stack used in the projects (level up opportunity).
60	Senior	Has an eye for possibilities and knows how to meet the needs of the clients.
61	Senior	Accountable for the documentation of the solution, such as repository README, process descriptions and system descriptions.
62	Tech lead	Giving internal educational and inspirational talks.
63	Tech lead	Advising on growth plans.
64	Tech lead	Be involved in the community of their domains in Stockholm/online.
65	Tech lead	Radiate knowledge internally & externally.
66	Tech lead	Involved in interview process and sit in on interviews.
67	Tech lead	Give directions and recommendations on integrations with client systems.
68	Tech lead	Build own and team understanding of the client, their business model and users.
69	Tech lead	Thinking and communicating about the challenges we will face in the next 6 to 12 months in their domain.
70	Tech lead	Advise about reducing complexity in projects, services, systems and processes from their domain point of view.
71	Tech lead	Design system architectures with good UX, information design, scalability and security that are cost efficient for the client.
72	Tech lead	Domain knowledge on platforms/frameworks.
73	Tech lead	Be responsible for the tech radar in their domain, and communicating about it.
74	Tech Director (manager path)	Defining and follow up on our coding practices in projects.
75	Tech Director (manager path)	Define and lead solution and system architecture practices.
76	Tech Director (manager path)	Attend and contribute in external technical forums in used areas.
77	Tech Director (manager path)	Ability to understand clients business and factor this understanding into solutions.
78	Tech Director (manager path)	Part of defining the dept. strategy — culture, stack, etc.
79	Tech Director (manager path)	Create trust relationship with the client and cultivate a close relationship with tech people of the client.
80	Tech Director (manager path)	Remove technology blockers from the team.
81	Tech Director (manager path)	Identify cases of being bottle necks and change the structure to fix them.
82	Tech Director (manager path)	Mentor team members according to their growth plan.
83	Tech Director (manager path)	Work on the team dynamic to maximise abilities, growth, collaboration and innovation.
84	Tech Director (manager path)	1:1s with tech team members.
85	Tech Director (manager path)	Work with design and biz directors to achieve the goals for that studio.
86	Tech Director (manager path)	Resolve conflicts in the team.
87	Tech Director (manager path)	Strategic advisory towards the client.
88	Tech Director (manager path)	Maintain a constructive feedback culture.
89	Tech Director (manager path)	Support in building a culture of a community.
90
91
92
93
94
95
96
97
98
99
100