SWE Onboarding
by Parker · 12 things on Twos
- Take informed risks. Seek to learn "why"
- Things to do: code/unit test (always together), review others code, ensure your code was reviewed, end to end aka system testing (sometimes), deploy, monitor, support, design next round of code
- We write unit tests so when people change our code in the future, our tests will fail if their changes break something
- Ask manager: 1. What will I be doing here? 2. What does my group do?
- Design docs are necessary for any work. Write the design doc. Get feedback on it. Use it to explain and for promotion
- Managers are responsible for administration, advocacy, coaching, and leading by example
- Go/manager-definition
- Tech leads (TL) are responsible for setting the technical direction, coordinating resources, engineering representative
- Product Manager (PM) responsible for responsible for determining overall direction of product, prioritizing features, point of contact for others on the core team
- Program manager (PgM) responsible for working closely with engineers and may be technical (TPM), developing requirements and plans, manage implementation and deployment
- Mentor: responsible for guidance and feedback, sharing resources, cultural torchbearer
- go/flebron-swe-onboarding