tezvyn:

A key metric dropped 20%. How would you investigate?

Source: newrelic.comadvanced

This tests systematic diagnosis of critical issues. A great answer segments the drop (by region, platform), then traces data upstream from the dashboard to the source, correlating with technical metrics. A red flag is jumping to code before scoping the impact.

This tests your ability to lead a systematic investigation under pressure, distinguishing data bugs from business changes. A strong answer first segments the metric drop (by user, region, device) to isolate the impact. Then, trace the data lineage upstream from the dashboard to the source, checking for silent failures or schema changes. Finally, correlate the drop with technical metrics like latency or error rates. A red flag is jumping into logs or code without first scoping the problem via segmentation.

Read the original → newrelic.com

Get five bites like this every day.

Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.

A key metric dropped 20%. How would you investigate? · Tezvyn