https://careers.google.com/how-we-hire/#step-self-reflection
https://about.google/philosophy/
(- Generally better to choose a story that’s more recent). (- Good to point out how you improved out of this).
(+ Improving Wiki Notes). (- Probably better to quantify it).
(+ How did you work extra in the same time frame?) (- Working extra/on the weekends + long days isn’t that great). (+ Probably better to be clearer on tasks/description).
(+ Probably better to point out some takeaways, it’s important to spread and delegate the work + grow the team).
(+ Ask questions for why the project is slipping, and create a process to keep stakeholders in the loop.)
(+ Good to ask a clarifying question) (- Is it a management question? Accessibility is important for all sites). (- I would say that we should require accessibility, we understand the requirements of our users).
(+ Left a faulty certificate on a staging server). (+ Had to leave a lot of tickets open which counts against our team). (+ What would happen if something major happened which was customer facing)? (- I think its bad to mention that staging/dev should be broken, since it helps to debug some more important issues). (+ Communicate + prioritize).
(+ Teaching a coworker about testing better instead of doing a brute force solution). (- Probably better to have a stronger story).
(+ Why are old web components bad? Why is server-side rendered bad? We weren’t familiar with the codebase isn’t a great reason.) (+ Highlighting wins that happened from using a more familiar web framework). (- Would like more detail about quantifying it).
(+ Infinitely loading loop). (+ Adding error handling + error pages, + better accessibility for our users). (+ Analytics would be useful to tell a story).