Marcus Bell
Online sixty hours a week, in every meeting, a comment on every document. Projects unclear.
- Level
- Senior Engineer
- Tenure
- 4 years
The numbers
One quarter, from the dashboards, as they reach the room.
| Tickets closed | 29 |
|---|---|
| Pull requests merged | 15 |
| Incidents handled | 1 |
| Status active, hours a week | 61 |
| Meetings attended | 100% |
| Document comments | 143 |
| Posts in team channels | 140 |
| Direct messages sent | 75 |
Self-review#
I maintained full engagement across all cross-functional forums this quarter, attending every team and division meeting and contributing review comments on 143 design and planning documents to keep the team’s thinking aligned. I provided continuous availability to colleagues across time zones, including out-of-hours support. I delivered 29 tickets on the payments surface and handled one incident in March. My priority has been to be a present, reliable senior voice for the team during a period of change.
Peer feedback#
From Daniel Cho, nominated by Marcus. Marcus is always there. Whatever time you post, he has seen it, and he usually has a comment. In a quarter with a reorg in it, that kind of steadiness matters.
From Aisha Rahman, assigned. Marcus left 31 comments on the Deploy Platform v2 design document. I went back and counted: 24 were typo fixes or “great point”, 5 were questions answered in the paragraph above, and 2 were useful. He was in every one of my meetings and I cannot recall him deciding anything in any of them.
What the last manager left#
- First in, last out, judging by the status dot.
- Replied to my message on a Sunday. Did not ask him to.
- Genuinely not sure what his projects were this quarter. Check the tickets.
The announcement#
None this quarter.
Where they sit#
Reports to your line. Senior, four years, no system of his own. On every meeting invite the team has. The one incident he handled in March was resolved by Tom on the same call.