Experience and good learnings from past.
-
Be familiar with the product, ask for quota/env to use it like the customer, learn the customers experience.
-
Need to understand why we need the feature, not in a hurry to jump into the implementation.
-
External dependencies are always risks.
-
Different levels of test are necessary: unit test, functional test, integration test, e2e test and UAT, CUJ test(if it is customer facing product).
-
Considering hare weekly status on your projects with manager/skip manager, so they know what you are working on.
-
Be more proactive/leadership, such as meeting driving to make progress, action items figure out, and confirm the stakeholders understand the role before your absence.
-
Always note down meeting summary and share with stakeholders, link to calendar tab.
-
Know what is going on around you, set bi-weekly sync up with colleagues to understand what are they working on, this could inspire you to get solution on your projects.
-
Always consider buffers on project timeline.
-
Document your projects’ progress, as detailed as possible: time, context, screenshot, link, what have done so far, TODOs. This can help you be better at multitasking.
-
Domain knowledge sharing, contribute to team tech talks.
-
Use engineer survival guide suggestions and staff engineer path.