9 Asana SQL Interview Questions (Updated 2024)

Updated on

March 2, 2024

At Asana, SQL is crucial for analyzing user behavior data to improve product features and generating business intelligence reports to drive strategic decision-making. That's why Asana almost always evaluates jobseekers on SQL query questions in interviews for Data Science, Analytics, and & Data Engineering jobs.

As such, to help you study for the Asana SQL interview, this blog covers 9 Asana SQL interview questions – can you answer each one?

Asana SQL Interview

9 Asana SQL Interview Questions

SQL Question 1: Calculate Monthly Average Task Completion Time

As a part of the data analysis team in Asana, you are tasked with analyzing user behavior. To help improve the platform, you are asked to calculate the average time (in days) it takes for tasks to be completed by users on a monthly basis. You need to consider the tasks created and completed within the window of each calendar month.

Example Input:
task_iduser_idcreate_datecomplete_date
36012108/01/2022 00:00:0008/05/2022 00:00:00
52311508/03/2022 00:00:0008/15/2022 00:00:00
10293408/15/2022 00:00:0008/25/2022 00:00:00
44522109/02/2022 00:00:0009/08/2022 00:00:00
30671509/05/2022 00:00:0009/07/2022 00:00:00
Example Output:
mthavg_completion_time
810.00 days
94.00 days

Answer:


This SQL query extracts the month part from the create_date and groups by it, taking the average of the difference between the complete_date and create_date. It only includes the tasks completed within the same month they were created. The result is ordered by month to see the trend of average completion time over the months. The AVG function will give the average completion time in days since we are handling dates.

p.s. Window functions show up pretty frequently during SQL interviews, so practice the 27+ window function questions on DataLemur

DataLemur Window Function SQL Questions

SQL Question 2: Project Tracking System

Consider you are designing a project tracking system for Asana. We have two tables called and .

The table has three columns: (identifier for the project), (identifier for the project manager), and (name of the project).

The table also has four columns: (identifier for the task), (identifier for the project the task is associated with), (identifier for the person assigned to the task), and (status of the task).

Write a SQL query that calculates the percentage of tasks completed for each project.

Example Input:
project_idproject_manager_idproject_name
1123"Project Alpha"
2265"Project Beta"
3362"Project Gamma"
Example Input:
task_idproject_idassignee_idtask_status
1041065"Done"
5671123"Not Started"
6892362"In Progress"
6092192"Done"
0033981"Done"
3003192"In Progress"

Answer:

Here's how you can write the SQL query using PostgreSQL:


This query first joins the and tables on . Then, it calculates the percentage of tasks completed in each project. The statement is used to count the tasks with "Done" status, and then this count is divided by total count of tasks. The function and clause are used to group these calculations by project name. The final result is the percentage of tasks completed for each project.

SQL Question 3: What's the difference between and ?

is used to combine the output of multiple statements into one big result!

Suppose you were a Data Analyst at Asana working on a Sales Analytics project, and had data on sales leads from both the company's Salesforce CRM and it's legacy Hubspot CRM. To write a query to analyze leads created before 2023 started, across both CRMs, you could use in the following way:


filters out duplicates, so each email/job title/company only shows up once (even if it's in both Salesforce and HubSpot CRMs).

On the other hand, the operator does NOT filter out duplicates, so if a lead shows up in both CRMs, it'll be listed twice in the output of .

Asana SQL Interview Questions

SQL Question 4: Filter the users based on their task completion status

Given the database records of users and their tasks, filter the records to find all active users who have completed more than 50% of their tasks in the last month.

Example Input:
user_idregistration_dateis_active
0012020-01-01True
0022019-12-31True
0032021-01-10False
Example Input:
task_iduser_idtask_completion_dateis_completed
00010012022-06-29True
00020012022-06-30True
00030012022-07-01False
00040022022-06-30False
00050022022-07-01False
00060032022-06-30True
Example Output:
user_id
001

Answer:


The main part of the query is a subquery that sums up the total and completed tasks for users over the last month with the help of GROUP BY and CASE WHEN clause. This subquery is then joined with the users table to include only active users. Finally, the WHERE clause filters out the users whose proportion of completed tasks over the total tasks is more than 50%.

SQL Question 5: What is database normalization?

Normalization involves breaking up your tables into smaller, more specialized ones and using primary and foreign keys to define relationships between them. Not only does this make your database more flexible and scalable, it also makes it easier to maintain. Plus, normalization helps to keep your data accurate by reducing the chance of inconsistencies and errors.

The only downside is now is that your queries will involve more joins, which are slow AF and often a DB performance botteleneck.

SQL Question 6: Filtering Customer Records

As a data analyst at Asana, you have been tasked to filter thorough the customer records database to find customers whose emails contain 'asana'. Filter only customers who registered in the year 2021.

Example Input:
customer_idnameemailregistration_date
122Johnjohn.asana@gmail.com01/20/2021
345Emilyemily.asana@yahoo.com12/01/2021
567Daviddavid@gmail.com06/15/2021
654Lauralaura@yahoo.com05/10/2021
899Michaelasana.michael@hotmail.com03/05/2020
Example Output:
customer_idnameemailregistration_date
122Johnjohn.asana@gmail.com01/20/2021
345Emilyemily.asana@yahoo.com12/01/2021

Answer:

Our goal is to fetch customer records in Postgre-SQL with 'asana' in their email and who registered in 2021.


In the given query, we use the keyword with the wildcard to filter email addresses that include the string 'asana' anywhere. We also use the function to get the year part of the registration date and compare it with 2021 to make sure we are only considering customers who registered in this year.

SQL Question 7: Can you list the various types of joins in SQL, and describe their purposes?

In SQL, a join retrieves rows from multiple tables and combines them into a single result set.

Four JOIN types can be found in SQL. For an example of each one, suppose you had a table of Asana orders and Asana customers.

  1. INNER JOIN: Rows from both tables are retrieved when there is a match in the shared key or keys. An between the Orders and Customers tables would return only rows where the in the Orders table matches the in the Customers table.

  2. LEFT JOIN: A retrieves all rows from the left table (in this case, the Orders table) and any matching rows from the right table (the Customers table). If there is no match in the right table, NULL values will be returned for the right table's columns.

  3. RIGHT JOIN: A combines all rows from the right table (in this case, the Customers table) and any matching rows from the left table (the Orders table). If there is no match in the left table, NULL values will be displayed for the left table's columns.

  4. FULL OUTER JOIN: A combines all rows from both tables, regardless of whether there is a match in the shared key or keys. If there is no match, NULL values will be displayed for the columns of the non-matching table.

SQL Question 8: Calculating the Average Spend Per User On Different Projects

Imagine that Asana wants to analyze user spending behavior on different projects. You are asked to gather data where each row represent an unique user, and the columns represent their average spending on different project types.

For this analysis, you have 2 tables: and . The table has columns and and the table has columns , and .

Example Input:
project_idproject_type
1Marketing
2Development
3Finance
4Marketing
5Finance
Example Input:
user_idproject_idpurchase_amount
2151300
1822670
2151450
1825980
2153220
1824560
2152530

Your task is to write a SQL query that joins these tables and calculates the average spent per on each .

Answer:


This SQL query first joins the 'purchases' and 'projects' tables on the 'project_id' column to combine purchase and project information into one table. Then it groups the data by 'user_id' and 'project_type', and for each of these groups, it calculates the average purchase amount with the AVG function. The result is a list showing the average spending of each user on each project type.

Because join questions come up frequently during SQL interviews, practice this Snapchat JOIN SQL interview question: Snapchat Join SQL question

SQL Question 9: Identify Most Active Users by Weekly Log

As a project management company, Asana would like to understand its most active users in terms of task updates on a weekly basis. Develop a query that will identify the top 3 users with the most task updates for each week.

Assume you are given a table named that represents any task updates, comments, or other activities a user performs on a task. Each record represents an activity from a user on a certain timestamp.

Example Input:
update_iduser_idupdate_timetask_id
15423462022-06-02 14:14:204856
98435892022-06-03 09:28:488952
74963462022-06-04 10:12:502567
72558792022-06-08 22:05:448795
61645892022-06-09 16:26:146857
19428792022-06-10 10:55:263214
53243462022-06-11 17:42:321524
95468792022-06-14 21:16:401236
73823462022-06-15 19:32:565124
17465892022-06-16 08:12:006874
Example Output:
weekuser_idactivity_count
223463
225892
238792
233462

Answer:


The query first extracts the week number from by using the DATE_PART function. It then groups these weekly data by and computes the frequency of updates using COUNT function. The ORDER BY statement sorts the result in descending order by to get the users with the most updates. Finally, LIMIT 3 is used to retrieve only the top 3 users with the most updates each week.

Preparing For The Asana SQL Interview

The key to acing a Asana SQL interview is to practice, practice, and then practice some more! Besides solving the above Asana SQL interview questions, you should also solve the 200+ SQL questions on DataLemur which come from companies like Netflix, Google, and Amazon. DataLemur SQL and Data Science Interview Questions

Each SQL question has hints to guide you, detailed solutions and most importantly, there's an interactive coding environment so you can right online code up your SQL query and have it graded.

To prep for the Asana SQL interview you can also be useful to solve SQL questions from other tech companies like:

In case your SQL foundations are weak, forget about diving straight into solving questions – go learn SQL with this free SQL tutorial.

Free SQL tutorial

This tutorial covers topics including CASE/WHEN statements and creating summary stats with GROUP BY – both of which come up often in SQL interviews at Asana.

Asana Data Science Interview Tips

What Do Asana Data Science Interviews Cover?

In addition to SQL interview questions, the other topics to practice for the Asana Data Science Interview are:

  • Statistics and Probability Questions
  • Python Pandas or R Coding Questions
  • Data Case Study Questions
  • ML Modelling Questions
  • Resume-Based Behavioral Questions

Asana Data Scientist

How To Prepare for Asana Data Science Interviews?

To prepare for Asana Data Science interviews read the book Ace the Data Science Interview because it's got:

  • 201 interview questions taken from companies like Google, Tesla, & Goldman Sachs
  • a refresher covering SQL, Product-Sense & ML
  • over 900+ 5-star reviews on Amazon

Ace the Data Science Interview Book on Amazon

© 2024 DataLemur, Inc

Career Resources

Free 9-Day Data Interview Crash CourseFree SQL Tutorial for Data AnalyticsSQL Interview Cheat Sheet PDFUltimate SQL Interview GuideAce the Data Job Hunt Video CourseAce the Data Science InterviewBest Books for Data Analysts