You've just joined a small, high-ownership engineering team building a core product used by thousands of users every day.
Over the last week, people keep saying "the product feels slow and flaky," but nobody owns this part of the system and there's no clear root cause. Metrics exist, but they're noisy, and no one has had time to dig in.
Record a video walking us through how you'd approach this situation and what it says about how you work.
Demonstrate structured debugging and diagnostic approach
Show ownership and bias to action
Apply technical and systems reasoning to performance issues
Exhibit values of impact, curiosity, and velocity
Please submit:
On this page
