Hi Taro folks,
I’d like to create a doc to track my deliverables across engineering axes to make my work easier to see for my manager. This should also help with arguing for promotions down the road… does anyone have a good format for such a doc? FYI: engineering axes include project impact, people, direction, engineering excellence, etc.
Here's what I did:
@Rahul Just curious. ".. the 4 engineering axes for Meta.." which are these?
As mentioned in the original post, the 4 engineering axes for Meta SWEs are as follows:
If you're interested in exactly what these axes mean, check out our in-depth guide to Meta performance review here: https://www.promotions.fyi/company/meta/performance-review
I feel like maintaining a brag journal that's split up across the 4 Meta performance axes for engineers is overkill: It's true that it would be nice to have this pre-processing done prior to PSC to make self-review easier, but the cognitive load seems high.
For example, let's say you add "Delivered an internal tool that helped 15 engineers" to your doc. How would you split it across the 4 axes? How would you prevent double-dipping across axes? It's just too much IMHO, especially for an E4.
I actually didn't maintain a structured brag journal at all at Meta; instead, I mainly logged my accomplishments across 2 existing and more natural avenues, which I'll detail here.
Sharing your wins (and trying to get praise to keep your mental state positive) is an important part of that "awkward" 1 on 1 experience, which we talk about in-depth here: 1 on 1s Are The Time To Be Awkward
Here's a bunch of resources about Workplace and how to write awesome posts:
I lean on the side of having a rough idea of what progress looks like and how it's measured (e.g. OKRs) and keeping a running journal of things that are worth noting down. I like Alex's suggestion regarding putting "tags" so they become easier to find later. The point of not only relying on your BRAG doc and publishing your accomplishments / presenting wins & milestones achieved during townhalls, quarterly events, packaging it into a training/documentation for others to consume, and writing up a case study should all be in your arsenal.
Having a habit of collecting a quick testimonial when you've had a positive impact on others is very powerful as well (I've forgotten many times in the past). This has the added benefit of preventing a mad scramble at year-end to collect 360 feedback. Overall, social proof is extremely important since a written narrative will only get you so far during calibrations.