Growth
Your yearly story in one view — and an honest read on what is still missing.
My growth this year
Toggle any signal to compare trajectories.
Quarterly performance
Trajectory, consistency and best quarter.
QoQ improvement
+10.5%
Best quarter
Q3 · 84
Weakest quarter
Q1 · 68
Consistency
High
Q4 has not happened yet — no score is projected for it.
Technical depth tracker
Where depth is actually demonstrated.
Recommendation: architecture is your thinnest area. One design document on an existing responsibility would move it most.
Performance point system
Configurable model — not your company's official score.
21 evidence · trend +4 · Keep linking PRs and deployments to each delivery item.
9 evidence · trend +6 · Own one ambiguous, undefined problem this month.
11 evidence · trend +3 · Add a system-design or architecture artefact.
14 evidence · trend +2 · Record who else was involved so ownership is unambiguous.
6 evidence · trend +4 · Quantify one improvement with a before/after number.
12 evidence · trend +3 · Capture root cause for every investigation.
7 evidence · trend +5 · Log preventive actions and monitoring added.
4 evidence · trend +7 · Measure engineering hours saved per automation.
10 evidence · trend +1 · Record cross-team outcomes, not just meetings.
5 evidence · trend +2 · Log one self-initiated improvement per month.
3 evidence · trend +3 · Lead a design review or mentor on one problem.
6 evidence · trend +2 · Log what you learned on complex items.
8 evidence · trend +8 · Record explicit help requests from other engineers.
Overall performance points: 79/100
Go-to person signal
Counted from recorded evidence only.
- 4 complex issues resolved independently
- 2 RCAs documented
- 1 troubleshooting guide published
- 0 explicitly recorded help requests
To improve: record when engineers route issues to you, and run one knowledge-sharing session. Completing many tasks alone does not make you a go-to person.
What is stopping me from 5/5?
Technical Depth
- Why it matters:
- A top rating expects depth on problems no one has scoped for you.
- Recommended action:
- Own one architecture or performance problem end-to-end this quarter.
- Evidence to collect:
- Design document, benchmark before/after, RCA
- Success metric:
- 1 design doc + 1 measurable improvement
- Target date:
- 30 Sep 2026
Ambiguous Problem Ownership
- Why it matters:
- Most of your owned work was already well-defined.
- Recommended action:
- Take the next unowned production pattern and drive it to closure.
- Evidence to collect:
- Investigation notes, monitoring added, recurrence prevented
- Success metric:
- 1 ambiguous problem closed
- Target date:
- 15 Sep 2026
Go-To Person
- Why it matters:
- Manager feedback explicitly asked for this.
- Recommended action:
- Publish troubleshooting docs and record when engineers route issues to you.
- Evidence to collect:
- Docs, help requests, knowledge-sharing session
- Success metric:
- 3 recorded help requests + 1 session
- Target date:
- 30 Sep 2026
Quantified Business Impact
- Why it matters:
- Impact areas are identified but rarely quantified.
- Recommended action:
- Attach one number to each significant fix or optimisation.
- Evidence to collect:
- Dashboards, error rates, volumes, hours saved
- Success metric:
- 80% of major items quantified
- Target date:
- Ongoing