Deon & Karen Derrico’s Biggest Secret Revealed By Son They Shunned After He Accused Them Of Fraud
Our friendly administrative staff helps with skills needed for testing, scheduling, and returning timely results to the recruiters. Derrico will test in all aspects of IT dealing with infrastructure, security, development, support, administration, and engineering. We test on soft skills handling management, project management, and business analysis. Clients are able to see status of the screening from submittal to completed results using the client dashboard. A written report is sent by email and can also be viewed through the portal.
The Leaders in one-on-one technical interviewing in IT for over 20 years. We will adapt our personalized testing to meet your specific needs. Derrico interviewers are senior-level IT professionals. Our screeners discuss concepts and questions in a one-on-one conversation with your candidate. Derrico interviewers are thoroughly vetted and trained to create a consistent method of testing. Completed interview results are returned to you in a timely manner.
Once logged into your dashboard, our clients are able to schedule screenings, monitor process, and manage results. Once the screening has been added to our system it is assigned to a senior technical screener working in the field and will kick off at the time and date scheduled. When the candidate is contacted we will professionally assess skills required for the client. We will contact your candidate and use adaptive question sets to find strengths and weaknesses. Once the screening is completed a document will be created and sent to all recipients specified by the client.
Solution of SQL Interview Question #2
The solution SQL query is:
The trick in this task is that you had to use the COUNT()
function two times: first, you had to count the number of s per user, then the number of users (who fulfill the given condition). The easiest way to do that is to use a subquery.
COUNT()
function with a GROUP BY
clause on the event_log
table.AS _per_user
). It’s a syntax requirement in SQL.WHERE
filter and a COUNT()
function on the result of the subquery.Before the tasks – What can you expect in an SQL technical screening?
There are two common ways an SQL tech screening can be done.
The simpler but less common way is that you get a computer, a data set, and a task. While you are solving the task, the interviewers are listening and asking questions. A little trial-and-error is totally fine, as long as you can come up with the correct solution in a reasonable amount of time.
The other, more difficult (and by the way much more common) way is the whiteboard interview. In this case, you don’t get a computer. You have to solve the task and sketch up the code on a whiteboard. This means that you won’t get feedback (at least not from a computer) on whether you made a logical or a syntax error in your code. Of course, you can still solve the tasks by thinking iteratively. You can crack the different SQL problems one by one… But you have to be very confident with your SQL skills.
Additionally, usually, you have to solve the tasks on the fly. Maybe you will get 3-5 minutes of thinking time but that’s the maximum you can expect.
I know, this sounds stressful. And it is. But don’t worry, there is some good news, as well. Because companies know that this is a high-stress interview type, compared to the real-life challenges, you will get relatively simpler tasks. (See the difficulty level below!)
There are several types of SQL tech assessments. The one that I described above (and for that, I’ll provide a few exercises below) is the most common one. When people say “SQL tech screening,” they usually refer to that. To be more precise, I like to call it “in-person SQL screening.”
But, in fact, there are four different types of SQL assessments:
JOIN
s!” That’s a stupid type of SQL tech assessment — as it focuses on theory and not on practice. Still, some companies… you know.When someone asks you to do an “SQL tech screening,” either of the above can come up. Still, the most common is the in-person SQL screening. So let’s see a few examples of that!
Here are three SQL interview questions that are really close to what I actually got or gave on data analyst/scientist job interviews!
Try to solve all of them as if they were whiteboard interviews!
In the second half of the article, I’ll show you the solutions, too!
Just subscribe to the Data36 Newsletter here (it’s free)!
Let’s say you have two SQL tables: authors
and books
. The authors
dataset has 1M+ rows. Here’s a small sample, the first six rows:
author_name | book_name |
author_1 | book_1 |
author_1 | book_2 |
author_2 | book_3 |
author_2 | book_4 |
author_2 | book_5 |
author_3 | book_6 |
… | … |
The books
dataset also has 1M+ rows and here’s the first six:
book_name | sold_copies |
book_1 | 1000 |
book_2 | 1500 |
book_3 | 34000 |
book_4 | 29000 |
book_5 | 40000 |
book_6 | 4400 |
… | … |
Create an SQL query that shows the TOP 3 authors who sold the most books in total!
(Note: Back in the days, I got almost this exact SQL interview question for a data scientist position at a very well-known Swedish IT company.)
You work for a startup that makes an online presentation software. You have an event log that records every time a user inserted an into a presentation. (One user can insert multiple s.) The event_log
SQL table looks like this:
user_id | event_date_time |
7494212 | 1535308430 |
7494212 | 1535308433 |
1475185 | 1535308444 |
6946725 | 1535308475 |
6946725 | 1535308476 |
6946725 | 1535308477 |
… | … |
…and it has over one billion rows.
Note: If the event_date_time
column’s format doesn’t look familiar, google “epoch timestamp”!
Write an SQL query to find out how many users inserted more than 1000 but less than 2000 s in their presentations!
(Note: I personally created and used this interview question to test data analysts when I was freelancing and my clients needed help in their hiring process.)
The first table is called employees
and it contains the employee names, the unique employee ids, and the department names of a company. Sample:
department_name | employee_id | employee_name |
Sales | 123 | John Doe |
Sales | 211 | Jane Smith |
HR | 556 | Billy Bob |
Sales | 711 | Robert Hayek |
Marketing | 235 | Edward Jorgson |
Marketing | 236 | Christine Packard |
… | … | … |
The second SQL table is called salaries
. It holds the same employee names and the same employee ids – and the salaries for each employee. Sample:
salary | employee_id | employee_name |
500 | 123 | John Doe |
600 | 211 | Jane Smith |
1000 | 556 | Billy Bob |
400 | 711 | Robert Hayek |
1200 | 235 | Edward Jorgson |
200 | 236 | Christine Packard |
… | … | … |
The company has 546 employees, so both tables have 546 rows.
Print every department where the average salary per employee is lower than $500!
(Note: I created this test question based on a real SQL interview question that I heard from a friend, who applied at one of the biggest social media companies (name starts with ‘F.’ ;))