You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A brief introduction to the background context behind the current problem's situation:
Why is this problem worth solving?
To determine the relative priority of this problem in contrast to that of many others, ask: What goes wrong if this remains unfixed after a finite amount of time?
How was this problem discovered?
Tracking trends of problem discovery sources helps us focus our efforts more precisely
Who is affected by this problem, and what workarounds are available to them at the time of writing?
Depending on the relative seniority of the level you’re hired at, and the company age/leadership experience, you may be called on to define answers to some of the questions below. Tread accordingly.
Information checklist
Culture
What separates great from good performance?
What might be the largest difference between two different engineering teams here?
What would be the biggest piece of advice all of you have for me?
What are the most common challenges faced by new team members here?
Which actions make new team members reach full productivity in weeks as opposed to months?
Are there any recent cultural changes I should be aware of?