SQL Case · Hard · 45 min
Game economy: Find completed events whose amount exceeds their player segment's completed-event average
Game economy: Find completed events whose amount exceeds their player segment's completed-event average.
View taskPublic task directory
Every entry below is a crawlable link to a unique public task page. This directory complements the interactive filters and keeps the complete catalog connected through standard pagination.
Page 353 of 386 · 18,491 tasks
SQL Case · Hard · 45 min
Game economy: Find completed events whose amount exceeds their player segment's completed-event average.
View taskSQL Case · Medium · 30 min
Game economy: Find players that reached matchcompleted no more than seven days after creation.
View taskSQL Case · Medium · 30 min
Game economy: Return player-gamemode relationships active ten days after the first relationship began.
View taskSQL Case · Easy · 20 min
Game economy: Find players with at least two recorded events.
View taskSQL Case · Hard · 45 min
Game economy: Calculate each gamemode category's share of all completed value.
View taskSQL Case · Easy · 20 min
Game economy: Calculate completed event value for each player segment.
View taskSQL Case · Hard · 45 min
Game economy: Group consecutive active dates into islands for each player.
View taskSQL Case · Easy · 20 min
Game economy: Count distinct players with activity on each day.
View taskSQL Case · Medium · 30 min
Game economy: Calculate daily completed value and its running total.
View taskSQL Case · Hard · 45 min
Game economy: Measure whether each creation-date cohort returned on the next calendar day.
View taskSQL Case · Medium · 30 min
Game economy: Keep the latest row for each external event key.
View taskSQL Case · Easy · 20 min
Game economy: Find players with no activity after the first active month's end.
View taskSQL Case · Medium · 30 min
Game economy: Find completed events above the same player's completed-event average.
View taskSQL Case · Easy · 20 min
Game economy: Return the first matchcompleted timestamp for each player that succeeded.
View taskSQL Case · Easy · 20 min
Game economy: Find events whose gamemode reference does not exist.
View taskSQL Case · Easy · 20 min
Game economy: Return the latest event for each player.
View taskSQL Case · Hard · 45 min
Game economy: Return one row per player with completed lifetime value and latest completed event.
View taskSQL Case · Easy · 20 min
Game economy: Combine live and archived completed events without accidental deduplication.
View taskSQL Case · Medium · 30 min
Game economy: Compare completed value with the previous active month.
View taskSQL Case · Medium · 30 min
Game economy: Calculate the completed-event rate for every gamemode with activity.
View taskSQL Case · Hard · 45 min
Game economy: Resolve every gamemode to its root gamemode.
View taskSQL Case · Medium · 30 min
Game economy: Count players that produced sessionstarted and later produced matchcompleted.
View taskSQL Case · Medium · 30 min
Game economy: Rank players by completed amount inside each region.
View taskSQL Case · Medium · 30 min
Game economy: Find matchcompleted events that happened within seven days of the same player's previous success.
View taskSQL Case · Hard · 45 min
Game economy: Calculate the rolling average over each player's current and previous two events.
View taskSQL Case · Medium · 30 min
Game economy: Measure the share of players in each segment that ever reached matchcompleted.
View taskSQL Case · Medium · 30 min
Game economy: Split each player's events when inactivity exceeds 30 minutes.
View taskSQL Case · Easy · 20 min
Game economy: Produce one status summary row per player.
View taskSQL Case · Medium · 30 min
Game economy: Find the gamemode with the largest completed value in each category.
View taskSQL Case · Medium · 30 min
Game economy: Return the two highest-value players in each segment.
View taskSQL Case · Easy · 20 min
Game economy: List players that never produced a matchcompleted event.
View taskSQL Case · Hard · 45 min
Healthcare operations: Find completed events whose amount exceeds their patient segment's completed-event average.
View taskSQL Case · Medium · 30 min
Healthcare operations: Find patients that reached visitcompleted no more than seven days after creation.
View taskSQL Case · Medium · 30 min
Healthcare operations: Return patient-carepath relationships active ten days after the first relationship began.
View taskSQL Case · Easy · 20 min
Healthcare operations: Find patients with at least two recorded events.
View taskSQL Case · Hard · 45 min
Healthcare operations: Calculate each carepath category's share of all completed value.
View taskSQL Case · Easy · 20 min
Healthcare operations: Calculate completed event value for each patient segment.
View taskSQL Case · Hard · 45 min
Healthcare operations: Group consecutive active dates into islands for each patient.
View taskSQL Case · Easy · 20 min
Healthcare operations: Count distinct patients with activity on each day.
View taskSQL Case · Medium · 30 min
Healthcare operations: Calculate daily completed value and its running total.
View taskSQL Case · Hard · 45 min
Healthcare operations: Measure whether each creation-date cohort returned on the next calendar day.
View taskSQL Case · Medium · 30 min
Healthcare operations: Keep the latest row for each external event key.
View taskSQL Case · Easy · 20 min
Healthcare operations: Find patients with no activity after the first active month's end.
View taskSQL Case · Medium · 30 min
Healthcare operations: Find completed events above the same patient's completed-event average.
View taskSQL Case · Easy · 20 min
Healthcare operations: Return the first visitcompleted timestamp for each patient that succeeded.
View taskSQL Case · Easy · 20 min
Healthcare operations: Find events whose carepath reference does not exist.
View taskSQL Case · Easy · 20 min
Healthcare operations: Return the latest event for each patient.
View taskSQL Case · Hard · 45 min
Healthcare operations: Return one row per patient with completed lifetime value and latest completed event.
View task