System Design Bar ⬆️ Internally in Amazon

I joined Amazon in 2018 as SDE2 and I was blown away after seeing how SDEs are supposed to document their design in 1-pager and 6-pagers. At first it looked an over kill to me. Then after writing a COE (Correction of error) for an outage. I started loving documenting my work. Today I am a SDE3 with good documentation skill and way better communication skill then my peers(sde2 equivalent in Google/Microsoft/Apple/Uber). Love Amazon's Internal System Design Bar. Well here is the SOP for any external SDE2: 1. Setup a 30min meeting with your SDE3/TPM/PM to gather requirements. 2. Divedeep and your document your finding in bullet points. 3. Share it with your SDE3/TPM/PM and ask for open questions over Quip. 4. Setup another 30min follow-up requirement gathering session. 5. Do a whiteboarding with your peer SDE. 6. Ask for 1-pager/6-pager template from your team. 7. Follow the format and start writing. 8. Share for internal team feedback and gather comments. 9. Share the revised version for internal team feedback. 10. Setup a review with dependent team for feedback. 11. If blast radius can impact whole org then setup a review with PE. 12. Add implementation timeline and share with SDM. 13. Start implementing and mark milestones. 14. Add testing details + CR links. 15. If required put a user guid for reference. Thanks, A satisfied engineer TC-1.1cr Yoe-8