Your question is Recurring Abuse Incident Reporting. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
Recurring abuse reporting matters because operations teams need a repeatable way to identify patterns, prioritize risky accounts, and monitor whether interventions are reducing repeat incidents over time.
Walk through how you would structure a SQL-based report to track recurring abuse incidents across Klaviyo accounts. Explain what grain you would choose for the report, how you would define a recurring incident, and how you would use SQL to summarize repeat behavior over time. You should also describe what dimensions and metrics you would include so the report is useful for both day-to-day review and trend analysis.
The interviewer is looking for a practical reporting design answer rather than a single query. Focus on how you would model the logic in PostgreSQL, including how you would use CTEs, date functions, and aggregations to build a reliable recurring-abuse view.