How to put down accomplishments on my resume as a senior engineer?

Team development and engineering excellence on your resume, or should I not mention them at all?

Can you expand exactly on what these mean? I'm also a bit confused as you mentioned daily activities (like leading stand ups?), and I agree that you can't really mention that.

When it comes to team development, I immediately think of mentorship. There are a couple of angles you can mention here:

1. The number of engineers you mentored
2. The growth they achieved, particularly with promotion speed. I was able to get engineers promoted at Meta 2x faster than company average, and I mentored E3/E4/E5s. This is something quite tangible that shows that you're a strong mentor (instead of telling)

When it comes to engineering excellence, I'm thinking more along the lines of commits landed/reviewed and the quality of that. This is hard to capture on a resume unless you have something concrete like "I was a Top 5% code committer in my organization". My code quality course dives into that: https://www.jointaro.com/course/level-up-your-code-quality-as-a-software-engineer/how-this-course-works/

Annual awards given? Again, should I even mention that?

I actually think this is fine, but you should mention the context of the award (i.e. what does it mean). A lot of awards have in-house terminology. Let's say you got the "Excelsior" award, something a recruiter won't understand upon reading it:

1. What do you need to do to get the award? Ship high-quality code? Deliver impact? Mentor others?
2. How often is the award given?
3. How many people in your organization get the award each cycle?

Here's more resources on resume optimization: [Taro Top 10] How To Write A Better Engineering Resume To Get More Jobs

Edited the question and added pointers.

For the mentorship, you can show the metrics I mentioned before. If you want to get even better at mentorship, I recommend this: [Taro Top 10] Effective Mentorship And Growing Others

For engineering excellence, you can mention the unit tests and DB migration:

• For unit tests, try to understand the impact, primarily with bugs/regressions prevented. A good testing effort should come with that understanding as I talk about here: "What do mobile testing strategies look like at top tech companies?"
• For DB migration, you can describe the complexity reduction (I assume the previous process was very manual) alongside stability improvements (botched DB migrations is one of the most common ways to break production)

Document-first culture is interesting, but I can't come up with good numbers for it minus pages of documentation created. I would just further explain what it is on your resume and exactly how it made the sharing of knowledge easier.

For the award, I personally don't think 1 in 6 will look too impressive to a recruiter, but you can still add it if you want. I don't think it will hurt.